Pathmaker Programming Guide

Specifying CALL and SEND Parameters
Creating Requesters
5–36 067868 Tandem Computers Incorporated
Figure 5-9 shows a sample of the SCREEN COBOL code that the Pathmaker product
produces for the calling requester and for the called requester.
Figure 5-9. Sample SCREEN COBOL Code for Requester Calls
055
REQ-1
SCREEN COBOL Excerpt
REQ-2
SCREEN COBOL Excerpt
WORKING-STORAGE SECTION.
01 B-DEF
01 Z-DEF
01 K-DEF
01 L-DEF
PIC X(5).
PIC 9(8).
PIC X(3).
PIC X(7).
PROCEDURE DIVISION.
CALL REQ-2 USING
T9154-LINKAGE
B-DEF
F-DEF.
PIC X(5).
PIC X(3).
LINKAGE SECTION.
01 B-DEF
01 C-DEF
PROCEDURE DIVISION USING
T9154-LINKAGE
B-DEF
C-DEF.
01 T9154-LINKAGE.
SCREEN SECTION.
• • •
• • •
• • •
• • •
SEND Parameters You use the SEND Parameter Definition screen to specify the mapping between
reference objects or fields within reference objects from the context of this requester
and the data portion of the request and reply IPC messages of one service.
The Pathmaker product supplies most of the parameters on this screen by matching
reference objects in the requester context of this requester to reference objects in the
IPC message defined for the service. If there is not an exact match (name, length, and
type) between the Requester Context screen of the requester and the IPC reference
objects defined for the service, you will have to complete some portions of this screen
yourself.
The following points are guidelines for using the SEND Parameters screen:
Each reference object or field in the IPC message of the service must have a match
in the Requester Context screen of the requester. Matching fields do not have to
have the same name, but they must be the same length and be compatible data
types.