Guardian Application Conversion Guide

Opening and Communicating With a High-PIN Server
Converting C Applications
096047 Tandem Computers Incorporated 5–23
Reading System Messages From $RECEIVE
Your requester might read system messages from $RECEIVE using the READ[X] or
READUPDATE[X] procedure:
char message_buffer[200]; /* Message buffer (200 bytes) */
...
read_count = 200;
c_code = READX (receive_file_number,
message_buffer,
read_count,
bytes_read);
The lengths shown for each system message are subject to change. In a future release,
Tandem might add new fields to the end of a system message (while maintaining the
layout of the existing fields). Therefore, use a READ[X] or READUPDATE[X] message
buffer at least 250 bytes in length. Also, use a read_count parameter of 250 bytes.
If you use the ZSYSC file, use the ZSYS_VAL_SMSG_LEN constant declaration to
specify the system message length in bytes. If you work in words you can use the
ZSYS_VAL_SMSG_WLEN constant declaration instead.
char message_buffer[ZSYS_VAL_SMSG_LEN];
...
read_count = ZSYS_VAL_SMSG_LEN;
c_code = READX (receive_file_number,
message_buffer,
read_count,
bytes_read);
The ZSYSC file also contains structures that you can use when your requester reads
system messages.
Reading Process-Deletion System Messages. Your requester might monitor a server
process by reading these process-deletion system messages from $RECEIVE:
-2 CPU down: named process deletion
-5 Process normal deletion: stop
-6 Process abnormal deletion: abend
Convert your requester to read and process the D-series system message -101 (Process
deletion), which supersedes all the above messages.