Pathmaker Reference Manual

IPC Definition Screen
Pathmaker Screens
1–42 067869 Tandem Computers Incorporated
Request Reference Object
Enter an ordered list of the data elements to be sent to the service.
Each Request Reference Object you enter must be a DDL definition, DDL record,
NonStop SQL table object name, valid alias name, or pseudofield name.
Table object or alias names cannot match any name used in the Logical File Name
column of the Logical File Entries screen.
If you enter a table object name in either this column or the Copy Of column, the
Pathmaker product automatically marks the service as containing embedded SQL.
Pseudofields can be passed to services, but cannot be returned from the service to the
requester.
The @ADVISORY pseudofield is automatically included in the IPC header generated
by the Pathmaker product, so do not include it in your message.
All other pseudofields must be explicitly included in the IPC message.
@CURRENT-PAGE
@CURSOR-FIELD
@CURSOR-POSITION
@DATE
@LOGICAL-TERMINAL
@PAGE-COUNT
@PHYSICAL-TERMINAL
@TIME
See the Screen Painter and the Pseudofield Partial screens in this manual for details
about these pseudofields.
Copy Of
Using an assumed name, or alias, for a reference object allows you to use more than
one copy of the same reference object as an IPC parameter.
To define an alias, enter a valid name for the language you are using (COBOL85 or C)
into the Request Reference Object column and the actual name of the reference object
into the corresponding Copy Of column. Reference objects named in the Copy Of
column must be DDL definitions, DDL records, or NonStop SQL table object names.
Pseudofields cannot be used here.
If you are not using an alias, leave the Copy Of column blank.
If you enter a table object name in either the Copy Of column or in the Request
Reference Object column, the Pathmaker product automatically marks the service as
containing embedded SQL. You must create the table object name on the SQL Table
Registration screen before using this screen.