3.7

Output Message Cache and Retrieving Procedure

3.7.1

Output Message Cache

Output message cache refers to an area which only exists in the interactive processing mode(packaged software) and interactive processing mode (SMTP two-way), and where messages withmessage types of Printer [P]/[A], user's own interface [T], or Storage [U] are temporarily stored.
For this area, there are 3 types, QST (terminal output message queue), QFL (error message queue),
QEX (stored message queue). A procedure to retrieve messages stored in this area is called "retrieving
procedure". Details of the procedure vary depending on types of message queues.

3.7.2

Retrieving procedure"Error message retrieving procedure (SYG)" (hereinafter, referred as to "SYG procedure") and "stored
message retrieving procedure (REQ)" (hereinafter, referred as to "REQ procedure" are procedures
which are carried out when retrieving output messages stored in the output message cache in NACCS
Center server.
For output message cache, there are the following 3 areas. Table 3.7.1 shows 3 areas in the output
message cache.
Table 3.7.1
Type(1) QST(Terminal
output message
queue)

Setting unit ofqueue
Each logicalterminal name

3 Areas in Output Message Cache
Content

Area where messages with message type of Printer [P]/[A], user's own
interface [T], or Storage [U] are stored before being sent to users.
the messages are stored in this area, and at the same time, are sent to thefollowing destination.
• For interactive processing mode (software package)→ Logical Terminal Name

User’s e-mailaddress(2) QFL
Each user code
(Error message
queue)(3) QEX(Storedmessagequeue)

Each user code

Area where messages with message type of Printer [P]/[A], user's own
interface [T], or Storage [U] are stored before being sent to users.
the messages are stored in this area, and at the same time, are sent to thefollowing destination.
• For interactive processing mode (SMTP two-way)→ User’s e-mail address
Area where messages are stored when messages stored in QST (terminal
output message queue) cannot be output due to error.
* The message is stored only if the mode is the Interactive Processing Mode
(SMTP two-way).
Area where messages to request retrieving are stored.

3-7-1

In cases when an error occurs during the sending of messages stored in QST (terminal output
message queue) for the Interactive Processing Mode (SMTP two-way), messages stored in QST(terminal output message queue) will be stored in QFL. Figure 3.7.1 shows image of the output
message cache. In this case, the way how the messages are stored is changed from each logicalterminal name or each user’s e-mail address to each user code.

Table 3.7.2 shows retrieving procedure for messages stored in QFL (error message queue) and QEX(stored message queue).

QST
QFL
QEX

Figure 3.7.1 Output Message Cache

Table 3.7.2

Name of User Queue and Retrieving Procedure

Name of queue
QFL (error message queue)
QEX (stored message queue)!

Retrieving procedure (procedure code)
Error message retrieving procedure(SYG)
Stored message retrieving procedure(REQ)

Only messages with message type of Printer [P]/[A], user's own interface [T], or Storage [U]are stored in the output message cache.
Therefore, when faults such as troubles in communication paths, center down, or down of
SMTP two-way server occurs, the relevant messages will be discarded and no longer theuser cannot be received.

3-7-2

3.7.2.1

SYG procedure"SYG procedure" refers to the procedure to retrieve messages stored in QFL (error message
queue) in the interactive processing mode (SMTP two-way).
(1)

Conditions where messages are stored in QFL (error message queue)

When messages satisfy the following conditions of (1), (2) and (3), those will be stored in QFL(error message queue). Figure 3.7.2 shows image where messages are stored in QFL (error
message queue).
(1) The message is for the Interactive Processing Mode (SMTP two-way).
(2) A message is an output information, and message type is Print [P]/[A], user's own interface[T], or Storage [U].
(3) Due to the fact that the line between NACCS Center server and the user system is
disconnected, or faults occur in hardware or software of the user system, communication
cannot be normally carried out.
NACCS Center server

User system

SMTP server

××

ReceptionsystemCore processing system
Procedure
processing
systemMessag e Typeother th an [P], [A], [T],[U]

Discardedor

Messag e Type[P], [A], [T], [U]Communication
impossible

QST

SYG

Messag es with message
type of [P], [A], [T], or [U]
are reg istered in QS T at
first.

QFL
QEX

When the line between NACCS Center server and the user system is
disconnected, or faults occur in hardware or software of the user system, andcommunication cannot be normally carried out, messages registered in QST will
be stored in QFL

Figure 3.7.2 Image where Messages Are Stored in Error Message Queue(2)

Example of procedure sequential of "SYG procedure" in interactive processing mode (SMTP
two-way)

When retrieving messages stored in QFL (error message queue) through "SYG procedure",
carry out the following procedure:
Figure 3.7.3 shows an example of procedure sequential of "SYG procedure" in interactive
processing mode (SMTP two-way).
(1) Specify REF△△△△ in procedure-by-procedure field through "SYG procedure", then send themessage. (See Table 3.7.3)(2) A list of messages stored in QFL (error message queue) of the output message cache will
be returned.
(3) After obtaining the list, send output information code of the processing result message to be
retrieved. (See Table 3.7.3)
3-7-3

(4) A processing result notification message for "SYG procedure" and a processing result
message of the relevant output information code are sent from NACCS Center server to theuser system.
! • When carrying out "SYG procedure", do not send output information code from the beginning, but makesure to specify REF△△△△ in procedure-by-procedure field and send it, and obtain a list of messages
stored in QFL (error message queue) of the output message cache, then retrieve a processing result
message.
• The number of messages which can be retrieved is written in the obtained list. However, there are somemessages which are newly stored in the output message cache after the list is referred, so there is apossibility that messages of more than the number written in the list will be sent from NACCS Center
server.
• There need to periodically carry out "SYG procedure" and retrieve messages stored in the output message
cache in NACCS Center server. However, this procedure results in putting a heavy load on NACCS Center
server, so do not this procedure frequently.
(For guidelines for interval of retrieving, refer to T08 in "4.2.6 Others (5) value of each timer classification.")User system

NACCS Center server[SYG error message process]Process code

Core processing system

REF
(1)

Procedure
processing
systemFileexchange
block

Processing
request message

QST[SYG error message inquiry process]Process code

List

OutputInformation code
AAE0010
AAD0020

Number ofmessages
0002
0005

(2)
Process Result
Message

REF
response

Q
F
L

COMPLETION[SYG error message inquiry process]Process code

AAD0020

OutputInformation code
AAE0010
AAD0020

Number ofmessages
0002
0005

(3)
Processing
request message

COMPLETION(4)
Processing result
notification message

Message

Message

Process Result
Message

QEX

Figure 3.7.3 Example of procedure sequential of "SYG procedure" in interactive processing mode
3-7-4

(SMTP two-way) (The screen shown in the figure is one example.)

3-7-5

(3)

Example of message used in "SYG procedure"(1) Input message used in "SYG procedure"
When retrieving messages stored in the error message queue through "SYG procedure", send
the following message to NACCS Center server. Figure 3.7.4 shows an example of an input
message used in "SYG procedure". In addition, Table 3.7.3 shows procedure-by-procedure
fields in input messages used in "SYG procedure".
XXXXXXXXXXX････････XXXXXXXXXX <CRLF>
Input common field (398 bytes)

XXXXXXX <CRLF>

Procedure-by-procedure field (7 bytes)

Figure 3.7.4 Example of Input Message Used in "SYG Procedure"

Table 3.7.3
Field name
Data

Delimiter

Procedure-By-Procedure Field (Input) used in "SYG Procedure"

length72OutlineSpecifies types of request of
retrieving

Indicates the end edge of the field.

Sample Settings, etc.
REF△(when obtaining a list)
Output information code (when retrieving amessage)(e.g.: AAE0010)(CRLF sign must be entered.)(2) Output message used in "SYG procedure" (when obtaining a list)
Figure 3.7.5 shows an example of an output message when REF is specified inprocedure-by-procedure fields and the message is sent (when obtaining a list). In addition,
Table 3.7.4 shows procedure-by-procedure fields.
XXXXXXXXXXX･･････････････････････XXXXXXXXXX<CRLF>

Common output field (398 bytes)
XXXXX-XXXX-XXXX

Processing result
code 1 (15 bytes)△△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△(15 bytes)(15 bytes)(15 bytes)<CRLF>(15 bytes)

XXXX <CRLF>
Number of information (4 bytes)
XXXXXXX <CRLF>
Output information code (7 bytes)
XXXX <CRLF>

Output information code and the number of nontransmitted messages are the repeating fields

Number of non-transmitted messages(4 bytes)Figure 3.7.5

Example of Output Message used in "SYG Procedure" (when obtaining a List)
3-7-6

Table 3.7.4
Item
No.

Procedure-By-Procedure Field (Output) used in "SYG Procedure" (When Obtaining a List)

Field name1

Processing resultcode2Delimiter

3

Number of
information

4

Delimiter

5

Output information
code (Note)
Delimiter(Note)
Number of
non-transmitted
messages(Note)
Delimiter(Note)

6
7

8

lengthOutlineSample Settings, etc.

75 The processing result which isassessed by the system is output
by code.
2 Indicates the end edge of the field.

00000-0000-0000…(60 spaces)…

4 Number of repetition of output
information code andnon-transmitted messages is
specified.
2 Indicates the end edge of the field.

e.g.: 0001

7 The code of an output message is
specified.
2 Indicates the end edge of the field.

e.g.: AAE0010(CRLF sign must be entered.)(CRLF sign must be entered.)(CRLF sign must be entered.)

4 The number of messages with
e.g.: 0002
above-mentioned output
information code stored in QFL(error message queue) is specified.
2 Indicates the end edge of the field. (CRLF sign must be entered.)(Note) Item No. 5 through 8 are the repeating fields.

(3) Output message used in "SYG procedure" (when retrieving a message)
Figure 3.7.6 shows an example of an output message when procedure-by-procedure fields
are specified and the message is sent (when retrieving a message). In addition, Table 3.7.5
shows procedure-by-procedure fields.
XXXXXXXXXXX･･････････････････････XXXXXXXXXX<CRLF>

Common output field (398 bytes)
XXXXX-XXXX-XXXX△△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△

Processing result
code 1 (15 bytes)(15 bytes)(15 bytes)(15 bytes)<CRLF>(15 bytes)

XXXXXXXXX････････････XXXXXXXXXX<CRLF>

Procedure-by-procedure
information (40 bytes)

Figure 3.7.6 Example of Output Message Used in "SYG Procedure" (When Retrieving a Message)

Table 3.7.5
Item
No.

Procedure-By-Procedure Field (Output) used in "SYG Procedure" (When Retrieving a
Message)

Field name1

Processing resultcode2Delimiter

3

Procedure-by-proced
ure information

4

Delimiter

lengthOutlineSample Settings, etc.

75 The processing result which is
00000-0000-0000…(60 spaces)…
assessed by the system is output
by code.
2 Indicates the end edge of the field. (CRLF sign must be entered.)

40 Indicates specific information.

e.g.: ACCEPTED REQUEST (normal termination): NO ELEMENT (no subject to be retrieved): RECEIVING TERMINAL (already during
retrieving)
2 Indicates the end edge of the field. (CRLF sign must be entered.)

3-7-7

3.7.2.2

REQ procedure"REQ procedure" refers to the procedure to retrieve messages stored in QEX (stored message
queue).
(1) Conditions where messages are stored in QEX (stored message queue)
When messages satisfy the following conditions of (1) and (2), those will be stored in QEX(stored message queue). Figure 3.7.7 shows image.
(1) Message Destination Control Format is QEX type (Note).
(2) A message is an output information, and message type is Print [P]/[A], user's own
interface [T], or Storage [U].
(Note) QEX refers to queue for each user code where EXC type messages which are output in
response to third party's event are registered.
In addition, for Message Destination Control Format, refer to "Chapter 5 Message
Destination Control".
User system

NACCS Center server

Core processing system
Procedure
processing system

Transaction Request• Messages other than QEX typemessages• Other than Message Type [P], [A], [T],[U]

• Messages other than QEX typemessages• Message Type [P], [A], [T], [U]

QST
QFL

REQ

• QEX type messages• Message Type [P], [A], [T], [U]QEX

Figure 3.7.7 Image where Messages Are Stored in Stored Message Queue (When (1) and (2) Are
Satisfied)

3-7-8

(2) "REQ procedure" for interactive processing mode (software package is used)
In interactive processing mode (software package is used) also, "REQ procedure" needs to be
carried out in order to retrieve messages stored in the output message cache. However, ininteractive processing mode (software package is used), the function to retrieve stored
messages can realize that.
(3) Example of procedure sequential of "REQ procedure" in interactive processing mode (SMTP
two-way)
When retrieving messages stored in QEX (stored message queue) through "REQ procedure",
carry out the following procedure: Figure 3.7.8 shows an example of procedure sequential of"REQ procedure" in interactive processing mode (SMTP two-way).
(1) Specify REF in procedure-by-procedure field through "REQ procedure", thensend the message. (See Table 3.7.6)(2) A list of messages stored in QEX (stored message queue) of the output message cache will
be returned.
(3) After obtaining the list, send output information code of the processing result message tobe retrieved. (See Table 3.7.6)(4) A processing result notification message for "REQ procedure" and a processing result
message of the relevant output information code are sent from NACCS Center server tothe user system.
!

• When carrying out "REQ procedure", do not send output information code from the
beginning, but make sure to specify REF in procedure-by-procedure field andsend it, and obtain a list of messages stored in QEX (stored message queue) of the output
message cache, then retrieve a processing result message.
• The number of messages which can be retrieved is written in the obtained list. However,there are some messages which are newly stored in the output message cache after thelist is referred, so there is a possibility that messages of more than the number written in
the list will be sent from NACCS Center server.
• There need to periodically carry out "REQ procedure" and retrieve messages stored in the
output message cache in NACCS Center server. However, this procedure results in
putting a heavy load on NACCS Center server, so do not this procedure frequently.
(For guidelines for interval of retrieving, refer to T08 in "4.2.6 Others (5) value of eachtimer classification.")

3-7-9

User system

NACCS Center server[REQ stored message process]Process code

Core processing system

REF
(1)

Procedure
processing
systemFileexchange
block

Processing
request message

QST
QFL

[REQ stored message inquiry process]Process code

List

OutputInformation code
AAE0010
AAD0020

Number ofmessages
0002
0005

(2)
Process Result
Message

REF
response

Q
E
X

COMPLETION[REQ stored message inquiry process]Process code

AAD0020

OutputInformation code
AAE0010
AAD0020

Number ofmessages
0002
0005

(3)
Processing
request message

COMPLETION(4)

Message

Processing result
notification message
Process Result
Message

Message

Figure 3.7.8 Example of procedure sequential of "REQ procedure" in interactive processing mode
(SMTP two-way)(The screen shown in the figure is one example.)

3-7-10(4) Example of message used in "REQ procedure"(1) Input message used in "REQ procedure"
When retrieving messages stored in the stored message queue through "REQ procedure",
send the following message to NACCS Center server. Figure 3.7.9 shows an example of an
input message used in "REQ procedure". In addition, Table 3.7.6 shows
procedure-by-procedure fields in input messages used in "REQ procedure".

XXXXXXXXXXX･･･････････XXXXXXXXXX <CRLF>
Input common field (398 bytes)

XXXXXXX <CRLF>

Procedure-By-Procedure Field (7 bytes)

Figure 3.7.9 Example of Input Message Used in "REQ Procedure"

Table 3.7.6
Field name
Data

Procedure-By-Procedure Field (Input) used in "REQ Procedure"

length7

Delimiter

OutlineSpecifies types of request of
retrieving

2

Indicates the end edge of the field.

Sample Settings, etc.
REF (when obtaining a list)
Output information code (when retrieving amessage)(e.g.: AAE0010)(CRLF sign must be entered.)(2) Output message used in "REQ procedure" (when obtaining a list)
Figure 3.7.10 shows an example of an output message when REF is specified inprocedure-by-procedure fields and the message is sent (when obtaining a list). In addition,
Table 3.7.7 shows procedure-by-procedure fields in output messages used in "REQ
procedure".
XXXXXXXXXXX･･････････････････････XXXXXXXXXX<CRLF>

Common output field (398 bytes)
XXXXX-XXXX-XXXX△△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△

Processing result
code 1 (15 bytes)(15 bytes)(15 bytes)(15 bytes)<CRLF>(15 bytes)

XXXX <CRLF>
Number of information (4 bytes)

XXXXXXX <CRLF>
Output information code (7 bytes)

Output information code and the number of untransmitted
messages are the repeating fields.

XXXX <CRLF>
Number of non-transmitted
messages (4 bytes)

Figure 3.7.10 Example of Output Message used in "REQ Procedure" (when obtaining a List)
3-7-11

Table 3.7.7
Item
No.
1

Procedure-By-Procedure Field (Output) used in "REQ Procedure" (When Obtaining a List)

Field namelengthProcessing result
code

75

2

Delimiter

2

3

Number of
information

4

4

Delimiter

25

Output information
code (Note)
Delimiter(Note)
Number of
non-transmitted
messages(Note)

7

Delimiter(Note)

2

6
7

8

2
4

OutlineSample Settings, etc.

The processing result which isassessed by the system is output
by code.
Indicates the end edge of the field.

00000-0000-0000…(60 spaces)…

Number of repetition of output
information code andnon-transmitted messages is
specified.
Indicates the end edge of the field.

e.g.: 0001

The code of an output message is
specified.
Indicates the end edge of the field.

e.g.: AAE0010

The number of messages withabove-mentioned output
information code stored in QEX(stored message queue) is
specified.
Indicates the end edge of the field.

e.g.: 0002

(CRLF sign must be entered.)(CRLF sign must be entered.)(CRLF sign must be entered.)(CRLF sign must be entered.)(Note) Item No. 5 through 8 are the repeating fields.
(3) Output message used in "REQ procedure" (when retrieving a message)
Figure 3.7.11 shows an example of an output message when procedure-by-procedure fields
are specified and the message is sent (when retrieving a message). In addition, Table 3.7.8
shows procedure-by-procedure fields.
XXXXXXXXXXX･･････････････････････XXXXXXXXXX<CRLF>

Common output field (398 bytes)
XXXXX-XXXX-XXXX△△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△ △△△△△△△△△△△△△△△

Processing result
code 1 (15 bytes)(15 bytes)(15 bytes)(15 bytes)<CRLF>(15 bytes)

XXXXXXXXX････････････XXXXXXXXXX
Procedure-by-procedure information(40 bytes)<CRLF>

Figure 3.7.11 Example of Output Message Used in "REQ Procedure" (When Retrieving a Message)
Table 3.7.8

Procedure-By-Procedure Field (Output) used in "REQ Procedure" (When Retrieving a
Message)

Item
No.
1

Field namelengthProcessing result code752Delimiter

2

3

Procedure-by-procedure
information

40

4

Delimiter

2

Outline
The processing result which isassessed by the system is output
by code.
Indicates the end edge of the
field.
Indicates specific information.

Indicates the end edge of the
field.

3-7-12

Sample Settings, etc.
00000-0000-0000…(60 spaces)…

(CRLF sign must be entered.)e.g.: ACCEPTED REQUEST (normal
termination): NO ELEMENT (no subject to be retrieved): RECEIVING TERMINAL (already during
retrieving)(CRLF sign must be entered.)