Skip to main content

Preface

This document is intended to help you install and use the CS1ULOAD function. The CS1ULOAD function is part of the INFO-RECOVERY product range (option InfoVic2).

Installing the CS1ULOAD Function

Materials​

You have received:

  1. a magnetic tape or a cartridge

  2. a printed document and the installation sheet "PRODUCT INSTALLATION JCL", which contains the JCL that must be used for a successful installation.

The magnetic tape contains two data sets:

  • the first data set is the object module of the installation program,

  • the second data set contains the object code of all modules which have to be installed.

The installation sheet contains a confidential code which will select the modules to be installed and set the expiration date if this is a product trial. If you are testing the product, the expiration date will appear on the installation sheet. When you wish to acquire a permanent license, you will be issued a permanent confidential code and will be able to reinstall the same tape.

note

The installation procedure must be run only on the machines described in the test or permanent license agreement.

Unload Procedure​

This installation takes place outside SMP/E. It only uses standard IBM utilities such as (LOADER, LINKEDIT). Please make sure that you are not using any non-standard utilities with those names. If you are, please include a STEPLIB DD statement to refer to the library that contains the actual IBM utilities.

The following steps are to be performed:

  1. Create the JCL using the installation sheet as a model. Please check that the CPU serial and model numbers on the installation sheet are correct.

  2. Insert a JOB card in front of the deck.

  3. Complete the installation sheet with the actual library names. If you are using temporary libraries, please insure that all members are copied to the final libraries when making the permanent installation.

  4. Change the name SYSDA (temporary data sets), if necessary.

  5. Mount the tape as required.

  6. Submit the job.

  7. Check the return code (return code = 0).

  8. Apply the PTFs (mandatory).

  9. Copy the product tape datasets to permanent disk as described in steps 1 and 2 of chapter " Reinstalling Without the Product Tape". These disk datasets should be excluded from migration products as they are required for CPU upgrades and Disaster Recovery procedures.

If the job has abended there will usually be a self explanatory message in the SYSOUT. If this message indicates that an abnormal return code was issued by a utility program, the explanation will usually be found at the end of the listing (SYSPRINT).

The most common errors are:

  • an erroneous confidential code,

  • a misspelled DDNAME or DSNAME,

  • an insufficient region size (see EXEC card),

  • SYSLIB dd missing (should point to a library containing ISPLINK).

PTF Processing​

Installing the PTF Processing Application​

Creating the Data Sets​

  1. When installing the PTF Management Application for the first time the user must create a library that will contain all PTFs of the product.

    The characteristics of this partitioned data set are described below:

    • LRECL=80

    • RECFM=FB

    • BLKSIZE unimportant but must be a multiple of LRECL

    • SPACE=(CYL,(1,1,80))

The dsname of this library must be entered into the PTFLIB field in the "INFOTEL PTF Management" panel described below.

  • Each time an installation or a reinstallation is performed, using the installation JCL provided with a tape, the user must create or recreate the application "log" data set for the PTFs. This sequential data set specifies which PTFs are already applied to the current version. It is important to keep this data set thus allowing the application to correctly select the PTFs that are to be applied.

    Use the PTFLOG member from the INFSAMP library to create and initialize this data set.

    The dsname of this library must be entered into the PTFLOG field of the "INFOTEL PTF Management" panel described below.

    caution

:

This data set must not be recreated if you receive a tape or a floppy disk with PTFs.

Loading the PTF Library​

If you receive a PTF by fax, create the corresponding member in the PTF library instead of following the procedure that is described below.

The PTFs are supplied in a sequential data set that may be:

  • the third data set of the product's installation tape,

  • one of the data sets of a PTF tape,

  • a floppy disk data set that is to be transferred to the "host". The floppy disk is a sequential data set (same as the third data set on tape) and must be uploaded in binary format without translation. The PTFLOAD job on INFSAMP should be used to merge it onto the PTF PDS.

The PTFLOAD member of the INFSAMP library contains the JCL to load the product's PTFs library from this sequential data set.

The SYSIN data set of this JCL is the sequential PTFs data set described above.

The SYSUT2 data set of this JCL must correspond to the PTF library described in chapter " Creating the Data Sets".

Applying the PTFs​

In order to start the PTF Management Application, use the EXEC command to execute the PTF procedure that is to be found in the INFSAMP library.

This application provides information about the PTFs that are already applied, allows the user to select the new PTFs that are to be applied and to generate the JCL that will apply the PTFs. This JCL must be submitted to apply the PTFs.

After the start-up, a configuration panel is displayed:


PTFPAN2 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- INFOTEL PTF Management \-\-\-\-\-\-\-\-\-\-\-\-\-\-- Row 1 of 21
Command ===\>
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- JCL Generation Information \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
JobCard ===\> //P390PTF JOB \' \',\'PTF\',MSGCLASS=H,NOTIFY=P390
===\>
===\>
===\>
Work Unit for temp file ===\> SYSALLDA
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- Dataset Name Information \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
Ddname Dsname
PTFLIB ===\> P390.TEST.PTF
PTFLOG ===\> P390.TEST.PTFLOG
MVSLOAD ===\> P390.TEST.LOAD
MVSLINK ===\> P390.TEST.LOAD
MVSLPA ===\> P390.TEST.LOAD
INFSAMP ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
INFPLIB ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
IMSMAC ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
IMSRES ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
IDMSSRC ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
DB2LINK ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
DB2DBRM ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
DTCLINK ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
ISPLOAD ===\> P390.TEST.LOAD
ISPCLIST ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
ISPMSGS ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
ISPPANEL ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
ISPSKELS ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
ISPTBL ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
SAPLINK ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
DMSLINK ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
TRASHMOD ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
TRASHOTH ===\> \...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
******************************* Bottom of data ********************************

Provide the appropriated values for the fields, then press PF3 to display the next panel.

  • Fill in the JOB card that will be used to generate the JCL.

  • The field "Work Unit for temp file" contains the name of the unit to be used in the generated JCL for the allocation of temporary data sets; the default value is SYSALLDA.

  • For the column "Dsname" of the "Dataset Name Information" part, you must provide the names of product's installation libraries for each ddname:

    • The ddnames PTFLIB and PTFLOG correspond to the library that contains the PTFs and to the sequential application "log" data set of the PTFs. (refer to chapter " Creating the Data Sets").

    • The ddnames TRASHMOD and TRASHOTH correspond to the backup libraries that contain the old version of members which are replaced by the PTF. These libraries have to be created before applying the PTF. TRASHMOD should be defined as PDSE if at least one of the product load-module libraries is defined as a PDSE. TRASHMOD, used for load modules, has to be created with RECFM=U. TRASHOTH, used for other member, has to be created with RECFM=FB,LRECL=80. After applying and validating a set of PTFs, the members from the backup library may be deleted (the library may be delete and recreated as well).

    • The other ddnames correspond to the product's installation JCL.

    • Only the ddnames corresponding to the products and options installed at your site should be specified.

    • The dsnames MUST NOT use quotes (' ').

Selecting the PTFs​

After saving, the panel to select the PTFs is displayed:


PTFPAN1 \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- LIST OF PTF \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- Row 1 of 3
Command ===\> Scroll ===\> CSR
IMPORTANT
Do NOT select any MAN PTF w-o first calling the technical support center.
PTF are automatically selected, just hit the \'END\' pfkey to generate the JCL.
Line Commands:
S to Select U to Unselect V for Details
Cmd Name Type State Sel Title
. UT152000 AUTO ERROR Y ERROR IN CLAUSE DELETE WHERE
. UT152002 AUTO OK N ERROR CREATING INDEX
. UT152004 MAN N INVALID RETURN CODE
. UT152005 AUTO Y S001 ABEND ON WORK FILE
******************************* Bottom of data ********************************

This panel is used to select the PTFs that are to applied, either individually (line commands) or by group (command field). Only the PTFs that may be applied to the product and to the options that are installed on your site or that are already applied, are displayed.

Press PF3 to obtain the generated JCL.

There are two types of PTFs: the "automatic" that apply to all installations, and the "manuals" that allow or suppress a special function and that are peculiar to one or several sites.

By default, all "automatic" PTFs not yet applied will be selected. The "manual" PTFs must be selected individually.

The status OK is assigned to PTFs that are already applied. These PTFs are not selected automatically.

caution

The selection or the deselection of a PTF leads to a selection or a deselection of all PTFs that are related ("PreReq"). This means that the deselection of a PTF being followed by a selection of the same PTF may remove the application of some PTFs.

After having selected the PTFs, the generated JCL is displayed. Just submit this JCL to apply the PTFs.


****** ***************************** Top of Data ******************************
000001 //P390PTF JOB \' \',\'PTF\',MSGCLASS=H,NOTIFY=P390
000005 //* \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
000006 //* PTF: UT152000
000007 //* TITLE: ERROR IN CLAUSE DELETE WHERE
000008 //* \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
000009 //ERROR EXEC PGM=IEBGENER
000010 //SYSPRINT DD SYSOUT=*
000011 //SYSIN DD DUMMY
000012 //SYSUT2 DD DISP=MOD,DSN=P390.TEST.PTFLOG
000013 //SYSUT1 DD *
000014 UT152000 ERROR
000015 /*
000016 //P152000A EXEC PGM=AMASPZAP
000017 //SYSPRINT DD SYSOUT=*
000018 //SYSLIB DD DISP=SHR,DSN=P390.TEST.LOAD
000019 //SYSIN DD *
000020 NAME INFREORG ABCDEF
000021 VER 001B 0000,0000
000022 REP 001B 0010,0020
000023 CHECKSUM 03214560
000024 /*
000025 //ABEND EXEC PGM=XXXXXXXX,COND=(4,GE,P152000A)
000026 //P152000B EXEC PGM=AMASPZAP
000027 //SYSPRINT DD SYSOUT=*
000028 //SYSLIB DD DISP=SHR,DSN=P390.TEST.LOAD
000029 //SYSIN DD *
000030 NAME AUTREOMN ABCDEF
000031 VER 001B 0000,0000
000032 REP 001B 0010,0020
000033 CHECKSUM 03214560
000034 /*
000035 //ABEND EXEC PGM=XXXXXXXX,COND=(4,GE,P152000B)
000036 //OK EXEC PGM=IEBGENER
000037 //SYSPRINT DD SYSOUT=*
000038 //SYSIN DD DUMMY
000039 //SYSUT2 DD DISP=MOD,DSN=P390.TEST.PTFLOG
000040 //SYSUT1 DD *
000041 UT152000 OK
000042 /*
000043 //* \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
000044 //* PTF: UT152005
000045 //* TITLE: S001 ABEND ON WORK FILE
000046 //* \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
000047 //ERROR EXEC PGM=IEBGENER
000048 //SYSPRINT DD SYSOUT=*
000049 //SYSIN DD DUMMY
000050 //SYSUT2 DD DISP=MOD,DSN=P390.TEST.PTFLOG
000051 //SYSUT1 DD *
000052 UT152005 ERROR
000053 /*
000054 //P152005A EXEC PGM=AMASPZAP
000055 //SYSPRINT DD SYSOUT=*
000056 //SYSLIB DD DISP=SHR,DSN=P390.TEST.LOAD
000057 //SYSIN DD *
000058 NAME INFREORG ABCDEF
000059 VER 001B 0000,0000
000060 REP 001B 0010,0020
000061 CHECKSUM 03214560
000062 /*
000063 //ABEND EXEC PGM=XXXXXXXX,COND=(4,GE,P152005A)
000064 //P152005B EXEC PGM=AMASPZAP
000065 //SYSPRINT DD SYSOUT=*
000066 //SYSLIB DD DISP=SHR,DSN=P390.TEST.LOAD
000067 //SYSIN DD *
000068 NAME AUTREOMN ABCDEF
000069 VER 001B 0000,0000
000070 REP 001B 0010,0020
000071 CHECKSUM 03214560
000072 /*
000073 //ABEND EXEC PGM=XXXXXXXX,COND=(4,GE,P152005B)
000074 //OK EXEC PGM=IEBGENER
000075 //SYSPRINT DD SYSOUT=*
000076 //SYSIN DD DUMMY
000077 //SYSUT2 DD DISP=MOD,DSN=P390.TEST.PTFLOG
000078 //SYSUT1 DD *
000079 UT152005 OK
****** **************************** Bottom of Data ****************************

Each PTF starts with an ERROR step informing the LOG data set that the PTF was not correctly applied (in case a problem occurs during its application).

Each step of the PTF (AMASPZAP, IEBUPDTE or IEWL) is followed by an ABEND step being executed in case an error occurs and that leads to a S806 abend that stops the execution of the JCL.

The PTF ends with an OK step informing the LOG data set that the PTF was correctly applied.

Just submit this JCL to apply the PTFs.

If an error occurs during the application of a PTF, the job will stop with an "abend" and no more PTFs will be applied. In this case you must view the output of this job, correct the problem and put the product's elements in the same state as before the abend. Just modify your JCL to restart from this point or generate another JCL to apply PTFs (the PTFs that were already applied will no longer be selected automatically).

important

Once all PTFs have been applied, display the PTFLOG data set and search for the instructions "INSTR" that inform you about further steps to do:

Example:


XX100022 OK 2 Jul 2002
XX100022 INSTR You must rebind the plan INFOTEL
XX100022 INSTR Submit the JCL in BINDPLAN member of INFSAMP library

Installing on an Unauthorized or Backup CPU​

Any permanent licensed version of the product will install and run on any CPU for a number of days known as the backup extension (BE) days. The BE days are determined by Infotel and the customer at the time of licensing.

BE days are granted to allow for initial processing in emergency situations (e.g. - disaster recovery). If processing must extend beyond the BE days, contact your Infotel representative for an extension or for permanent licensing on a new CPU.

warning

The Infotel product is not operable on any new CPU unless the installation procedure is performed. You cannot use IEBCOPY or any other utility to make the product available on a unauthorized CPU. You must, even to operate for the BE days, follow the "Installation procedure" or the "Reinstalling Without the Product Tape" procedure which follows.

Reinstalling Without the Product Tape​

This procedure should be used in preparation for disaster recovery, or in the event of a CPU upgrade involving a serial number change. In general, it is a procedure for eliminating the need for a product tape when the product must be run on a CPU other than the one for which it was originally licensed.

  • Copy the following three data sets to permanent disk:

    {wrapper="1" role="DL"}

    • PRODUCT INSTALLATION JCL

      This JCL is created by the user from the Product Installation JCL provided by Infotel. The JCL should include the confidential code (in the EXEC statement).

    • INFO.SYSLIN

      This is the first of two data sets on the product tape. It is referenced by the ddname SYSLIN in the Product Installation JCL.

    • INFO.INSTALL

      This is the second of two data sets on the product tape. It is referenced by the ddname INSTALL in the Product Installation JCL.

      INFO.SYSLIN and INFO.INSTALL may be copied by standard utilities such as IEBGENER or IEBCOPY.

  • Modify the Product Installation JCL to reflect the disk location of INFO.SYSLIN and INFO.INSTALL.

The above steps should be completed immediately after permanent licensing is attained.

To install the product modules on a new or currently unauthorized CPU (as in the case of disaster recovery), execute the Product Installation JCL prepared in step 2 above. The product modules will install for BE days as described in the previous section.

Extending the number of days of operation on an unlicensed CPU, converting the license to a new CPU, or adding a CPU is accomplished by replacing the confidential code in the Product Installation JCL.

Libraries used by CS1ULOAD

All PDS data sets that are used during the installation of INFO-RECOVERY and all DDNAMEs specified inside the installation JCL are described below.

Read-Only Libraries​

SYSLIB is the ISPF library on the site that contains the ISPLINK module. It can be concatenated with the IMS module library of the site, if you have to install the InfoRec1 product or InfoVic IMS. These libraries are used during the link phase of INFO-RECOVERY modules.

DB2LIB is the library of the site's DB2 load modules. This library is used during the link phase of the INFO-RECOVERY modules for the InfoVic DB2 or InfoRec2 product.

Write-Only Libraries​

For CS1ULOAD​

MVSLOAD is the library of the INFO-RECOVERY load modules. INFPLIB is the parmlib library that contains skeletons, panels, clists, XPROC procedures, and useful parameters for the different functions of the INFO-RECOVERY software.

For confidential code management​

MVSLOAD also contains the load-modules allowing batch management of confidential code.

INFSAMP is the library that contains JCLs and CLISTs necessary for confidential code management; they have to be customized.

ISPLOAD is the library that contains the load-modules allowing interactive management of confidential codes. This library should be concatenated in ISPLLIB.

ISPCLIST is the library that contains the start procedures for the interactive management of confidential codes. This library should be concatenated in SYSPROC or SYSEXEC.

ISPPANEL is the library that contains the ISPF panels and tutorial for the interactive management of confidential codes. This library should be concatenated in ISPPLIB.

ISPMSGS is the library that contains the ISPF messages for the interactive management of confidential codes. This library should be concatenated in ISPMLIB.

Authorizing Modules for TSO​

  • Update the active member IKJTSOnn in SYS1.PARMLIB library adding the name IPKAUTH:

    a. to the list of authorized programs (AUTHPGM NAMES),

    b. to the list of authorized programs via TSO call (AUTHTSF NAMES).

    same definition as the IEBCOPY program.

    The authorization is immediate with the ESA TSO command PARMLIB or after the next IPL.

    The syntax of the PARMLIB command is as following:

     PARMLIB UPDATE(nn)

    where nn is the value that was specified for IKJTSOnn.

or:

  • Update the member IKJEFTE8 of the SYS1.LINKLIB library adding the name IPKAUTH where the IEBCOPY is found.

    The authorization is effective at the next IPL.

note

If you are using ACF2, then authorize IPKAUTH and IPKCMD0 as TSO command processors with ACF2.

First Installation

For the first installation, follow the steps below:

  1. Unload the tape.

  2. Customize the parmlib.

  3. Define the default parmlib.

  4. Check the first installation.

  5. Generate the production environment.

If it is not the first installation of a product, bypass this chapter and go to Automatic installation. Otherwise, execute the following steps as described.

Customizing the Parmlib​

The only necessary preparation is the customization of the members of the parmlib specified in the following paragraphs. Indeed, all INFO-RECOVERY products derive site characteristics from the following members:

  • PRODUCTS describes the installed products.

  • SYSIDS describes all MVS systems using the products.

  • IMSIDS describes IMS systems using the products.

  • IMSDSGS describes the IMS data sharing groups.

  • THT describes the local time.

  • DB2IDS describes DB2 systems using the products.

  • DB2DSGS describes the DB2 data sharing groups.

  • JOBCARD generates job cards.

  • CUSTOM describes global INFO-RECOVERY parameters.

  • CTRLRUN supervises the status of CSXEXEC batch runs (this member does not need a customization for the first installation).

PRODUCTS - Products Description​

The provided products are these:

  • InfoRec is the common basis for all other products

  • InfoRec1 and/or InfoRec2 and/or InfoVic1/2 are specific products.

Use the EDIT command on the PRODUCTS member.

Type the dataset name chosen during the unload phase (MVSLOAD ddname) to update the CLOAD parameter value.

Syntax​



P0 NAME=INFOREC, INFOREC product.
FUNCTION=(CSXEXEC, Function list
\...\.....,
\...\.....),
CLOAD=cload, Current loadlib dsname.
* Dsname of the MVSLOAD library
* (if first installation)
TEST=Y/N, Test mode Y/N.
TPLIB=tplib, Test parmlib dsname.
XDATE=format Date format.
*
PV NAME=INFOVIC, INFOVIC product.
FUNCTION=(function, Function list.
\...\.....,
\...\.....)
* Comment.
P1 NAME=INFOREC1, INFOREC1 product.
FUNCTION=(function, Function list.
\...\.....,
\...\.....)
* Comment.
P2 NAME=INFOREC2, INFOREC2 product.
FUNCTION=(function, Function list.
\...\.....,
\...\.....)

{wrapper="1" role="DL"}

  • CLOAD=cload

    CLOAD= is the dsname of the load module library where the product has been copied.

  • TEST=Y/N

    Another load library or another parmlib may be indicated.

    Default parameter: N

  • TPLIB=tplib

    TPLIB= is the name of the test parmlib referred to above.

    Default parameter: NONE The value NONE indicates no test parmlib.

  • XDATE=format

    A format for dates may be indicated.

    Default parameter: DD/MM/YY

  • NAME=INFOVIC

    NAME= indicates the name of the product whose characteristics follow.

  • FUNCTION= (function,.)

    FUNCTION= indicates the specific functions of this product that are active. Leave this list as is. It should not be modified because doing so may make some functions inaccessible.



*
PV NAME=INFOVIC, Product InfoVic
FUNCTION=(CS1ULOAD, List of functions
\...\.....,
\...\.....)
* Comment.

SYSIDS - MVS System Descriptions​

You may adapt the SYSIDS member using one entry for each MVS system running the products.

Use the EDIT command on the SYSIDS member.

The product libraries do not have to be authorized and no IPL is required. Nevertheless:

  • The CSXEXEC module needs APF authorization. It is copied into a user LINKLIST library:
  • For the InfoRec2 and InfoVic2 products, some authorized load-modules also have to be copied into a LINKLIST library (see chapter Customizing the Modules).

Type the LINKLIB parameter and other necessary parameters.

Syntax​



* Comment.
S1 SYSID=sysid, MVS sysid.
SYSAFF=sysaff, job execution system.
CLASS=A, A default class for this system.
ISPMLIB=ispmlib, ISP message library dsname.
ISRMLIB=isrmlib, ISR message library dsname.
ISPTLIB=isptlib, ISP tables library dsname.
ISRTLIB=isrtlib, ISR tables library dsname.
SORTLIB=sys1.sortlib, Sort library.
LINKLIB=linklib, User linklist library for CSXEXEC.
PROCLIB=proclib, User CLISTS library.
EXECLIB=execlib, REXX programs library.
DEFIMSID=imsid, Default IMSID on this MVS.
DEFDB2ID=db2id Default DB2ID on this MVS.
* Comment.
S2 SYSID=sysid, A second entry\...
\...

{wrapper="1" role="DL"}

  • SYSID=sysid

    SYSID= is the identifier of the MVS system described by the parameters that follow.

  • CLASS=A

    CLASS= is the default class for this system. This information will be used for automatic generation of JCL.

  • ISPMLIB=ispmlib

    ISPMLIB= is the dsname of the ISP message library of ISPF for this system. A typical member of this library is ISPV01.

  • ISRMLIB=isrmlib

    ISRMLIB= is the dsname of the ISR message library of ISPF/PDF for this system. A typical member of this library is ISREI00.

  • ISPTLIB=isptlib

    ISPTLIB= is the dsname of the ISP table library of ISPF for this system. A typical member of this library is ISPSPROF.

    Default parameter: NONE

  • ISRTLIB=isrtlib

    ISRTLIB= is the dsname of the ISR table library of ISPF/PDF for this system. A typical member of this library is ISRPROF.

    Default parameter: NONE

  • SORTLIB=sys1.sortlib

    SORTLIB= is the dsname of the sortlib library for this system, used when the generated batch job uses the sort.

  • LINKLIB=linklib

    LINKLIB= is the dsname of a user LINKLIST library.

    The purpose of the linklist library is twofold:

  • It makes production JCL for products independent of a STEPLIB.

  • It is required by the standard mechanism of products for the automatic maintenance procedure.

  • PROCLIB=proclib

    PROCLIB= is the dsname of the user clists library. It is used to execute user clists before generating the JCL

    Default parameter: NONE

  • EXECLIB=execlib

    EXECLIB= is the dsname of the user REXX program library. It is used to execute user procedures before generating the JCL This library must not contain a member named SETUP.

    Default parameter: NONE

  • DEFIMSID=imsid

    DEFIMSID= is the name of the default IMS system for this MVS system.

  • DEFDB2ID=db2id

    DEFDB2ID= is the name of the default DB2 system for this MVS system.

DB2IDS - DB2 System Descriptions​

You must adapt the DB2IDS member using one entry for each DB2 system running the products. If DB2 is not used, skip this section.

Use the EDIT command on the DB2IDS member and include all required parameters.

Syntax​



* Comment.
D1 DB2ID=db2id, DB2 db2id.
ALIAS=alias, Cataloged ALIAS of FIC/IIC dsn(s).
* (must be \<= 8 characters).
PLAN=CSnPLAN, Plan to be used for products
* n-parmlib.
DB2BSDS=db2bsds, BSDS dsname to be used for this
* db2id.
DB2EXIT=db2exit, DB2 exitlib dsname (contains DSNHDECP).
DB2LIB=db2lib, DB2 loadlib dsname.
VSAMCAT=vsamcat, Cataloged ALIAS for directory dsnames.
ACCESS=access, DB2 catalog access mode SQL/QFAST/FAST
SITETYPE=sitetype, DB2 site type LOCALSITE/RECOVERYSITE
TDEVTYPE=tdevtype, ICs tape unit type used with TDEVNUM
TDEVNUM=n, number of tape units of type TDEVTYPE
to be used for FICs/IICs input data sets
CS2RECON=cs2recon, VIC recon dsname. (One per DB2)
CS2RECVO=cs2recvo VIC recon volume.
* Comment.
D2 DB2ID=DB2ID, A second entry\...
\...

{wrapper="1" role="DL"}

  • DB2ID=db2id

    DB2ID= is the identifier of the DB2 subsystem described by the parameters that follow.

  • ALIAS=alias

    ALIAS= is the catalog alias (ICF) for image copy and incremental image copy dsnames. All INFO-RECOVERY data sets of this type will begin with this ALIAS.

    The alias must be less than or equal to 8 characters;

  • PLAN=CSnPLAN

    PLAN= is the name of the unique plan of the products. The "n" character distinguishes between the different parmlibs of INFO-RECOVERY. It will automatically be created by the installation process.

  • DB2BSDS=db2bsds

    DB2BSDS= indicates the name of the BSDS for this DB2.

  • DB2EXIT=db2exit

    DB2EXIT= indicates the name of the EXITLIB for this DB2. (This library must contain the valid module DSNHDECP.)

  • DB2LIB=db2lib

    DB2LIB= indicates the name of the loadlib for this DB2.

  • VSAMCAT=vsamcat

    VSAMCAT= indicates the name of the VSAM catalog for DSNDB01.

    Default parameter: NONE

  • ACCESS=access

    ACCESS= indicates the access mode chosen to read the DB2 catalog: SQL, QFAST or FAST.

    The SQL access mode reads the DB2 catalog through the SQL statements CSQ* in the parmlib.

    In the FAST and QFAST access modes, some SQL statements are replaced by direct VSAM read access to the DB2 catalog. The QFAST access mode ensures data integrity by asking first for a QUIESCE of the catalog tablespace that will be read. The FAST access mode does not ask for a QUIESCE; data are read in the relevant VSAM cluster as they appear there since they have last been written to disk.

    Default parameter: SQL

  • SITETYPE=sitetype

    SITETYPE= indicates the value (LOCALSITE or RECOVERYSITE) of the same parameter contained in the module DSNZPARM.

    Default parameter: LOCALSITE

  • TDEVTYPE=tdevtype

    to specify the type of support (non-disk) of ICs corresponding to the input/output units which number is to be specified by the TDEVNUM parameter;

    Default parameter: 3480

  • TDEVNUM=n

    to specify the minimum number of units to be used by INFO-RECOVERY to read the Image Copy data sets (that are not on disks) (the unit type is specified with TDEVTYPE);

    Default parameter: 3

  • CS2RECON=cs2recon

    CS2RECON= is the dsname of the specific RECON data set of InfoVic. You must have a distinct InfoVic RECON for each DB2 environment. It will automatically be created by the installation process.

  • CS2RECVO=cs2recvo

    CS2RECVO= is the volume name of the InfoVic RECON.

CUSTOM​

The member CUSTOM describes the global parameters of INFO-RECOVERY. It supervises ISPF skeletons used by these products.

The execution of these product skeletons tests the variables of the CUSTOM member in order to choose its operating mode and to support these products:

  • tape management (TMS or TLMS),

  • disk management (DFHSM),

  • job management (UCC7, OPC, HS5000)

For example, if you code a tape management system, a new data set to be cataloged will be created with EXPDT=99000 (TLMS or TMS). To delete this tape data set, the "uncatlg method" will be used.

The standard JOBCARD clist uses the default values for the accounting and the MSGCLASS specified in the CUSTOM member.

Use the EDIT command on the CUSTOM member and include all required parameters.

Syntax​



* Comment.
JOBCHECK=Y/N CHECK jobs submitted by the
* Products (Y/N).
JOBWAIT=jobwait, Wait job queued time interval
* (seconds).
JOBQTIME=jobqtime, Max queue time for a job (HHMM).
PERFORM=perform, A non-swapable MVS perform group.
TAPEMSYS=tapemsys, TAPE management system.
DISKMSYS=diskmsys, DISK management system.
JOBMSYS=jobmsys, JOB management system.
UCC7PSW=, Reserved.
WORKGRP=workgrp, Default work group.
DISKGRP=diskgrp, Default disk group.
TAPEGRP=tapegrp, Default tape group.
DISKUNIT=diskunit, Dasd unit type (3350, 3380)
MAXPRIM=, Primary allocation for
* multivolume file (disk)
MAXUNIT=, Max number of disk volumes for
* one file (FIC).
TYPRUN=typrun, Clear the jobcard typrun value.
USER=user, Clear the jobcard user value.
PSW=psw, Clear the jobcard password value.
JOBNAME=jobname, Job name for the generated JCL.
RC=retcode, Return code that replaces abend 4001.
DEFACCNT=\"ACCOUNT\", Default accounting.
DEFMSGCL=defmsgcl Default MSGCLASS.

{wrapper="1" role="DL"}

  • JOBCHECK=Y/N/C

    Y means that the submitted jobs are supervised

    N means that the submitted jobs are not supervised. Nevertheless, the generated jobs will contain the CHECK steps with the timestamp of their generation and with an identification mark of the mother job (its jobname, its address space).

    C means that the jobs will not contain CHECK steps.

    The values N and C are especially useful if JCL must be retrieved from the JCLOUT data set.

    Default parameter: Y

  • JOBWAIT=jobwait

    JOBWAIT= is the waiting time for the start of a submitted job.

    Default parameter: 10 (seconds)

  • JOBQTIME=jobqtime

    JOBQTIME= is the maximum waiting time for a submitted job in the input queue.

    Default parameter: 0005 (minutes)

  • PERFORM=perform

    PERFORM= indicates a non swappable MVS performance group.

    Default parameter: blank

  • TAPEMSYS=tapemsys

    TAPEMSYS= indicates the name of the tape management system of your site (TMS, TLMS) or NONE.

    It takes into account the tape management system at your site inside the skeletons used by the different products.

    Default parameter: TLMS

  • DISKMSYS=diskmsys

    DISKMSYS= indicates the disk management system of your site (DFHSM) or NONE.

    It takes into account the disk management system at your site inside the skeletons used by the different products.

    Default parameter: DFHSM

  • JOBMSYS=jobmsys

    JOBMSYS= is the name of the job management system of your site (UCC7, OPC, HS5000) or NONE.

    Default parameter: UCC7

  • UCC7PSW=

    UCC7PSW= is the identifier used with job management system UCC7.

  • WORKGRP=workgrp

    WORKGRP= is a default disk allocation unit for the work data sets of the generated jobs.

    Default parameter: SYSALLDA

  • DISKGRP=diskgrp

    DISKGRP= is a default disk allocation unit for the disk data sets generated by INFO-RECOVERY.

    Default parameter: SYSDA

  • TAPEGRP=tapegrp

    TAPEGRP= is a default tape allocation unit for tape data sets generated by INFO-RECOVERY.

    Default parameter: 3480

  • DISKUNIT=diskunit

    DISKUNIT= is a DASD unit type.

    Default parameter: SYSALLDA

  • TYPRUN=typrun

    TYPRUN= changes the TYPRUN parameter of the generated job card; see JOBCARD below.

    Default parameter: blank

  • USER=user

    USER= changes the USER parameter of the generated job card; see JOBCARD below.

    Default parameter: blank

  • PSW=psw

    PSW= changes the PASSWORD parameter of the generated job card; see JOBCARD below.

    Default parameter: blank

  • JOBNAME=jobname

    JOBNAME= indicates the name of the generated job for all executions of INFO-RECOVERY. For a more complex use, see JOBCARD below.

    Default parameter: blank

  • RC=retcode

    RC= provides the possibility to issue a return code instead of an abend 4001. Specifying a value of zero means that no conversion is required.

    Default parameter: 0

  • DEFACCNT=ACCOUNT

    DEFACCNT= forces the account of the generated job card. This parameter must be coded between two quotation marks ("), and should include the commas if any. See JOBCARD below.

  • DEFMSGCL=defmsgcl

    DEFMSGCL= is the default MSGCLASS of the generated job card. It must be a class of type 'HOLD'. See JOBCARD below.

    Default parameter: X

JOBCARD​

Use the EDIT command on the JOBCARD member.

This CLIST is used when creating a JOB card during automatic generation of JCL.

The values used by this CLIST are initialized from the ISPF variables found in the CUSTOM member.

You can customize the JOBCARD CLIST. To this effect, you can use the TYPRUN, USER, PSW, DEFACCNT, and DEFMSGCL parameters, defined in the member CUSTOM of the parmlib.

note

Another CLIST called JOBCARD0 is included in the PARMLIB. It uses the jobname of the generating job instead of the TSO userid to generate the jobname of the generated job. To use it, it suffices to rename it into JOBCARD.

Clist JOBCARD​



PROC 0
/*\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--*/
/* JOBCARD INSTALLATION CLIST EXIT */
/* */
/*\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--*/
/* */
/* THE JOBCARD CLIST DERIVES DEFJOB FROM THE JOBNAME IN BATCH MODE */
/* ADDING \"\$\",\"@\" OR \"0\"(AFTER TRUNCATION TO 7 CHARS IF NECESSARY) */
/* */
/* USER CAN DEVELOP ANY LOGIC RELATIVE TO &ZUSER VARIABLE FOR */
/* ANOTHER SETTING OF DEFJOB, ACCOUNT OR MSGCLASS VARIABLES. */
/* */
/* CAUTION : ACCOUNT MUST BE CODED EXACTLY TO AVOID INSTALLATION */
/* PROBLEM. USE STATEMENT &STR(\....) TO MAKE SURE THAT*/
/* ANY CHARACTER STRING WILL BE ACCEPTED. */
/* */
/* VARIABLES SYSID, IMSID, CLASS AND BATCH CAN BE USED IF */
/* NECESSARY. BATCH=Y/N INDICATES THE TYPE OF &ZUSER. */
/* */
/* DON\'T CHANGE SYSID, IMSID OR BATCH. CLASS MAY BE MODIFIED. */
/* */
/* THE STRUCTURE OF THE RESULTING JOBCARD WILL BE : */
/* */
/* //&JOBNAME JOB &ACCOUNT.MSGCLASS=&MSGCLASS,CLASS=&CLASS, */
/* // NOTIFY=&NTUSER(,TYPRUN=&TYPRUN) */
/* */
/* (SEE CSKJOBC SKELETON.) */
/* */
/*\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--*/
/**/
ISPEXEC VGET (DEBUG) ASIS
IF &DEBUG = Y -
THEN DO
CONTROL MSG LIST CONLIST SYMLIST
END
/**/
ISPEXEC VGET (DEFMSGCL DEFACCNT DEFJOBP) ASIS
ISPEXEC VGET (ZUSER SYSID IMSID CLASS BATCH) ASIS
/**/
IF &BATCH = Y -
THEN DO
SET DEFENDC = &Z
SET DEFJOB = &DEFJOBP
IF &LENGTH(&DEFJOBP)=8 THEN DO
SET DEFENDC = &SUBSTR(8:8,&DEFJOBP)
SET DEFJOB = &SUBSTR(1:7,&DEFJOBP)
END
IF &DEFENDC = &STR(\$) -
THEN DO
SET DEFJOB = &DEFJOB.&STR(à)
END
ELSE DO
IF &DEFENDC = &STR(à) -
THEN DO
SET DEFJOB = &DEFJOB.&STR(0)
END
ELSE DO
SET DEFJOB = &DEFJOB.&STR(\$)
END
END
END
ELSE DO
SET DEFJOB = &STR(&ZUSER)R /* A DEFAULT JOBNAME */
END
/**/
SET MSGCLASS = &DEFMSGCL /* MSGCLASS */
IF &DEFACCNT = THEN SET ACCOUNT = /* YOUR JOB ACCOUNT */
ELSE SET ACCOUNT = &STR(&DEFACCNT,)
/**/
ISPEXEC VPUT (DEFJOB ACCOUNT MSGCLASS CLASS) ASIS

CTRLRUN​

CTRLRUN checks the status of CSXEXEC batch jobs.

This parmlib member does not have to be customized during the first installation. If that is the case, skip to the following step.

CTRLRUN member has two purposes:

  • a default user library can be declared for batch INFO-RECOVERY jobs. Members in this library can be user members, or members masking members with the same name of the parmlib during the execution.

    Note that user libraries may not be piled in this way: the parameter USERLIB is ignored when found in a USERLIB.

  • an "out of service" option of INFO-RECOVERY can, if needed, supersede, without JCL modifications, all batch steps CSXEXEC: they do nothing and give a return code of zero.

    note

:

The NULL parameter typed in USERLIB member CTRLRUN is taken into account in batch CSXEXEC steps (NULL=Y specified in the USERLIB nullifies batch CSXEXEC steps).

Syntax​



* Comment
NULL=N, NULL mode : Y/N
USERLIB=NONE dsname of a batch USERLIB

{wrapper="1" role="DL"}

  • NULL=N

    Setting the NULL parameter to Y means that all CSXEXEC batch steps do nothing with a zero return code.

    This bypasses the INFO-RECOVERY function without JCL modifications.

    Default parameter: N

  • USERLIB=userlib

    USERLIB= is the dsname of a USER parmlib.

    Default parameter: NONE

Customizing the Modules​

Customizing the CSXEXEC Module​

Use the EDIT command on the £CSJXINS member of the parmlib.

Modify PARMLIB, LOADLIB, and LINKLIB variables so that they correspond to what you have specified during installation.

Modify the job card.

Submit the job.

Copying the InfoRec2 and InfoVic2 Modules into the LINKLIB​

note

This step must only be done if you are installing InfoVic2 and/or InfoRec2.

Use the EDIT command on the £CSJXIN1 member of the parmlib.

Modify LOADLIB, LINKLIB variables so that they correspond to what you have specified during installation.

Modify the job card.

Submit the job.

Copying the InfoRec1 and InfoVic1 Modules into the LINKLIB​

note

This step must only be done if you are installing InfoVic1 and/or InfoRec1.

Use the EDIT command on the £CSJXIN2 member of the parmlib.

Modify LOADLIB, LINKLIB variables so that they correspond to what you have specified during installation.

Modify the job card.

Submit the job.

Refreshment of the LLA​

Perform a refresh LLA by issuing the following console command

 F LLA,REFRESH

Checking the Installation Process​

To check that the first part of the installation is OK, execute the following verification procedure under TSO/ISPF:

  1. Select option 7: "Perform Dialog Test" of the primary ISPF/PDF panel.

  2. Select option 1: "Invoke dialog functions/selections menus".

  3. Initialize the following fields:

             PGM ===> CSXEXEC
       NEWAPPL   ===> YES                            ID    ===> CSX

    Press ENTER.

  4. Press ENTER to obtain the primary INFO-RECOVERY panel.

  5. To check that the installation is correct, select all authorized options in the primary panel. Consult help panels with the PF1/13 keys.

  6. The use of InfoRec under TSO/ISPF is now checked. The UPGRADE function defined above will check the correct execution of batch processing.

Generating the Products Environment​

Use the general installation menu (see chapter General Installation Menu) to generate the products environment.

The INSTALL function will produce and automatically submit the JCL used to generate the environment of the requested product.

This task is performed using ISPF skeletons.

Use TEST=Y to check the JCL before a real execution.

Use TEST=N to submit the JCL.

After this operation, the products are installed.

Generation of the production environment​

To generate the production environment, the following steps must be performed:

  1. Apply the UPGRADE function to generate the production libraries and the production environment (A environment) - see: UPGRADE - Upgrade.

  2. Apply the APPLY function - see: APPLY - Default parmlib.

The production environment is now active.

Exit the product, reconnect, select the installation panel, and verify that the default environment is now the production one.

Automatic installation

To install a new version, or a new product, execute the following steps:

  1. Unload the tape in test libraries.

  2. Declare the new parmlib library (created in the above step) as a user library in the user configuration menu (option C in the general INFO-RECOVERY menu

  3. Execute the RECEIVE function (see: RECEIVE - Receiving a tape).

  4. Customize the parmlib if necessary (see: Customizing the Parmlib).

  5. Generate the products environment, if necessary (see: Generating the Products Environment).

  6. Test the new version (as described below),

  7. Execute the UPGRADE function (see: UPGRADE - Upgrade).

Tests of the new version​

Several users may test the new version. This may be done using the parmlib management panel which allows substitution of the current environment with the test environment for these users.

The TEST parameter of the PRODUCTS member of the parmlib facilitates the process: a test environment may be attached to the production environment.

Use the EDIT command on the PRODUCTS member of the current environment, and, for the InfoRec product:

  • Replace the TPLIB parameter with the name of the test parmlib.

  • Replace the TEST parameter with the Y value.

Now, all users of the production environment will have access to the test environment.

No other modification is necessary.

After the validation of a new version, it is necessary to replace the production environment with the test one: use the UPGRADE function (see: UPGRADE - Upgrade).

The production environment will be created automatically with the UPGRADE mechanism.

General Installation Menu

Once the installation of InfoRec is finished, select option I (INSTALL) from the general menu of INFO-RECOVERY. The general menu for installation and maintenance services is displayed:


INFO-RECOVERY - Installation Panel
COMMAND ===\>
typrun option ===\>
job check \....===\>
Default parmlib \.....
Test parmlib \.....
Current parmlib \.....
O COPY - Copy the members of parmlib 1 INFOREC1 Installation
R RECEIVE - New level of INFOREC products 2 INFOREC2 Installation
C APPLY - Change the default parmlib 3 INFOVIC Installation
U UPGRADE - Upgrade the current parmlib
M RESET - Reset the members parmlib

Specify the letter of the service you want to use. To exit, press PF3/15 (End).

After a service has been selected, an ISPF panel displays a list of libraries that were modified. Select option TEST (Y/N) to view or submit the JCL generated by the service.

The option TYPRUN (H/S) on the general installation menu allows the user to HOLD or SCAN the installation jobs. If this parameter is blanked out, the jobs will be submitted for execution.

The option JOBCHECK (Y/N) allows the user to activate or deactivate control of the submitted jobs. The default value for this option is specified in the CUSTOM member of the parmlib.

Installing InfoRec2​

The InfoRec2 Installation Service allows the user to generate the InfoRec2 product's environment. Select option 2 on the general installation menu to display the following panel:


INFO-RECOVERY - INFOREC2 Installation Panel
COMMAND ===\>
Test option ===\>
Install parmlib \.....
Db2id \...\...\...\...===\> (specify a db2id or ALL)
Press Enter to validate installation request or PF3/15 for exit

This service generates JCL to automatically create, for each DB2 sub-system, the application plan used by INFO-RECOVERY.

The DB2IDS member of the current parmlib provides the description of all DB2 sub-systems (see: DB2IDS - DB2 System Descriptions).

Use this service again if you need to modify the product's plan name associated to a DB2 subsystem, or to rebind the plan if an upgrade invalidates the former bind. The user requesting this service must be authorized to execute a bind in the specified DB2 sub-systems. No authorization for DB2 databases is necessary.

Verification of the installation of InfoRec2​

All InfoRec2 functions are available after this step and may be tested as follows:

  1. Select option 2 (InfoRec2) on the primary INFO-RECOVERY menu.

  2. Select option 1 (FIC) of InfoRec2 menu.

    After the display of the copyright of the function, enter the following parameters corresponding to your site:

     TS=(ABC*),TEST=Y

    Use PF3/15 to exit the menu.

Installing InfoVic​

The InfoVic Installation Service allows the user to install the InfoVic product. Selecting option 3 on the general installation menu activates InfoVic and displays the following panel:


INFO-RECOVERY - INFOVIC Installation Panel
COMMAND ===\>
Test option ===\>
Install parmlib \.....
Imsid \...\...\...\...===\> (specify an imsid or ALL)
Create VIC recon..===\> (Y/N)
Db2id \...\...\...\...===\> (specify a db2id or ALL)
Create VIC recon..===\> (Y/N)
Press Enter to validate installation request or PF3/15 for exit

This option generates JCL to automatically create the RECON-VIC and/or PSBs defined for each IMS or selected DB2 system. This JCL includes IDCAMS DELETE/DEFINE steps; the new RECON-VIC will scratch and replace any older data set with the same name.

Member IMSIDS of the current parmlib provides the description for all IMS systems (CS1RECON and CS1RECVO parameters).

Member DB2IDS of the current parmlib provides the description for all DB2 systems (CS2RECON and CS2RECVO parameters).

Use this service again to modify the name of a PSB or of a RECON-VIC, if necessary.

Checking the InfoVic Installation Process​

All InfoVic functions are available as soon as the IMS generation includes the generated deck (this applies to the CS1VIC function).

Yet some functions are already available at this point and the correct installation of InfoVic may be tested as follows:

  1. Select option V (InfoVic) from the primary INFO-RECOVERY menu.

  2. Select option 1 (Virtual image copy) from the InfoVic menu.

    After the message "CS1VIC started... ", enter the following parameters with their appropriated values on the command line:

     DB=(ABC*),ID=MYTRY

    Use PF3/15 to exit the menu.

  3. Select option 2 (Map) from the InfoVic menu.

    After the message "CS1MAP started... ", enter the following parameters with their appropriated values on the command line:

     DB=(ABC*)

    Use PF3/15 to exit the menu.

  4. Select option 3 (Recov) from the InfoVic menu.

    After the message "CS1RECOV started... ", enter the following parameters with their appropriated values on the command line:

     DB=(ABC*),ID=MYTRY,TEST=Y

    Use PF3/15 to exit the menu.

RECEIVE - Receiving a tape​

The RECEIVE installation service automatically bypasses the customization that was done in the previous environment thus allowing the user to keep the same values for the new environment.

Prior to executing the RECEIVE function, use option C from the main menu to check that the user configuration specifies the test environment that was created during the tape unloading step:


User library \...\....===\> new parmlib library dsname
(ddname INFPLIB in installation JCL)
User option \...\.....===\> Y (Y/N)

Furthermore, you may need to customize the following members of the new parmlib library before using the RECEIVE service:

  • CSKSTEP if ISPF load-modules are not in linklist.

  • CSKJOBC if CSXEXEC is not in linklist.

Select option R on the general installation menu to execute the RECEIVE installation service. The following panel is displayed:


INFO-RECOVERY - RECEIVE Installation Panel
COMMAND ===\>
test option ===\>
Production parmlib ..===\>
Test parmlib \...\....===\>
Test loadlib \...\....===\>
The test parmlib will be upgraded with the production parmlib
Press Enter to validate RECEIVE request or PF3/15 for exit

Specify the test and production parmlibs as well as the test loadlib.

The RECEIVE service assigns the name of the test loadlib entered inside this panel to the member PRODUCT. It retrieves production values from members SYSIDS, DB2IDS, IMSIDS, and then copies the members CUSTOM and CTRLRUN (as well as the members that are not available on the test site, for example user clists) from the parmlib of the production site to the parmlib of the test site.

However, the RECEIVE service does not handle the JOBCARD clist; if the JOBCARD clist has been customized in the production parmlib library, the user must take care to transfer these customizations to the test parmlib library.

All new parameters of CS1* members (members which contain the default values of parameters for each function) are automatically added; additions are dated and a summary of of these modifications is available for consultation, using the option Notes of the general INFO-RECOVERY menu.

The new version can then be tested independently of users working inside the production environment. When finishing the test processing, the user may want to test the new version under production environment conditions. Just specify the parameter TEST=Y in the production parmlib.

To immediately switch back to the previous condition, just specify TEST=N.

The new version can then be distributed using the UPGRADE function.

APPLY - Default parmlib​

The APPLY installation service allows the user to modify the default parmlib used by the CSXEXEC module.

Select option C on the general installation menu to display the following panel:


INFO-RECOVERY - APPLY Installation Panel
COMMAND ===\>
test option ===\>
Current parmlib \...\.....
Linklib \...\...\...\...\....
Default parmlib \...\.....
The default parmlib value, a marked CSXEXEC module in linklib, will be
replaced by a CSXEXEC module marked with the current parmlib value.
A /F LLA,REFRESH is needed to activate the new default.
Press Enter to validate APPLY request or PF3/15 for exit

The "APPLY" function defines the current environment as being the default environment. Just replace the version of the CSXEXEC module (to be found in the linklist) by the CSXEXEC module of the current environment. After a refresh of the LLA using the command F LLA,REFRESH, all batch programs, except those with a CSXPLIB DD statement, will automatically execute inside this environment.

To switch back to the previous condition, just issue another "APPLY" from the parmlib of the previous environment.

After the refresh of the LLA, and after at least one exit from the product (PF3/15), make sure that the general installation menu points to the new default parmlib.

UPGRADE - Upgrade​

The UPGRADE installation service replaces the INFO-RECOVERY version of the production environment with the test environment. Select option U on the general installation menu to display the following panel:


INFO-RECOVERY - UPGRADE Installation Panel
COMMAND ===\>
test option ===\>
Test parmlib \...\.....===\>
Test loadlib \...\.....===\>
Production parmlib ..===\>
Production loadlib ..===\>
The production parmlib and loadlib will be upgraded with the test
libraries.
Press Enter to validate UPGRADE request or PF3/15 for exit

Specify the test and production parmlibs and loadlibs.

If no test parmlib and loadlib are associated with the current environment, the UPGRADE service cannot be selected.

If the production environment does not exist, the UPGRADE service creates it by using the test environment as a model. Otherwise the production environment is deleted, and then recreated from the test environment.

RESET - Copy or Reset Members​

The RESET Installation Service is used to re-initialize one or several member(s) (ex: IMSIDS, CS1IIC, etc. ..) of the current parmlib using the test parmlib as a model. Select option M on the general installation menu to activate the RESET Installation Service. The following panel is displayed:


INFO-RECOVERY - RESET Installation Panel
COMMAND ===\>
test option ===\>
Current parmlib \...\.....
Selection list \...\...===\>
Such as : (CS1*,IMSIDS,US*)
All members selected will be replaced. (PRODUCTS member is always preserved)
Press Enter to validate RESET request or PF3/15 for exit

If no test parmlib is associated with the current environment, the service restores default parameters provided during the initial installation.

Members to be selected are designated using a list of generic or specific criteria (ex: (CS1 *), (CS1IC, CS1CA), etc. ..), entered in the panel displayed by the service.

Member PRODUCTS is always ignored, even if it is directly selected or implied by a generic specification. Otherwise, the description of the current parmlib would be destroyed.

COPY - Copy of Members​

The COPY Installation Service is used to copy one or more members (ex: DB2IDS, CS1VIC, etc...) from the current parmlib to a parmlib chosen by the user. Select option O on the general installation menu to display the following panel.


INFO-RECOVERY - COPY Installation Panel
COMMAND ===\>
test option ===\>
Current parmlib \...\.....
Receive parmlib \.....===\>
Selection list \...\...===\>
Such as : (CS1*,IMSIDS,US*)
All members selected will be copied. (PRODUCTS member is always preserved)
Press Enter to validate COPY request or PF3/15 for exit

The user must specify the parmlib to where the selected members must be copied.

Members to be selected are designated by a list of generic specifications or specific names (ex: (CS1 *), (CS1FIC, CS1IIC), etc. ..), on the panel displayed by the COPY Installation Service.

Member PRODUCTS is always ignored, even if it is selected by the designation criterion.

Managing Confidential Codes

Some modules of INFOTEL products are protected by a confidential code. This confidential code describes:

  • the type of product (InfoPak, InfoScope).

  • the options of the product (InfoPak VSAM, InfoPak MVS).

  • the type of version (test, permanent).

  • the CPU serial and model number on which the product is to be executed.

When the expiration date or CPU serial or model numbers have to be modified (example: a test version becomes a permanent version), your INFOTEL correspondent sends you a new confidential code. The installation of this code can be performed in BATCH mode by the program ILGMJCDB or under ISPF.

note

Installation can still be performed using the INFOTEL tape.

Customizing the PASSTAR Procedure​

The REXX procedure PASSTAR invokes the interactive confidential code management application.

PASSTARC is the CLIST version of PASSTAR.

Tables library​

The program managing confidential codes in interactive mode uses an ISPF table to save the list of the libraries containing INFOTEL load modules. It is necessary to allocate an ISPF table library in the start procedure PASSTAR or PASSTARC.

This library must be allocated with the ddnames ISPTLIB and ISPTABL. It can be specific to your INFOTEL software or be any user library having the following characteristics:

  LRECL=80,RECFM=FB,BLKSIZE=3120

For a specific table library, allocating one track will be enough.

Library allocation​

There are two ways to allocate the libraries used by the confidential code management application:

{wrapper="1" role="DL"}

  • In the REXX or CLIST start procedure

    Replace in the REXX procedure PASSTAR (or CLIST PASSTARC) the ???? fields by the library names. In this case, the allocation of the libraries is done when starting the application.

  • In the LOGON procedure

    The modules which have been copied to the ISPLOAD library (as named in the installation JCL) by the installation process, must also be in one of the concatenated libraries of the ISPLLIB card, the STEPLIB card of the LOGON procedure, or must be in LINKLIST.

The other libraries allocated under the ddnames ISPxxx in the installation JCL, should be concatenated with corresponding libraries in the LOGON procedure; the alternative is to copy their members to the corresponding libraries already allocated in the LOGON procedure.

The LIBDEF of the ISPF libraries and the corresponding FREE must then be suppressed from the procedure PASSTAR (or PASSTARC).

Starting the confidential code management application​

The member PASSTAR (or PASSTARC) contains the procedure that starts the interactive confidential code management application. It must be copied to a library concatenated under the ddname SYSPROC or SYSEXEC of the LOGON procedure.

Entering TSO PASSTAR (or TSO PASSTARC) in the command line of an ISPF panel results in the display of the confidential code management menu. The actual use of the application is described below.

Managing Confidential Codes under ISPF​

There are two ways to access to the confidential code application:

  • Using the option P in the primary MENU of the product, if this option is available.

  • Using the TSO command PASSTAR or PASSTARC, if the INFOTEL product does not contain interactive application or if its primary MENU does not contain the specific option P.

Primary Menu​

The following panel is displayed:


\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- INFOTEL: CONFIDENTIAL CODE \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
COMMAND ===\>
Select one of the following options:
0 SELECT INFOTEL LIBRARIES
1 UPDATE CONFIDENTIAL CODES
T TUTORIAL
X FIN
Press END or RETURN to quit

Please define the libraries that contain the load modules of INFOTEL product, first.

Selecting INFOTEL Libraries (Option 0)​

The following panel is displayed:


\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- SELECT INFOTEL LIBRARIES \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
COMMAND ===\> SCROLL ===\> CSR
List of the INFOTEL load module libraries:
(A volume may be entered for uncatalogued libraries)
( I to add lines, D to delete lines)
S LIBRARY NAME VOLUME
. INFOTEL.ISPLLIB
. INFO0.TEST.MVSLOAD HSMX13
**********************************************************************

This panel allows you to add, suppress, and/or modify lines in the list of libraries that contain INFOTEL load modules.

The VOLUME field has to be entered only for non cataloged data sets.

No validity check is performed on this panel, another panel will list the allocation errors when accessing the libraries.

The command CAN allows cancellation of all modifications.

Updating The Confidential Code (Option 1)​

The next panel is displayed:


\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- UPDATE CONFIDENTIAL CODE \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
COMMAND ===\>
CONFIDENTIAL CODE ===\> 660C18,DBACBA,6EED80,4DB987
CPU NUMBER TO BE CONTROLLED:
(format: XXXXSSSSMMMM SSSS: serial number , MMMM: model)
( \'*\' to control your own CPU)
CPU 1 ===\> * CPU 2 ===\> CPU 3 ===\>
CPU 4 ===\> CPU 5 ===\> CPU 6 ===\>
CPU 7 ===\> CPU 8 ===\> CPU 9 ===\>
CPU 10 ===\> CPU 11 ===\>

The meaning of the different fields is as follows:

Description of Input Fields​

{wrapper="1" role="DL"}

  • X

    Backup Extension Days

or

{wrapper="1" role="DL"}

  • Confidential code

    this field must be either entered a new confidential code obtained from Infotel to update INFOTEL load modules, or the value 'X'. If the value 'X' is used, "Backup Extension Days" are put into effect. This allows Infotel products to be used on new BACKUP CPUs for a few days. In a disaster test this should provide all the time needed for the test with reinstallation. If this is a new or upgraded CPU notify Infotel to acquire a new confidential code. The Confidential Code can be found on the Installation JCL that was sent with the product tape.

  • CPU

    It is possible to enter up to 11 CPU numbers in the confidential code. The value '*' tests the validity of the confidential code on the current CPU.

Allocation Error​

If allocation errors occur, the next screen is displayed:


\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- UPDATE CONFIDENTIAL CODE \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
COMMAND ===\> SCROLL ===\> CRS
PRESS ENTER TO CONTINUE, PF3 TO CANCEL
ERROR DURING ALLOCATION OF THE FOLLOWING LIBRARIES:
LIBRARY NAME VOLUME
INFO0.TEST.MVSLOAD HSMX13
***********************************************************************

By pressing ENTER, the search for modules continues in libraries that are correctly allocated. By pressing PF3, the search is canceled and the preceding screen is displayed.

List of Protected Modules​

The list of modules containing the new confidential code is displayed on the following screen:


\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- UPDATE CONFIDENTIAL CODE \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--
COMMAND ===\> SCROLL ===\> CSR
( S ALL!COMP!PART!INV for global modification)
List of INFOTEL protected modules:
( S to update a module)
S MODULE STAT LIBRARY VOLUME RESULT
. INFVCFL0 COMP INFOTEL.ISPLLIB UPDATED
. INFCMPS1 PART INFOTEL.ISPLLIB LEN. ERROR
. INFCMPS2 INV INFOTEL.ISPLLIB
*********************************************************************************

The meaning of the different fields is as follows:

{wrapper="1" role="DL"}

  • S

    Selection field to update a module by entering S value.

  • Module

    Name of an INFOTEL module accepting the new confidential code.

  • Stat

    Compatibility of the module with the confidential code. It can be compatible (COMP) if options are equal, partially compatible (PART) if options are not the same, or invalid (INV) if the module contains a code non identifiable by the INFOTEL system.

  • Library

    Name of the library that contains the module.

  • Volume

    Volume name if the library is not cataloged.

  • Result

    Result of the update. Possible values are:

  • UPDATED when the module has been updated

  • LEN.ERROR when the module cannot be updated because the new confidential code is too long. In this case, it is necessary to reinstall the product. The number of supported CPUs in a confidential code cannot be changed without reinstallation, in general.

  • NOT UPDATED when the module cannot be updated (for example if the module is RACF protected).

The following commands may be used for a global modification:

{wrapper="1" role="DL"}

  • S ALL

    Update all the modules.

  • S COMP

    Update all the compatible modules.

  • S PART

    Update all the compatible modules and all the partially compatible modules.

  • S INV

    Update all the invalid modules.

Managing Confidential Codes in BATCH mode​

ILGMJCDB is a batch user program. It searches a list of user libraries for the INFOTEL protected modules for a specific INFOTEL product. It will update the confidential code in these load modules and present in a report the list of the protected modules, the status of the modules (compatibility) and/or the result of the update.

The installation process has placed the module ILGMJCDB in the MVSLOAD library.

Using ILGMJCDB​

The program ILGMJCDB can be executed with the following JCL - an example is provided in the sample library (TSTCOD):


//jobname JOB \...\...\...\...\....
//stepname EXEC PGM=ILGMJCDB,PARM=\'action-code,confidential-code\'
//STEPLIB DD DSN=library-which-contains-ILGMJCDB
//PRINT DD SYSOUT=*
//INFLIBxx DD DISP=SHR,DSN=library-name
//\...\...\...\...\...\...\...\...\...\...\...\...\...\...\.....
//INFLIBxx DD DISP=SHR,DSN=library-name
//SYSIN DD *
MOD module library
\...\...\...\...\...\....
CPU cpu-number
/*

Call Parameters​

The confidential-code parameter of the INFOTEL JCL that you have received or a single 'X'. The value 'X', if entered, will implement "Backup Extension Days". This allows a permanent version of the product to run on a new CPU for a few days without reinstallation.

The confidential-code parameter corresponds to the confidential code specified on the INFOTEL JCL that you have received.

The action-code parameter can have the following values:

{wrapper="1" role="DL"}

  • V

    To test the validity of a confidential code (syntax error) or to test it against a list of CPU serial numbers. A message is displayed in SYSOUT (invalid or valid confidential code) and the return code is set to 0 if the code is valid, or to 8 if not.

  • L

    Tests the validity of a confidential code. Then searches for modules which correspond to the product that may accept this code. The list of modules is displayed in SYSOUT.

  • U

    Performs the same functions as L and updates the confidential code in all fully compatible modules. A module is fully compatible when it contains the same options as those defined in the installation JCL. A non-zero returncode indicates that no update was performed.

    A summary report is printed in SYSOUT.

  • P

    Performs the same functions as U, the only difference being that the code is updated even if it is only partially compatible. A module is partially compatible when the confidential code of the installation JCL contains fewer options than the load module. The return-code from this option must be zero to indicate the change was done.

    A report is printed in SYSOUT.

  • T

    May be used to verify that a module is allowed to be executed on a specific CPU. Running this at IPL time would allow the user to know that the product supports this CPU Serial and model Number. The operator could be notified by this test if the product requires attention. The result would normally be RETURN CODE zero. A RETURN code 4 would remind the user of the need to update the confidential code at a backup site.

  • X

    This is not a Function Code, but a confidential code type and must be used with a valid function code. Is used to implement "BACKUP Extension Days", allowing the product to run on a new or backup CPU for a number of days. If this is a new or upgraded CPU notify INFOTEL to acquire a new confidential code.

DDNAMEs Used​

{wrapper="1" role="DL"}

  • SYSPRINT

    Result data set. Receives execution messages of ILGMJC.

  • INFLIBxx

    Library that contains load modules to be modified. The two characters xx may be any characters authorized in a ddname.

    Each library has to be allocated under its own ddname (no concatenation).

  • SYSIN

    Optional. Can contain MOD and/or CPU control cards. If the SYSIN is omitted, or does not contain MOD card, the processing will scan all the modules containing a confidential code in all INFLIBxx libraries.

    The format of SYSIN cards is as follows:


  MOD module library volume
  CPU cpu-number

{wrapper="1" role="DL"}​

MOD :

Control card describing a module to be updated. A MOD card is necessary for each module to be modified. Nevertheless, if one desires to modify all the modules that are compatible with the new confidential code in all INFLIBXX libraries, do not code MOD card in SYSIN.

{wrapper="1" role="DL"}

  • module

    Name of the module to be updated.

  • library

    Library containing the INFOTEL modules.

  • volume

    Volume of the library if it is not cataloged.

  • CPU

    Control cards describing a CPU serial number that has to be tested against the confidential code.

  • cpu number

    A CPU number on 12 hexadecimal characters without comma. The value '*' allows you to test the validity of the code on the current CPU.

Example 1:


//jobname JOB \...\...\...\...\....
//STEP1 EXEC PGM=ILGMJCDB,PARM=\'U,120C18,025804,77ED80,4DB987\'
//STEPLIB DD DSN=INFOTEL.MVSLOAD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//INFLIB0 DD DSN=INFOTEL.ISPLLIB,DISP=SHR
//INFLIB1 DD DSN=INFO0.TEST.MVSLOAD,DISP=SHR,VOL=SER=HSMX13,
// UNIT=3380
//SYSIN DD *
MOD INFVCFL0 INFOTEL.ISPLLIB
MOD INFPCOPY INFO0.TEST.MVSLOAD HSMX13
CPU *
/*

In this example, ILGMJCDB updates the confidential code in the module INFVCFL0 that is found in the library INFOTEL.ISPLLIB, and in module INFPCOPY in the non cataloged library INFO0.TEST.MVSLOAD. The module is updated only if the new code is fully compatible with the old one, and if the new confidential code is valid on the current CPU.

note

Use of the MOD card restricts the update to specified modules of your INFOTEL product. The MOD card function should only be used after consulting with INFOTEL Technical Support.

Example 2:


//jobname JOB \...\...\...\...\....
//STEP1 EXEC PGM=ILGMJCDB,PARM=\'T\'
//STEPLIB DD DSN=INFOTEL.MVSLOAD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//INFLIB0 DD DSN=INFOTEL.MVSLPA,DISP=SHR
//SYSIN DD *
MOD INFVCP0 INFOTEL.MVSLPA
CPU XXXX03149021
/*

In Example 2, ILGMJCDB checks the module INFIVCP0 in library INFOTEL.MVSLPA for a CPU with serial 0314, last four digits, and model 9021. A RETURN code of zero indicates INFIVCP0 will run on this CPU and a RETURN code of 4 indicates that INFIVCP0 will ABEND with a 4040 if executed on the 9021 with serial number 0314.

Results of ILGMJCDB​

ILGMJCDB produces a report showing the result of the update (ddname SYSPRINT).

A sample report is reproduced below:


*****************************************************************************************************************
* INFOTEL LE 01/06/93 A 10:15 PAGE : 1 *
* CONFIDENTIAL CODE REPORT *
*****************************************************************************************************************
* CONFIDENTIAL CODE : 120C18,025804,77ED80,4DB987 *
*****************************************************************************************************************
* MODULE * LIBRARY * VOLUME * STATUS *
*****************************************************************************************************************
* * * * *
* INFVCFL0 * INFOTEL.ISPLLIB * * UPDATED *
* INFPCOPY * INFO0.TEST.MVSLOAD * HSMX13 * NOT UPDATED, THE CODE IS TOO LONG *

The second module is not updated because the new code is too long. In this case to update the modules, a new installation of the product is necessary.

Updating the Confidential Codes in Batch Mode​

Use the sample (member TSTCOD) that is provided in the product's INFSAMP library. The following values must be inserted into the TSTCOD member:

  1. Specify as STEPLIB the library that contains the ILGMJCDB module (MVSLOAD library of the installation JCL).

  2. Specify in the DDNAMEs INFLIBxx (one ddname per library: INFLIB00, INFLIB01, ....) all libraries that contain load-modules of our products (perhaps the linklist).

  3. Do not specify a SYSIN (SYSIN DD DUMMY): this way the "Confidential Code Management" utility will modify all load-modules that must be updated.

  4. Submit a first job by specifying PARM='L,confidential code', thus allowing the utility to check if the confidential code is compatible with your installation. The output will be a listing that contains a list of modules with a status. If no error occurred, the execution result displays the status: CODE IS COMPATIBLE

  5. If such is the case, submit a second job by specifying PARM='U,confidential code' thus allowing the update for all load-modules. Otherwise, please forward the execution output report for analysis to the INFOTEL Technical Support Center.

Disaster Recovery Site Authorization​

Backup Extension Days can be turned on by running the following job. This job will authorize a CPU for emergency situations.

Using already installed libraries

Backup Extension Days can be activated by running the following job. This job will authorize a CPU for emergency situations.


//jobname JOB \...\...\...\....? .
//STEP1 EXEC PGM=ILGMJCDB,PARM=\'U,X\' .
//STEPLIB DD DSN=library.which.contains.ILGMJCDB,DISP=SHR .
//SYSPRINT DD SYSOUT=* .
//INFLIB0 DD DSN=library.name1,DISP=SHR .
//INFLIB1 DD DSN=library.name2,DISP=SHR .
//INFLIB3 DD DSN=library.name3,DISP=SHR .
//SYSIN DD * .
CPU * .
/* .

library.name1, library.name2... stand for the names of the libraries containing INFOTEL's products load modules (including libraries within linklist).

  • If some modules located in linklist are updated then you'll need to perform a F LLA,REFRESH command on the MVSLOG afterwards.

  • If some modules located in LPA are updated, generally an IPL is required to load the refreshed modules.

Rem.: This operation can be performed only once. A new run of this JCL would issue a Return Code 4.

Performing a new installation

In case of installation on a unauthorized-CPU machine, the Backup Extension Days are automatically activated.

See Managing Confidential Codes in BATCH mode.

Validity of a confidential code​

Two types of confidential codes are available: temporary and continuous codes.

  • Temporary codes:

    Usually, temporary codes are provided for products tests or breakdown service. These codes must be replaced after the expiration date.

  • Continuous codes:

    The continuous codes are delivered when bying the product to be executed on a determined number of machines.

    The authorization check-up is based on the 8 final characters of the CPU identifier, this is 4 final characters of the CPU SERIAL NUMBER, followed by the machine model (example 11119673).

    Use the command D M=CPU to obtain the CPU identifier as shown in the output below:


  RESPONSE=P390
  IEE174I 17.51.24 DISPLAY M 919
  PROCESSOR STATUS
  \>\>\> ID CPU SERIAL
  0 + 010CA17060
  CPC ND = 007060.P30.IBM.51.000000010CA1
  CPC SI = 7060.P30.IBM.51.0000000000010CA1
  CPC ID = 00

The 8 final characters of the SERIAL column (see the line starting with >>>) are used to check the authorization. In the example above, the corresponding code is 0CAI7060.

If any modification of the final 8 characters of the CPUID is done, the the confidential code must be replaced. This situation may occur in the following cases:

  • either the CPU SERIAL NUMBER, or

  • the machine model has changed.

For both types of confidential codes: The confidential code is related to the delivered tape number. When installing a new tape, the previous confidential code is no usable. Therefore, a new confidential code is provided for each new tape delivery.

InfoVic2

InfoVic2 includes all functions associated with DB2 recovery:

  • applicative checkpoints

  • DB2 automatic operator

  • physical recovery

  • application recovery to a checkpoint

  • "MAP" of the activity

General Description​

InfoVic2 is a RECOVERY control automaton that generates JCL and controls its execution.

It executes under TSO-ISPF and uses ISPF tables and skeletons.

The JCL is generated under specific conditions.

  • according to the user requirements that specify:

    • the function to execute

    • the subsystem (IMS and/or DB2) on which it has to be applied

    • the databases to process

    • the execution parameters

  • according to a default parameter library: the parmlib;

The user can also act on the JCL generation:

  • by requesting the execution of CLIST or REXX procedures

  • by providing its own generation skeletons

The generated JCL can be saved in a file or submitted directly by INFO-RECOVERY.

In this case, the generator job of the JCL will be called "GENERATING JOB", the current step of the generating job will be called "MOTHER STEP", and the submitted job will be called "GENERATED JOB".

The generating job can control the execution of the generated job. It can wait until the end of the execution of the generated job to continue its own execution In this case, the correct or erroneous execution of the generated job will provoke the good or bad execution of the mother step.

The control of the execution allows for the execution of image copy at the beginning of an application job, and for the continued execution of the application job only when the image copy is executed.

PARMLIB​

The PARMLIB is essential to INFO-RECOVERY. The PARMLIB contains these components:

  • JCL generation skeletons

  • Description of the IMS or DB2 site see the Installation Guide of INFO-RECOVERY, HR104

  • Default processing parameters for various functions

  • Standard CLIST of the product

  • ISPF panels

  • Members that allow execution of SQL statements

BATCH Execution​

In batch mode as well as in interactive, the execution of INFO-RECOVERY is requested by the call of the module CSXEXEC.

In batch mode, the necessary JCL is the following:


//S1 EXEC PGM=CSXEXEC,DYNAMNBR=50,REGION=2M,
// PARM=(FUNCTION,\'Funcname\'\[,Name,\'Value\'\])
//SYSIN DD *
Parameters of the requested function

When executed in batch mode, the module CSXEXEC receives two types of parameters:

  1. The execution parameter defines the function to execute

  2. The SYSIN file specifies on what databases to execute the function and detailed parameters of the function.

Parameters​

CSXEXEC receives a succession of (Name,Value) pairs, where Name is the name of a variable and Value its value. The value has to be coded between apostrophes.

Expected variables follow:

{wrapper="1" role="DL"}

  • FUNCTION

    This parameter is mandatory; it specifies the name of the function to execute: CS1VIC, CS1IC, etc....

  • IMSID

    This parameter is optional; it specifies the IMS subsystem on which the function will execute. The subsystem has to be defined in parmlib member IMSIDS.

    For a data sharing environment, the name of the IMS group can be specified. The group of IMSs must have been defined in member IMSDSGS of the PARMLIB.

    If this parameter is omitted, INFO-RECOVERY will work on the default IMS subsystem (as defined in parmlib member SYSIDS). The special value IMSID,'NONE' allows for skipping all IMS-related allocations; it may only be used for mixed DL1/DB2 functions for those executions in which only DB2 selection parameters are entered.

  • DB2ID

    This parameter is optional; it specifies the DB2 subsystem on which the function will execute. The subsystem has to be defined in parmlib member DB2IDS.

    You may specify the name of the DB2 group if data sharing is used on your site. If such is the case, the DB2 group must have been defined in member DB2DSG of the PARMLIB. INFO-RECOVERY will select the DB2 sub-system (inside the group) according to the system where the execution takes place.

    If this parameter is omitted, INFO-RECOVERY will work on the default DB2 subsystem (as defined in parmlib member SYSIDS). The special value DB2ID,'NONE' allows for skipping all DB2-related allocations; it may only be used for mixed DL1/DB2 functions for those executions in which only IMS selection parameters are entered.

  • DEBUG

    This parameter is optional. If any problem occurs, the DEBUG function allows the user to trace the Clist (or REXX) procedures, the INFO-RECOVERY skeletons, and the commands passed to the subsystem (IMS/DB2). Values: 'Y' or 'N' (default).

The example below shows the execution of a FULL IMAGE COPY (CS1FIC function) on the DB2 DB2E:

 //S1      EXEC PGM=CSXEXEC,DYNAMNBR=50,REGION=2M,
 //             PARM=(FUNCTION,'CS1FIC',DB2ID,'DB2E')
 //SYSIN   DD *
  Parameters of the CSIFIC function

Execution of an IMS image copy processing on the default IMS, with tracing of Clist and IMS commands.

 //S1      EXEC PGM=CSXEXEC,DYNAMNBR=50,REGION=2M,
 //             PARM=(FUNCTION,'CS1IC',DEBUG,'Y')
 //SYSIN     DD *
  Parameters of the CS1IC function

SYSIN​

The SYSIN file specifies variables that will manage the execution of the requested function.

  • Indication variables:

    On what databases and/or what tablespaces the function must be executed?

  • Execution variables:

    How the function has to be executed?

Format​

The SYSIN sets variables with the following syntax:

 VARIABLE=value

note

The character '*' in column 1 indicates a comment.

note

The blank character (' ') after the value indicates that the rest of the line is a comment.

note

The name of the variable must not begin in column 1. First column is reserved for the label followed by a blank.

note

A comma (',') behind the value of a variable connects the variable to the next variable and creates groups of variables. There will be as many executions of the function as there are groups of variables.

note

It is easier to read the SYSIN when starting the line with the indication variable: variable "DB" for IMS and variables "TS" and "DBSET" for DB2.

The different execution variables and the associated syntax are described in chapters covering each function.

Default Values​

It is not necessary to systematically enter all execution variables of a function into the Sysin:

For each INFO-RECOVERY function, a member of the same name is associated in the parmlib library.

It has the same syntax as the SYSIN file.

It contains the definition of all variables necessary for the execution of the function.

It sets the default customization of the function for the site. (see: Customizing INFO-RECOVERY).

The example below shows the execution of a FULL IMAGE COPY (function CS1FIC) of tablespaces from the DB2 DB2E and which name starts with CLI:

 //S1      EXEC PGM=CSXEXEC,DYNAMNBR=50,REGION=2M,
 //             PARM=(FUNCTION,'CS1FIC',DB2ID,'DB2E')
 //SYSIN   DD *
  TS=(CLI*)

In this example, no execution parameter was specified. The values found in member CS1FIC of the Parmlib will be used.

User Variables​

User variables can also be specified in SYSIN and can also be used in REXX procedures (or CLIST) or in user skeletons (see: User Variables).

The Other Data Sets​

Below is the list of optional DD cards and their use:

CSXPRINT

Checking the printing of messages. By default they are dynamically sent to SYSOUT=*.

CSXPLIB

Using a PARMLIB other than the default parmlib. The example below illustrates a VIC JCL where the parmlib has been forced:

 //S1      EXEC PGM=CSXEXEC,DYNAMNBR=50,REGION=2M,
 //             PARM=(FUNCTION,'CS1VIC',IMSID,'IMST')
 //CSXPLIB DD   DSN=INFOREC.V1R0.CSBPLIB,DISP=SHR
 //SYSIN   DD   *
   DB=(DBCLI*),ID=CLI01             <===... vic client database

CSXULIB

To add a user parmlib. The use of CSXULIB redefines ISPF objects used by the software and the default customization of the function. A member of the parmlib is then "masked" by a member with the same name existing in the user library.

The example below illustrates a RECOV JCL where a user library has been added:

 //S1      EXEC PGM=CSXEXEC,DYNAMNBR=50,REGION=2M,
 //             PARM=(FUNCTION,'CS1RECOV',IMSID,'IMST')
 //CSXULIB   DD DSN=userid.INFOREC.USERLIB,DISP=SHR
 //SYSIN     DD *
   DB=(DBCLI*),ID=CLI01,TEST=Y      <===... test of recovery

JCLOUT

All functions that generate JCL accept a TEST= parameter, allowing to print (TEST=Y) or to submit (TEST=N) the generated JCL. It is possible to write the generated JCL into a data set instead of submitting it by adding a JCLOUT DD statement.

The example below illustrates a JCL of RECOV where the submit has been routed to the library specified in JCLOUT:

 //S1      EXEC PGM=CSXEXEC,DYNAMNBR=50,REGION=2M,
 //             PARM=(FUNCTION,'CS1RECOV',IMSID,'IMST')
 //JCLOUT    DD DSN=userid.INFOREC.JCLOUT(MYRECOV),DISP=SHR
 //SYSIN     DD *
   DB=(DBCLI*),ID=CLI01,TEST=N    <===... Recov JCL copied to JCLOUT

Customizing INFO-RECOVERY​

All functions of INFO-RECOVERY are managed by ISPF variables. Associated with the ISPF skeletons, they generate the JCL for each function.

INFO-RECOVERY uses three types of variables:

  • System variables,

  • Site variables,

  • Function variables;

INFO-RECOVERY allows the use of a fourth type of variable: user variables.

Depending on their type, variables can be found in these locations:

  • Within call parameters of CSXEXEC in batch mode or user configuration in interactive mode

  • Within information provided during the call:

    SYSIN File in batch mode or function screen in interactive mode;

  • In the parmlib library,

  • Or directly generated by INFO-RECOVERY.

If a variable is specified both in SYSIN and PARMLIB, the value specified in SYSIN will be used.

If a variable is specified neither in SYSIN nor in PARMLIB, INFO-RECOVERY will use its own defaults.

System Variables​

System variables are non-updatable variables that are generated automatically during each execution. They cannot be specified in the user parmlib or in the SYSIN file.

Example: variable HHMMSSD that is used for the generation of an image copy dsname.

This variable contains the execution timestamp specified in tenth of seconds.

Site Variables​

Site variables define to INFO-RECOVERY the site's execution configuration and general conditions.

Their values can be specified in call parameter, in the SYSIN file or in the parmlib of INFO-RECOVERY.

6 members of the parmlib provide variables for the site:

  • SYSIDS describes all MVS systems using the products

  • IMSIDS describes IMS systems using the products

  • DB2IDS describes DB2 systems using the products

  • PRODUCTS describes installed products

  • CUSTOM describes the global INFO-RECOVERY customization

  • CTRLRUN checks the status of batch CSXEXEC

The format of these members is described in the Appendix. Modification rules are detailed in the Installation Manual HR104.

Function Variables​

Function variables are used to specify execution parameters of a function.

Their values can be specified in the SYSIN file or in the parmlib of INFO-RECOVERY in a member having the same name as the function.

Several variables are associated with each function. They are described in chapters that explain the function.

The user is informed about the:

  • indication variables

  • execution variables

After the first installation, parmlib members associated with functions contain a customization adapted to the most frequent use of INFO-RECOVERY and they only need to be modified for sophisticated tests (see adjustment paragraphs and complements for each function).

During re-installations or further upgrades, the customization is preserved and the new parameters are automatically added. This modification is dated. The list of all members that have been automatically modified may be viewed with the option 'Note' on the main INFO-RECOVERY menu.

User Variables​

User variables can be entered into the SYSIN file or in the parmlib member corresponding to the function.

These variables may be used by ISPF skeletons and REXX procedures (CLIST).

The example below illustrates the execution of a RECOVERY (function CS1RECOV) of IMS IMST databases which name begins with DBX, and specifies the user parameter USERDEST (this parameter is supposed to allow the routing of sysouts to a particular printer).

 //S1      EXEC PGM=CSXEXEC,DYNAMNBR=50,REGION=2M,
 //             PARM=(FUNCTION,'CS1RECOV',IMSID,'IMST')
 //SYSIN     DD *
   DB=(DBX*),USERDEST=rmt27

Calling User Procedures​

INFO-RECOVERY allows the execution of user REXX or CLIST procedure.

Corresponding members can be found in the PARMLIB or in a library declared in the member SYSIDS of the parmlib (variable SYSPROC or SYSEXEC).

Using CS1ULOAD

Purpose​

The CS1ULOAD function allows you to generate a job that reloads tablespaces using their most recent image copy. To do so, CS1ULOAD uses a generic list of tablespaces; then the InfoLoad Utility performs the reload processing.

The CS1ULOAD function analyses the DB2 catalog to:

  • set up the complete list of tablespaces,

  • retrieve the most recent image copies,

  • retrieve the characteristics of all tables belonging to the tablespaces on the list.

After that, the CS1ULOAD function builds the corresponding JCL. This JCL can either be retrieved or be submitted and supervised during the execution.

The CSIULOAD function only requires one mandatory parameter as follows:


TS=(dbgen1,tsgen1,dbgen2.tsgen2,\...)

The generated JCL contains one InfoLoad utility execution step per tablespace.

In order to optimize the mount processing of cartridges, the CS1ULOAD function determines the order to process the tablespaces.


//step EXEC PGM=INFUTILB
//STEPLIB DD DISP=SHR,DSN=????????
// DD DISP=SHR,DSN=????????
//SYSREC DD DISP=SHR,DSN=dsname-image-copy-file
// DD DISP=SHR,DSN=dsname-image-copy-file
\-\--\> if copy per partition
//SYSPRINT DD SYSOUT=*
//UTPRINT DD SYSOUT=*
//SYSDISC DD SYSOUT=*
//SYSIN DD *

The SYSIN statement contains the following parameters:

  • for a tablespace with one single table:

    LOAD DATA

    RESUME NO REPLACE KEEPDICTIONARY

    FORMAT COPY

    INTO TABLE creator.tablename ORIGINOBID 0

  • for a tablespace multi-tables:

    LOAD DATA

    RESUME NO REPLACE KEEPDICTIONARY

    FORMAT COPY

    INTO TABLE creator.tablename1 ORIGINOBID obid1

    INTO TABLE creator.tablename2 ORIGINOBID obid2

Constraints​

The information used to generate the JCL is retrieved from the original DB2 system when executing the CS1ULOAD function, such as:

  • the name of the creator,

  • the name of the table,

  • the OBID

The user variables are provided to change all creator names into another valid name on the target DB2 system.

However, a more sophisticated conversion of creator and table names must be handled by the user and must be performed when executing the JCL to be adapted to the target environment.

For partitioned tablespaces with image copies per partitions, the image copies will be concatenated in the input data set to sequentially load all partitions.

User Parameters​

Syntax​

The execution variables of the CS1ULOAD function are described below.

You can change the default values by modifying the CS1ULOAD member of the parmlib.


* comment
TS=(criterion,.), TS search criterion
EXTS=(criterion,..), EXTS exclusion criteria
TEST=Y/N, print (Y, def) or submit (N) the generated JCL
* or write (N) into JCLOUT if present.
DBSET=dbset, database search criterion
AUTHID=authid, creator search criterion
DISPLAY=Y/N, display (yes or no) the search result
PROC=proc, name of the XPROC procedure
ICSITE=L/R/C, recover with image copy of specified site
SIZE=Y/N/C, estimate (yes or no) the number of input records
STATS=Y/N, update (yes or no) the DB2 catalog statistics
STPEND=Y/N/NN, keep (yes or no) the \"pending\" status of the ts
* after execution
TSEMPTY=Y/N, process (yes or no) empty tablespaces
DSNLD=dsname, dsname of the library that contains the InfoLoad
* load-module
DSNPB=dsname, dsname of the parmlib that is used by InfoLoad
UID=uid, unique identifier for the job utility
RUNLIB=runlib, specifies the dsname of the DB2 RUNLIB
TIADPLAN=plan, specifies the name of the DSNTIAD plan
UTPRINT=Y/N, specifies whether the UTPRINT card must be generated
* or not generated in the INFUTILB execution step
ALTQTY=Y/N, update of the primary and secondary allocations
TSSET=N, extend selection to tablespace set Y/N (def. \"N\")
AUXTS=WITHBASE, WITHBASE/INLIST indicates if
* LOB/XML/TEMPORAL TS are processed with base TS
*
* Uservariable=, any user variable such as:
USDB2ID=usdb2id, name of the DB2 in the target environment
USCREA=uscreator, creator of tables in the target environment
USDB2EXI=usdb2exi, exits library (DSNEXIT) of the target DB2
USDB2LIB=usdb2lib, load modules library (DSNLOAD) of the target DB2
USREG=usreg, user region for the InfoLoad step
USCOND=retcode, value of the return code checked by COND
USTEST=Y/N, TEST parameter of the CS1ALTER sub-function
USCHECK=Y/N, JOBCHECK parameter of the CS1ALTER sub-function
USALTJOB=jobname, target JOBNAME (used when ALTQTY=Y)
USDSNLIB=dsname, Target Inforec loadlib.
* This loadlib must APF.
LSYSAFF=, execution system of the CS1ALTER sub-function
TITLE=\"\...\" a title
*
* comment
*
TS=(criterion,.), another set of parameters
\...

Description of the parameters​

{wrapper="1" role="DL"}

  • TS=(criterion,..)

    TS= specifies a list of tablespace names patterns. Tablespaces referenced in the DB2 catalog whose name matches one of the patterns are included in the list of tablespaces on which the requested function is to be performed.

    Precisely:

  • A name pattern means a generic name according to SQL LIKE syntax: special characters are the percent sign % and the underscore sign _; additionally, an asterisk * is transformed into a % sign.

  • For a pattern in the form dbname.tsname, tablespaces selected are those whose database name matches the dbname pattern, whose name matches the tsname pattern and whose creator's name matches the AUTHID pattern.

  • For a pattern in the form tsname, tablespaces selected are those whose database name matches the DBSET pattern, whose name matches the tsname pattern and whose creator's name matches the AUTHID pattern.

  • If TS=CATALOG is specified, the function will be performed on catalog tablespaces.

  • If TS=% or TS=* is specified, no catalog tablespace will be selected.

The database name often occurs as the first index column on catalog tables read by the function. Therefore, better performance in reading from the DB2 catalog will be achieved if the database name pattern is specified with as much precision as possible, either through the DBSET parameter, or through the qualifier in a list item of the form dbname.tsname.

  • EXTS=(criterion,.)

    specifies a list of tablespaces to be excluded from processing. The EXTS parameter has the same syntax then the TS parameter and allows you to exclude certain tablespaces from the list that has been obtained by using the TS parameter.

    The EXTS parameter is ignored in case of TS=CATALOG.

    Default: NONE

  • TEST=Y/N

    the TEST parameter is used to print (TEST=Y) or to submit (TEST=N) the generated JCL.

  • DBSET=dbset

    DBSET= is used as a default dbname pattern for each item in the list TS= in the form tsname; see the description of TS= parameter. Default parameter: %

  • AUTHID=authid

    AUTHID= is used as a creator's name pattern for each item in the list TS=; see the description of TS= parameter. Default parameter: %

  • DISPLAY=Y/N

    DISPLAY= lists on SYSOUT the selected databases and tablespaces.

    Default parameter: N

  • PROC=proc

    PROC= is the name of the standard XPROC procedure for the FIC function. A user procedure may be used.

    Default parameter: CSRFIC

  • TSSET=Y/N

    Allows to require the inclusion of all tablespaces that fulfill the reference integrity of selected tablespaces (those obtained by treating the TS and EXTS parameters): all tablespaces with a table linked by a reference integrity constraint to a tablespace table in the defined list are added to the list.

    • Y: research of the tablespace set for the referential integrity constraint.

    • N: Do not search this tablespace set.

    Default parameter: N

    note

:

The relations with the LOBS or XML or historical tablespaces are not taken into consideration through this parameter, but through the AUXTS parameter.

  • AUXTS=WITHBASE/INLIST.

    Indicates how auxiliary tablespaces (LOB, XML or historical) to include in the treatment are designated:

    • WITHBASE: the auxiliary tablespace are implicitly designated through the base tablespace name they depend. All LOB, XML or historical tablespace depending from a base tablespace designated with TS parameter (excepting the ones which names corresponds to EXTS criterion) is treated.

      note

:

In this case, the TS parameter only indicates the base tablespaces names.

  • INLIST: the auxiliary tablespaces are directly defined by their name through the TS parameter. All auxiliary tablespaces which correspond to the name criteria indicated by the TS parameter are processed.

    note

:

In this case, the TS parameter indifferently designates base tablespaces or LOBs or XML tablespaces. If the list defines both a base tablespace and some of its auxiliaries, they are nevertheless individually processed.

Default parameter: WITHBASE

  • ICSITE=L/R/C

    this parameter is only available from DB2 version 4 and above, it is used to specify that the recover is to be performed with the image copies of the specified site. L = Localsite, R = Recoverysite, C = Current site. Default parameter: C

  • SIZE=Y/N/C

    SIZE= allows you to generate the LOAD DATA statement that includes the SIZE parameter specifying the number of input records.

    If SIZE=Y is specified, this number is calculated according to the number of lines that are found inside the corresponding tables when generating the JCL.

    If SIZE=C is specified, this number is retrieved from the DB2 catalog (SYSIBM.SYSTABLES) and updated by the RUNSTAT utility.

    Default parameter: N

  • STATS=Y/N

    STATS= allows you to create the dataset to update the DB2 catalog statistics within an additional step.

    Default parameter: N

  • STPEND=Y/N/NN

    Specifying Y means that the tablespaces that have been loaded will be in COPY pending status and, possibly, the dependent tablespaces will be in CHECK pending status.

    Specifying N allows you to execute the LOAD DATA statement with option NOTIFY NO (meaning that the LOAD is not notified to DB2) and to START all tablespaces in an additional step.

    Specifying NN allows you to execute the LOAD DATA statement with option NOTIFY NO but without adding the START of the tablespaces.

    Default parameter: Y

  • TSEMPTY=Y/N

    Specifies if tablespaces with empty tables must be processed (Y) or must not be processed (N).

    Default parameter: Y

  • DSNLD=

    Specifies the dsname of the library that contains the InfoLoad load-module.

  • DSNPB=

    Specifies the dsname of the parmlib that is used by InfoLoad.

  • UID

    Indicates the unique identifier for the job utility.

    Default parameter: value of the JOBNAME.

  • RUNLIB=

    Indicates the dsname of the RUNLIB DB2.

  • TIADPLAN=

    Indicates the name of the DSNTIAD plan.

  • UTPRINT=

    The use of the UTPRINT ddname in the INFOTEL LOAD is related to the SORTCLAS variable of member INZTVAR in the INFOUTIL parmlib

  • ALTQTY

    The value Y allows you to generate an ALTER step for the tablespaces and indexspaces to update the primary and secondary allocations of the target system's objects (PQTY, SQTY and SECQTYI).

    Default parameter: N

Uservariable= :

Allows you to specify user variables that are described below:

{wrapper="1" role="DL"}

  • USDB2ID=

    To specify the identifier of the target DB2. If nothing is specified the name of the source DB2 is kept.

  • USCREA=

    To modify the CREATORs of the tables in the target environment, otherwise the names of the source DB2 are kept.

  • USDB2EXI

    To specify the exits library (DSNEXIT) of the target DB2. If no value is specified for the USDB2EXI parameter, then the value of the DB2EXIT parameter (belonging to member DB2IDS of the parmlib) is taken into consideration (see the INFO-RECOVERY Installation Manual (HR104), chapter "DB2IDS-DB2 System Descriptions").

  • USDB2LIB

    To specify the load modules library (DSNLOAD) of the target DB2. If no value is specified for the USDB2LIB parameter, then the value of the DB2LIB parameter (belonging to member DB2IDS of the parmlib) is taken into consideration (see the INFO-RECOVERY Installation Manual (HR104), chapter "DB2IDS-DB2 System Descriptions").

    If USDB2LIB=NONE is specified, then no default value is taken into consideration.

  • USREG

    To specify the user region of the InfoLoad step.

  • USCOND=retcode

    Specifies the return code value of the steps that are checked using the COND parameter of the EXEC card, a value higher than 4 allows you to continue the processing even though there are errors within the steps.

    Default parameter: 4

  • USTEST=Y/N

    Specifies the value of the TEST parameter that is used in the CS1ALTER sub-function. Use this parameter to provide a specific value to the CS1ALTER sub-function and that is different from the value used in the mother job of the main function CS1ULOAD. For example, specifying TEST=N and USTEST=Y allows you to submit the daughter job of the CS1ULOAD function (meaning the CS1ALTER sub-function) without executing the grand daughter job.

    Default parameter: Value of the TEST parameter.

  • USCHECK=Y/N/C

    Specifies the value of the JOBCHECK parameter that is used in the CS1ALTER sub-function. Use this parameter to provide a specific value to the CS1ALTER sub-function and that is different from the value used in the mother job of the main function CS1ULOAD.

    Default parameter: Value of the JOBCHECK parameter.

    note

:

If the JOBCHECK parameter is not specified within the CS1ULOAD main function, then the value specified in the CUSTOM member is taken into consideration. The CUSTOM member describes the global parameter setting of INFO-RECOVERY. (see the GR104 INFO-RECOVERY Installation manual).

  • USALTJOB=jobname

    Specifies the name of the job that was generated on the target system by the CS1ALTER function. The CS1ALTER function is activated when submitting the CS1ULOAD function with the parameter ALTQTY=Y.

  • USDSNLIB=dsname

    Specifies the name of the Inforec loadlib of the target environment. This loadlib is inserted into the steplib of the Inforec steps that are executed on the target environment.

    This option is useful when the CSXEXEC module is not in linklist on the target environment. The loadlib must be APF.

    The value USDSNLIB=Y indicates the use of a loadlib having the same name than the loadlib on the source environment (refer to chapter " PRODUCTS - Products Description").

  • LSYSAFF=

    Specifies the execution system of the CS1ALTER sub-function.

  • TITLE='....'

    To specify a title.

Examples​

The example below illustrates how to generate JCL into JCLOUT for a job that loads tablespaces corresponding to the generic names DSN8D51A.DSN8551% and AUTC%. This job also updates the DB2 catalog statistics for these tablespaces, generates the LOAD DATA statement with the option NOTIFY NO and estimates the number of records.


//JOBLIB DD DSN=DSN510.SDSNLOAD,DISP=SHR
// DD DSN=LABO.APFLIB=SHR
//USER EXEC PGM=CSXEXEC,DYNAMNBR=50,REGION=2M,
// PARM=(FUNCTION,\'CS1ULOAD\',DB2ID,\'DX51\'
//JCLOUT DD DSN=userid.INFOREC.JCLOUT(MYLOAD),DISP=SHR
//SYSIN DD *
TS=(DSN8D51A.DSN8551*,AUTC*),
TEST=N,DISPLAY=N,STATS=Y,STPEND=N,SIZE=Y
/*

If the SYSIN contains several commands, you must allocate a sequential dataset with DISP=MOD in the JCLOUT card, thus allowing the writing of several JCLs that are generated by the CS1ULOAD function.

note

The JCLOUT dataset must be empty before executing the CS1ULOAD function (otherwise the JCLOUT dataset might contain a JCL from the previous execution).

See the example below that illustrates the case described above:


//JOBLIB DD DSN=DSN510.SDSNLOAD,DISP=SHR
// DD DSN=LABO.APFLIB=SHR
//DELETE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD*
DELETE userid.JCLOUT.SEQ
SET MAXCC=0
//USER EXEC PGM=CSXEXEC,DYNAMNBR=50,REGION=2M,
// PARM=(FUNCTION,\'CS1ULOAD\',DB2ID,\'DX51\'
//JCLOUT DD DSN=userid.JCLOUT.SEQ,DISP=(MOD,CATLG,DELETE),
// SPACE=(TRK,(10,10)),UNIT=SYSDA
//SYSIN DD *
JOBNAME=FIRSTJOB,
TS=(DSN8D51A.DSN8551*,AUTC*),
TEST=N,DISPLAY=N,STATS=Y,STPEND=N,SIZE=Y
JOBNAME=SECONJOB,
TS=(TST8D51A.TST8552*,XUTC*),
TEST=N,DISPLAY=N,STATS=Y,STPEND=N,SIZE=Y
/*