COBOL Manual for TNS/E Programs (H06.08+, J06.03+)

Table 28 Message Types That the Program Generates (System)
Message-Type CodeCOBOL Keyword
Not used—see Table 30ABEND
-104CLOSE
-32CONTROL
-35CONTROLBUF
-23MEMORY-LOCK-COMPLETION
-24MEMORY-LOCK-FAILURE
-12NEWPROCESSNOWAIT-COMPLETION
-103OPEN
-34RESETSYNC
-33SETMODE
Not used—see Table 30STOP
-22TIME-SIGNAL
Messages generated by asynchronous hardware events must be explicitly requested.
NOTE: Specifying certain classes of system messages in the REPORT clause does not ensure that
the program will receive the system messages. In addition to specifying the system messages in
the REPORT clause, these messages must be explicitly requested by executing appropriate Guardian
procedures.
Table 29 Message Types That the Hardware Generates (Asynchronous)
Message-Type CodeCOBOL Keyword
-105BREAK
-02 or -101CPU-DOWN
-03CPU-UP
Not used—see Table 30NETWORK
-11POWER-ON
-10SETTIME
See the Guardian Procedure Errors and Messages Manual for a description of system messages,
their formats, and their implications.
LOGICAL-OPEN and LOGICAL-CLOSE are conventions that enable a program to keep track of its
active requesters simply and directly. LOGICAL-OPEN selects only the first OPEN message from
each new requester. OPEN messages from requester backups are automatically handled by the
run-time routines and not passed to the program. Similarly, LOGICAL-CLOSE selects only the final
CLOSE message from a requester. If both are asserted, the program receives a single OPEN
message whenever a process or process pair bids for requester access and a single CLOSE message
whenever an active requester relinquishes its access. Because the specific message type causes
all messages of its class to be passed to the program, the assertion of OPEN (or SYSTEM, which
implies OPEN) overrides LOGICAL-OPEN, and the assertion of CLOSE (or SYSTEM) overrides
LOGICAL-CLOSE.
150 Environment Division