Pathmaker Programming Guide

New and Changed Information
067868 Tandem Computers Incorporated v
Pathmaker Full Screen
Interface Changes
Seven new screens have been added to the Pathmaker full screen interface and several
existing screens have been modified to support the new product features for Release 3.
Refer to the screen descriptions in the Pathmaker Reference Manual for more
information.
New Auditing Requirement
for Pathmaker Catalogs
The Pathmaker product for Release 3 requires that project catalogs be created on or
imported to disk volumes that are audited by the Transaction Monitoring Facility
(TMF) product. An existing Pathmaker project can be converted to Release 3 only if
the catalog for that project resides on an audited volume. Refer to the PMPROJECT
utility in the Pathmaker Reference Manual for more information.
Requirement for DEFs and
RECORDs Used in
C Services
The Pathmaker product requires DEFs and RECORDs used in C services to be
compiled by DDL with the CFIELDALIGN_MATCHED2 command. As a
consequence of this requirement, field alignment of existing DEFs and RECORDs
could change when they are recompiled with the CFIELDALIGN_MATCHED2
command, making them incompatible with services, clients, requesters, and database
files that use old versions of the DEFs and RECORDs.
Pathmaker Utility
Enhancements
The enhancements to the Pathmaker utilities for Release 3 are summarized in the
following list. Refer to the appropriate utility in the Pathmaker Reference Manual for
more information.
The PMINSTAL utility has been enhanced to allow utility process configuration
for the C compiler, to provide a cleanup option for removing unneeded software
distribution subvolumes, and to properly secure the installation files.
The PMPROJECT utility allows you to specify a static execution priority for a
Pathmaker project. (Execution priority can be either static or dynamically
determined.) In addition, you can designate a swap volume for each Pathmaker
project.
The PMPROJECT utility INSTALL option now generates a master Pathway
configuration source file and subordinate source files for the target application’s
Pathway TCP, program and server object definitions. A source file that can
contain custom Pathway object definitions and commands is also generated. This
new approach allows most of an application’s Pathway configuration information
to be regenerated when changes are made to an application without disturbing the
custom Pathway object definitions and commands you have defined.
The PMPROJECT INSTALL command now uses the Pathmaker name of an initial
requester (if it is 15 characters or less) as the Program Name in the Pathway
configuration file for the generated application.
PMPROJECT now provides an INFO command that you can use to list
information about a project.
The PMPROJECT utility provides a CONVERT option that can be used to convert
a Release 2 (C20, C30, C31, or D10) Pathmaker project to Release 3 (D20). An
existing Pathmaker project can be converted to Release 3 only if the catalog for that
project resides on an audited volume.