Pathmaker Programming Guide

Installing an Application in the Production System
Finishing and Installing the Application
7–12 067868 Tandem Computers Incorporated
Installing an
Application in the
Production System
To install an application in the production environment, you duplicate object files and
startup files to the production system, alter the startup files as needed, create the
production SQL database (if necessary), then run the startup files.
This process is described in the next two subsections.
Steps for Installing a
Production Application
The steps for installing an application produced with the Pathmaker product are as
follows:
1. Use DUPCODE to move the application’s server object files and the help database
files. DUPCODE is a File Utility Program (FUP) source code file generated by the
PMPROJECT INSTALL command. You can use DUPCODE to move the generated
application’s files to a production system. DUPCODE moves the following files:
Server object files
Requester object files (POBJCOD, POBJDIR, and, if it exists, POBJSYM)
If the application contains SQL DB requesters, the SQL standard server
(SQLGS) and the SQL standard server message files (DTCMAPS and
TEXTFILE)
If the application contains Enscribe DB requesters, the Enscribe standard
server (DBSERVER)
Help server (HELPSRVO)
Help database files (HELPREQ, HELPPOS, HELPTXT, and HELPALT0)
Help utility (HELPUTIL)
The POET mapping server (MAPSRVO)
POET files (PMSGP and PMSVC)
DUPCODE also alters the alternate key file name, HELPALT0, in the base file
labels stored in HELPTXT and HELPREQ to point to the new location.
Note Files for use with applications developed using the Pathway Open Environment Toolkit (POET) product
are included in the Pathmaker product whether or not you are using POET. If you are not using POET,
you can ignore these files or remove references to them wherever they appear.
2. Use FUP DUP to copy the Pathway configuration files (PATHCNFG, PATHPRGS,
PATHSVRS, PATHTCPS, and PATHUSER), the Pathway cold start file
(PATHCOLD), the Pathway cool start file (PATHCOOL), and, for applications that
access NonStop SQL data, the SQL compilation file (SQLCODE). These files
should be modified for use in the production environment.
For applications that access a NonStop SQL database, perform these additional steps:
3. If you are creating a new SQL database, use FUP DUP to copy the SQL DDL
source file to the production system.