Pathmaker Programming Guide

Generating Requesters
Creating Requesters
5–42 067868 Tandem Computers Incorporated
If the Pathmaker product does not encounter any errors during generation or
compilation, the message Generation successful is displayed in the Last
Attempted Generation Message field the next time you visit the Requester
Generation data screen.
Files Used to Generate a
Requester
To generate the SCREEN COBOL source code for a requester, the Pathmaker product
uses information from the project catalog and from the requester skeleton file. The
requester skeleton file is a file provided by Tandem containing SCREEN COBOL code
plus special skeleton code. The requester skeleton provides the framework for the
requester.
To compile the source code into SCREEN COBOL object code, the Pathmaker product
uses three files:
The requester source code file (the file where you enter your SCREEN COBOL
program)
The requester source code file is the file you specify on the Requester Generation
Data screen. If you do not specify a requester source code file on the Requester
Generation Data screen, the Pathmaker product creates a temporary file to hold
the requester source code.
A file containing the standard Working-Storage and the Environment division
(T9154CPY)
T9154CPY is a file supplied by Tandem for requester generation.
A requester copy library (optional)
The requester copy library is a file that the Pathmaker product creates if you
supply a file name in the Copy Library field on the Requester Generation Data
screen. You can use a requester copy library to write SCREEN COBOL source
code that the Pathmaker product copies in at certain preselected points in the
requester. The Pathmaker product places the compiled object code into the
application’s SCREEN COBOL object library files (POBJCOD, POBJDIR,
POBJSYM).