Pathmaker Programming Guide

Modifying Requester/Server Pairs
Advanced Pathmaker Programming Topics
9–60 067868 Tandem Computers Incorporated
The Custom Source File should contain code that moves a value to T9154-REASON-
CODE, depending on the error:
?SECTION T9PR-UPDATE-TABLE
.
.
.
if customer ID is invalid
MOVE 1 TO T9154-REASON-CODE OF T9154-REPLY.
if order ID is invalid
MOVE 2 TO T9154-REASON-CODE OF T9154-REPLY.
if any other problem
MOVE 3 TO T9154-REASON-CODE OF T9154-REPLY.
.
.
.
The requester copy library should contain code to handle the reason code that you
returned:
?SECTION USER-POST-F4 , TANDEM
*
* Screen field name for customer ID is CUST-ID-FN.
* Screen field name for order ID is ORDER-ID-FN.
*
SET NEW-CURSOR AT CUST-ID-FN, ORDER-ID-FN
DEPENDING ON T9154-REASON-CODE.
*
Creating Screens That
Display Lists
Most applications have at least one screen dedicated to displaying a list of values. The
Pathmaker product itself has many examples of such a screen. One example, the
Requester Value List screen, lists requesters that have been added to the project.
Values list screens can only display a limited number of the total records in a file at
one time on a screen. The Requester Value List screen, for example, can display up to
14 requester names at a time on the screen. If more requesters exist, you need to press
a function key to list the next set of requesters on the screen.
These requirements mean that when you create a screen that displays lists you can:
Create an array to display the list on the screen. You create the array by using the
OCCURS clause in DDL.
Create two services: one to LIST the FIRST set of values and one to LIST the NEXT
set of values.
This manual provides two examples that illustrate how to create screens that display
lists. “Creating Tabular Screens” under “Additional Considerations for Coding
NonStop SQL Services” in Section 4 shows a very simple version of service code that
can display a list.