When punch data is received from the host system, MSRJE can do any of the following:
• Create a new disk file and write the punch data to it.
• Add the punch data to an existing file.
• Create a new sequential file and write the punch data to disk as 256-character unprocessed records.
• Add the punch data to an existing sequential file of 256-character unprocessed records (this file can contain both print and punch data).
The destination of punch output received from the host subsystem is controlled by a forms control table. When you configured MSRJE for the location specified in the MSRJE procedure command, you may have specified the name of a forms control table that is to control output received from the host system. The forms control table name is specified on display 36.0 during MSRJE subsystem configuration. You can create forms control tables by using the RJT ABLE procedure command, as described in Chapter 5. If you do not specify a forms control name during subsystem member configuration (on display 36.0), the IBM-supplied default values for punch output are used. These default values are shown in Appendix D.
When punch output is received from the host system, it is usually preceded by a host forms name. If MSRJE receives that name, it searches the specified forms control table, if any, for an entry with the same name. If a matching entry is found, the information in that table entry is used to control creating and writing of disk files. If no matching entry is found, the default punch output entry in the specified table is used. If no host forms name is received with the data, MSRJE uses the name from the previous output. If no forms control table was specified on display 36.0 during configuration, MSRJE uses the IBM-supplied punch output default values. The forms control table and the forms control table utility are described in Chapter 5. The IBM-supplied default values are shown in Appendix D.
Punch output directed to a disk file or to a compressed disk file is labeled by MSRJE using the punch file sequence number (as defined on display 36.0 during MSRJE configuration) and the file label from the matching forms control table entry. If there is no matching entry in the table, the punch default entry is used. If there is no forms control table, the IBM-supplied defaults for punch data, as shown in Appendix D, are used. The format of the label created by MSRJE is:
xxxxxxnn where
xxxxxx nn
is the file label from the control table entry or MSRJE
is the punch file sequence number if ADD-NO is specified in the control table.
or
nn is 00 when ADD-YES is specified in the control table entry.
Note: ADD-YES specifies that received punch data is to be written to an existing file (the new data is written after any data already in the file). If ADD-YES is specified and file xxxxxxOO does not exist, MSRJE creates that file and then writes the punch data to it. ADD-NO specifies that the data is to be written to a new file that is created when needed by MSRJE.
Whenever a file is created using the punch file sequence number, the number is increased by 1 for all files except the first file created. For example, if you had specified 10 for the punch file sequence number on display 36.0 during
configuration, the first file would be xxxxxxlO, and the next file would be xxxxxxl 1.
The maximum value for the sequence number is 99. If the last file created were xxxxxx99, the next file would be xxxxxxOl.
To take full advantage of the forms control table functions, you should be aware of the following:
• For SNA MSRJE, the host system should send Peripheral Data Information Records (PDIR), and forms names should be specified in the host system JCL.
The sending of PDIRs by the host is specified at the host system during system generation.
For BSC MSRJE, the host system should send forms mount messages, and forms name should be specified in the host system JCL.
If forms mount messages or PDIRs are not sent by the host system, MSRJE uses the last forms name received by the punch, or the forms name that was saved in the forms set member for the punch.
Operator Messages from the Host System
Operator messages from the host system received by MSRJE are written to the history file. If the MSRJE console is active when a message is received from the host system, the message is also displayed at the console.
Operator Messages from MSRJE
Messages to the operator from MSRJE are handled as follows:
All messages are logged to the history file.
• Reader messages are displayed at the display station that started the reader, unless the display station has been released, MSRJE has been started from the JOBQ, or MSRJE has been evoked.
• Readers started from the MSRJE console while in console input mode display only those messages that indicate the reader has started or ended.
• Messages from MSRJE relating to console input are displayed at the MSRJE console.
• Printer and punch messages are displayed at the MSRJE console if the console is active.
MSRJE supports the System/36
I I
NOHAL T capability. If a halt message is directed to a display station, it is automatically responded to, but not displayed, if the system NO HALT criteria are met. The System Reference manual describes the NOHALT capability.If a halt message is directed to a display station that has been released from
MSRJE, the message is logged to the history file, and the default response is always taken.
You can modify the default responses for MSRJE messages in the same manner as you can modify the default responses for other system messages. MSRJE messages are stored in the system message member (##MSGl). The System Reference manual contains more information.