Pathmaker Programming Guide

Adding, Modifying, or Deleting Requesters
Maintaining Pathmaker Applications
067868 Tandem Computers Incorporated 8–11
If you have added any help text, such as for a newly defined function key, you must
use FUP to move the help files to the production help subvolume.
Adding Initial Requesters
You can add initial requesters to an installed application, as well as to an application
still in the testing environment. The procedure for adding an initial requester is
similar to the procedure for adding a TRNS or MENU requester, with the following
differences:
Initial requesters are defined in the Pathmaker full screen interface by changing
the Initial Requester field on the Requester Definition screen from N to Y .
Initial requesters cannot be called by any other requester; therefore, you do not
have to regenerate any existing requesters when you add an initial requester.
You must alter the Pathway configuration file, PATHSVRS, when you add a DB
requester. Rename your PATHSVRS file and either rename or purge the other
application generated installation files. Then exit from the Pathmaker full screen
interface and regenerate PATHSVRS. See Step 10 under “Packaging Services into
New Servers” earlier in this section for more detailed information about
regenerating PATHSVRS.
Initial requesters must be added through the SET PROGRAM and the ADD
PROGRAM commands. Model your entry on other initial requester entries
generated by the Pathmaker product. In addition, you might have to increase the
values of a subset of the Pathway and TCP parameters. In a production
environment, you should also change the initial parameter on SET TERM.
The Pathway System Management Guide fully describes these parameters and the
commands for altering them.
Modifying Requesters Modifying requesters is easy if you do not plan to modify every requester in the
application. Modifying every requester in an application can be time intensive
because you must regenerate every modified requester.
When you regenerate a requester, the new version of the requester program is
automatically placed in the application’s POBJ files in the testing system. The POBJ
library will contain every generated version of the requester until you use SCUP to
specifically delete versions from the files. If you want to rerun an earlier version of the
program, use SCUP ALTER to deactivate the most recent version. If the application is
installed in a production environment, you must use SCUP to move the SCREEN
COBOL code for the requester to the production subvolume.
Every part of a requester can be changed except the requester’s name and type. These
parts include:
Requester features
Requester context
Appearance of the screen
Function key assignments