Guardian Application Conversion Guide

Being Opened by and Communicating With a High-PIN Requester
Converting COBOL85 Applications
4–26 096047 Tandem Computers Incorporated
Defining an Opener Table
If your program is a server that tracks its openers, you might define an opener table
using a process ID to identify an opener:
* C-series opener table.
01 OPENER-TABLE.
03 OPENERS OCCURS 15 TIMES.
05 CURRENT-COUNT PIC 999 COMPUTATIONAL.
05 PRIMARY-OPENER.
07 PROCESS-NAME PIC X(6).
07 CPU-PIN PIC S9(5).
05 BACKUP-OPENER.
07 PROCESS-NAME PIC X(6).
07 CPU-PIN PIC S9(5).
Convert your opener table to identify an opener using a process handle rather than a
process ID. For example:
* D-series opener table.
01 OPENER-TABLE.
03 OPENERS OCCURS 15 TIMES.
05 CURRENT-COUNT PIC 999 COMPUTATIONAL.
05 PRIMARY-OPENER PIC X(20).
05 BACKUP-OPENER PIC X(20).
Opening and Reading $RECEIVE
You might need to convert the part of your program that opens and reads $RECEIVE
as follows:
1. Your OPEN statement for $RECEIVE should not require any changes.
2. When you read a D-series system message from $RECEIVE using the READ
statement, use a message record area that is at least 256 characters in length.
The ZSYSCOB file contains a data structure for each system message. Because
each system-message data structure is in a separate section of ZSYSCOB, you can
copy only the data structures for the messages you actually read.
3. If necessary, modify the parts of your program that process each system message.
Refer to Table 4-2 for the D-series messages that supersede C-series messages.
4. Your CLOSE statement for $RECEIVE should not require any changes.