Your NOF program can provide various output formats to your NOF program or terminal. These include the format for an Automatic Entry to the NOF program. Within your NOF program, establish which of these formats you have received, by interrogating the returned values of GL-MSG-CODE, GL-MSG-KIND and GL-MSG-COUNT within GL-MSG-HEADER, which gives the first eight bytes of each message.

The output formats and values of these items are shown in the following subsections.

Response to HI (Page 2)

The formats used are as follows, where fireup is your Fireup Ispec, status is the 80-byte status line value, and five-spaces is literally five spaces:

fireup N01 status 
five-spaces N01 status

If you have a Fireup Ispec, you also get a response to a recall.

Response – Recall or REFRESH

The formats used are as follows, where ispec is your <<Ispec>> class, status is the 80-byte status line value, data is your screen data, and five-spaces is literally five spaces.

Response when Ispec not Recall or REFRESH:

five-spaces N01 status

Response to a request, Recall, or REFRESH:

ispec T data [ status ]

If the message type is a response to an Ispec request, REFRESH, or Recall, then the data is returned unformatted. This means that formatting routines (such as zero suppression), that would be performed if the output was to a terminal, are not performed. Refer to the following subsection for the NOF output format of screen attributes.

Automatic Entry to NOF program

The formats used are described as follows, where ispec is your <<Ispec>> class, data is your screen data, status is the 80-byte status line value, nn is a two-digit number, and nn-lines is nn 80 byte lines of data.

Automatic Entry to NOF program:

ispec T data

Status line message:

STATUS01 status

Error message:

ERRORS nn ( lines )

If the message type is an error message, nn can be 01 through 10. If the number of errors exceeds ten, additional error messages are sent. You might also get a response to a request, Recall, or REFRESH.

Response to Administration Command or Teach Screen Request

The formats used are described as follows, where nn is a two-digit number, and nn-lines is nn 80 byte lines of data.

Administration command:

COLONS nn ( nn-lines )

Teach screen request:

TEACHS nn ( nn-lines )

If the message type is a response to an Administration command or Teach screen request, or is Report output, nn can be 01 through 24.

Report Output Transactions

The format for Report Output transactions is as follows, where nn is a two-digit number, and nn-lines is nn 80 byte lines of data.

REPLYS nn ( nn-lines )

You receive a response to a Teach screen request, then possibly a response to a request, Recall, or REFRESH message type.

Transaction Fails LSM Security

The formats used are described as follows, where ispec is your Ispec, status is the 80-byte status line value, nn is a two-digit number, and nn-lines is nn 80 byte lines of data.

Transaction fails LSM security:

LSMERS01 status

End of reply:

&&&&&& nn ( nn-lines )

You receive an End of Reply message as the last message from the input transaction, unless the transaction fails to be recognized. This is not sent to NOF stations.

SWITCH; Command Output

The format for SWITCH; command output is as follows, where window is the 17 byte window name, partition is the 19 byte partition name, mmmm is the data length in bytes (with a maximum value of 1880), and data is mmmm bytes of data:

SWITCH window partition 
mmmm data

If the NOF program receives a SWITCH; command (SWITCH in first 6 characters), the data area received should be sent to the window in the message. The data length (mmmm) has a maximum of 1,880 bytes.