Pathmaker Programming Guide

Modifying Requester/Server Pairs
Advanced Pathmaker Programming Topics
9–54 067868 Tandem Computers Incorporated
Modifying
Requester/Server Pairs
Some modifications require adding code both to a requester copy library and to the
service Custom Source File. This subsection discusses some of the most common
reasons that you might want to modify a requester/server pair. The topics covered in
this subsection include:
Using Pathmaker pseudofields
Using reason codes (T9154-REASON-CODE)
Creating screens that display value lists
Using Pathmaker
Pseudofields
A pseudofield is a Pathmaker defined screen element used to display or send values
that do not have DDL definitions. You use pseudofields either in the Screen Painter or
in an IPC definition. A pseudofield becomes part of the requester’s context when you
use it in the Screen Painter or part of the IPC data structure when you use it on the IPC
Definition screen.
The Pathmaker pseudofields are:
@ADVISORY Contains the most recent advisory message generated by
the application.
@ADVISORY is automatically included on the application
screen when you create an application and cannot be
deleted.
@CURRENT-PAGE Contains the page number in the current requester’s
screen.
@CURRENT-PAGE is always part of the screen when you
create an application screen, but you can delete it and add
it back later.
@CURSOR-FIELD Contains either the screen field name or the point field
name where the cursor was positioned when you invoked
the service.
You cannot display @CURSOR-FIELD on the application
screen; you can only use @CURSOR-FIELD in an IPC
definition.
@CURSOR-POSITION Contains either the reference field name or the point field
name where the cursor was positioned when you invoked
the service.
You cannot display @CURSOR-POSITION on the
application screen; you can only use @CURSOR-
POSITION in an IPC definition.
@DATE Contains the current date, according to the system clock.
You can add @DATE to the application screen by using
the Screen Painter.