SCT Application System Tape Installation

Panvalet Library Loading

There are several different functions necessary when loading the Panvalet libraries in the test environment. Specifically, the following must be done:

These will each be discussed in the order they should be done. All JCL mentioned to help in these tasks are in the ISP32 Panvalet library.

Load Source
The SCT installation process creates a source library. This should go into the normal test Panvalet source library (ISP32). This is accomplished by running the following jobs:

IALOADS1
This job should point to the appropriate source PDS. It then creates a file that contains all of the source members in it.
IALOADS2
This takes the input file from IALOADS1 and adds ++INCLUDE statements necessary for Panvalet operation. This converts the source using the COPY REPLACING option format. There are two parameters for the job. The first is your initials. The second is a brief description of the process (e.g., Load SIS+). These two pieces of information are used when an initial change log is created for Cobol and Assembly members. A single file is output that contains all members from the original PDS in a format ready to add to a Panvalet library.
IALOADS3
This job takes the output file from IALOADS1 and inserts it into the Panvalet library you specify in the JCL.

Possible problems:

Insert Errors
This process assumes that members do not already exist in the target Panvalet library with the same name as those being added. If this happens, you will have to manually update those members which fail.
Panvalet Errors
The Panvalet insert process can sometimes experience errors. Certain characters in the data stream can cause Panvalet to think it has all of a certain member. The subsequent statements in that member from the input stream will not be processed and will generate error messages. Normally this happens on members which contain a listing of all changes being delivered. In such a case, the errors can be ignored. If it happens to programs or data, the members will have to be manually corrected.

Load JCL
This is also a 3 step procedure virtually identical to the previous step. It consists of:

IALOADJ1
This unloads the specified JCL PDS and puts all members into a single file.
IALOADJ2
This converts the file from IALOADJ1 into a file ready to load JCL into Panvalet.
IALOADJ3
As with IALOADS3, this loads the JCL members as converted in IALOADJ2 into the specified Panvalet library. Similar errors may occur.

Load DB2 Bindings
Bindings should be loaded into ISPOO.SCT.xxxx.BINDCNTL, where xxxx is TEST or INST. Two members from the DB2INST library should also be loaded, namely DSNCMD and DSNEND.

Before loading bindings, delete the old bindings in the BINDCNTL library for the system being installed.

Load DB2 DCL Includes
DCLs should be generated into the ISPOO.SCT.xxxx.DCL library, where xxxx is TEST or INST. The JCL delivered by SCT deletes the library and recreates it. This should be changed to reuse the library. The DCLGEN procedure will properly replace members. Before running this procedure, old members are best deleted to make sure old members no longer needed are purged.

Copy Panvalet Comments from Previous Releases
Our standards require that anything going into production must have Panvalet comments attached. New releases of existing products will normally have a few new items, but most members already exist in production. Rather than reapply Panvalet comments manually, two jobs accomplish this task.

IALOADS4
This will extract comments from all production Panvalet libraries and put them into ++COMMENT format needed for Panvalet.
IALOADS5
This will attempt to reapply Panvalet comments to the source test library (ISP32) and the source bindings library (ISP38).

In both cases, many errors will occur since the IALOADS4 job does not selectively extract comments. Such errors can be ignored.

Load Pre-Translated CICS Copy Members
For compilation of online programs to proceed correctly, certain members (SCT calls these the CICS Copy Book) must be pre-translated. This is done in the TSO SPX environment through the SCT/DB2 option. Specifically, it is option 312 on that menu.

Load DB2 CICS Copy Members
Some DB2 programs are used in both the batch and online environments. For this to work, different copy members having the same name are required. These are delivered by SCT with different names (batch will be xxxxxx and online will be xxxxxxC). These are moved into the Panvalet Bind/Copy library in the TSO SPX environment by using the 313 option on the SCT/DB2 menu. You may specify the input member with or without the trailing C. If the C is not present, it will be automatically added.

OIT--Applications Support


Last Modified: Monday, 17-Jul-2000 15:19:55 CDT

©2000 All Rights Reserved