Pathway/iTS Web Client Programming Manual (G06.24+)
How to Compile, Build, and Maintain a Pathway/iTS
Web Client
Compaq NonStop Pathway/iTS Web Client Programming Manual—520270-001
2-6
Set Up the Build Environment in a Windows
Environment
•
Creates a make file for building the application. The name of the make file is
specified in the JMAKENV command and is copied to the application-
home/build directory as make-file.mk.
•
Sets up the environment variables used by the make file.
For example, you would run the JMAKENV file for the sample application as follows:
TACL> JMAKENV invy /usr/test/inventory invymk
JMAKENV in the sample application does the following:
•
Creates the directory /usr/test/inventory/build.
•
Creates the directory /usr/test/inventory/bin where the built objects will
be stored.
•
Copies all the necessary files from the specified Java and HTML location (in this
example, the volumes default to the same volume and subvolume as mycfg) to the
NonStop Kernel OSS directory /usr/test/inventory/build.
•
Creates a make file named invymk for building the application.
•
Sets up the environment variables used by invymk.
•
Copies invymk to the directory /usr/test/inventory/build as
invymk.mk.
Set Up the Build Environment in a Windows Environment
Pathway/iTS provides a TACL MACRO utility named JMAKENV, which is used to set
up the build environment for the converted web client.
This utility uses the MAP file that is created at the time of conversion to generate the
build environment. The MAP file is created at the same location
($volume.subvolume) from which the CONVERT command was run. The MAP file
name is composed of the first four or five SCOBOL object file characters plus the
characters MAP. For example, if the SCOBOL objects are named MYAPPCOD,
MYAPPDIR, and MYAPPSYM, then the MAP file name is MYAPPMAP.
If the build environment is on a Windows NT server, JMAKENV creates two batch files
to move the converted files to the desired environment and copy the Java class and
HTML files to a directory under OSS for deployment.
From the TACL prompt on a NonStop Himalaya, run JMAKENV as follows:
file-name
is the name of the SCREEN COBOL object-file.
Note. The user running JMAKENV must have permission to create and copy files to the
application-home directory in the OSS environment.
RUN JMAKENV file-name NT