Skip to main content

Preface

This document is intended to help you install one of the INFO-RECOVERY products:

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

  • InfoRec1

    is described in the document HR101.

  • InfoRec2

    is described in the document HR102.

  • InfoVic1/2

    are described in the document HR103.

INFO-RECOVERY

INFO-RECOVERY is composed of four complementary and independent software packages:

  • InfoRec1

    InfoRec1 supervises, along with DBRC, all data sets associated with IMS recovery:

    • image copy

    • change accum

    • log

  • InfoRec2

    InfoRec2 supervises, along with the DB2 catalog, all data sets associated with DB2 recovery:

    • image copy

    • incremental image copy

    • log

  • InfoVic1

    InfoVic1 includes all functions associated with IMS recovery:

    • application checkpoint

    • IMS automatic operator

    • physical recovery

    • application recovery to a checkpoint

    • "MAP" of the activity

  • 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

The combination of InfoVic1 and InfoVic2 mixes DB2 and IMS checkpoints and repositions IMS databases and DB2 tablespaces to these checkpoints.

INFO-RECOVERY INSTALLATION

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.

Rules for CPU Serial Number Verification​

Infotel products are CPU serial and model number dependent. The Infotel product should be installed on each licensed CPU. It should not be copied to another licensed CPU to bypass the install procedure. The CPU serial and model numbers are assigned and checked by the install, and checked by the Infotel modules in order to insure a valid CPU during execution.

warning

A copy of the product will run on a correct CPU serial and model number but will fail on an unauthorized CPU serial or model number with a user abend 4040. It can be installed on, BUT NOT COPIED TO, an unauthorized CPU for a period of days for backup and recovery functions (see " Installing on an Unauthorized or Backup CPU").

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.

    important

:

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.

Be aware : 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 INFO-RECOVERY

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 INFO-RECOVERY Itself​

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.

Declaring the IPKAUTH Module to TSO​

The module IPKAUTH has to be declared to TSO as an authorized module. This declaration may be done by the following two ways (same declaration as for IEBCOPY).

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.

The INFO-RECOVERY Environment

To make the maintenance easier, INFO-RECOVERY provides a mechanism for swapping from a test environment to a production one.

Because of this mechanism, no modification of JCL is necessary for testing new releases or new versions of a product.

Also, it is possible to instantaneously restore the previous environment.

This facility suppresses risks as well as all of the updates associated with maintaining the product.

An environment is entirely defined by a PARMLIB.

A PARMLIB contains:

  • all "user dependent" information,

  • the name of the loadlib modules of INFO-RECOVERY.

The default environment is the one generated by the APPLY function (see APPLY - Default parmlib), or by the operation Customizing the Modules. This environment is used in batch processing, and it is generally the production one (A environment).

The default environment is usually the oldest. This default may be changed by:

  • using a DD card CSXPLIB for batch processing,

  • using the configuration panel under ISPF.

The current environment is the one actually used by INFO-RECOVERY. Initially, it is the default environment, but this may be changed by:

  • using the user configuration under ISPF,

  • using TEST and TLIB parameters of the PRODUCTS member (in the parmlib).

Generally, this test environment is created during the installation process (B environment).

Product Installation Diagrams

After installation:


- LINKLIST/CSXEXEC (default)
|
|
|
B-ENV | A-ENV
+\-\-\-\--+ +\-\-\-\-\-\-\-\-\-\-\-\--\>+\-\-\-\--+
| | | |
| | | |
| | (any user) | |
| | | |
| | | |
| | | |
| | | |

After receiving a new version of INFO-RECOVERY (product tape):


- LINKLIST/CSXEXEC (default)
|
|
your profile |
| B-ENV | A-ENV
+\-\-\-\-\-\-\-\-\-\-\-\--\>+\-\-\-\--+ +\-\-\-\-\-\-\-\-\-\-\-\--\>+\-\-\-\--+
| C | | |
| H | | |
(you) | A | (other users) | |
| R | | |
| G | | |
| E | | |
| M | | |
Tape \-\-\-\-\--\> | E | | |
| N | | |
| T | | |

- LINKLIST/CSXEXEC (default)
|
|
your profile |
| B-ENV | A-ENV
+\-\-\-\-\-\-\-\-\-\-\-\--\>+\-\-\-\--+ +\-\-\-\-\-\-\-\-\-\-\-\--\>+\-\-\-\--+
| R | | |
| E | | |
(you) | C | (others users) | |
| E | | |
| I | | |
| V | \<\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- | |
| E | customization | |
+\-\-\-\--+ report +\-\-\-\--+

During tests of the B environment by another user:


- LINKLIST/CSXEXEC (default)
|
|
your profile |
| B-ENV | A-ENV
+\-\-\-\-\-\-\-\-\-\-\-\--\>+\-\-\-\--+ +\-\-\-\-\-\-\-\-\-\-\-\--\>+\-\-\-\--+
| | | |
| | | |
- test of | | (other users) | |
the product | | | |
| | | |
(you) | | | |
| | | |

During tests of the B environment by all users:

TEST=Y on the A environment (parmlib management panel)


- LINKLIST/CSXEXEC (default)
|
|
|
(any user) B-ENV | A-ENV
+\-\-\-\--+\<\-\-\--+ +\-\-\-\-\-\-\-\-\-\-\-\--\>+\-\-\-\--+
| | | | |
| | | TEST=Y\-\-\--\> |
- test of | | | | |
the product | | +\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--TPLIB|
| | return | |
| | | |
| | | |

After the execution of an UPGRADE command that specifies the A as the production environment of the B environment:


- LINKLIST/CSXEXEC (default)
|
|
your profile |
| B-ENV | A-ENV
+\-\-\-\-\-\-\-\-\-\-\-\--\>+\-\-\-\--+\<\-\-\-\-\-\-\-\--+ +\-\-\-\--+
| U | | |
| P | | |
| G | | |
(any user) | R ═════════════════════════════\> |
| A | | |
| D | | |
| E | | |

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.
\...\.....,
\...\.....)

Description of the parameters​

{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, as explained in chapter: The INFO-RECOVERY Environment.

    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.

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\...
\...

Description of the parameters​

{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 (see Calling User Procedures).

    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 (see Calling User Procedures). 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.

IMSIDS - IMS System Description​

You may adapt the IMSIDS member using one entry for each IMS system running the products. If IMS is not used, skip this section.

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

Syntax​



* Comment.
I1 IMSID=imsid, IMS imsid.
ALIAS=alias, cataloged alias for IC/CA dsn(s).
* (must be \<= 8 characters).
LEVEL=level, IMS level: B10 for V11,
* C10 for V12, D10 for V13,
E10 for V14.
OPTIMIZE=Y/N, IC optimization choice.
DUMMYDB=dummydb, Dummy DB for OLDS switch.
PSBNAME=(psb1,\...), Pool list of AOP PSBs.
TRNNAME=(trn1,\...), The associated transactions.
AGNAME=agn, Application Group name.
DBRCFORC=Y/N, DBRC mandatory (Y/N).
DBCTL=Y/N, The automatic operator DBCTL
* to be used or not.
DBDLIB=dbdlib, IMS dbdlib dsname.
PSBLIB=psblib, IMS psblib dsname.
ACBLIB=acblib, IMS acblib dsname.
MACLIB=maclib, IMS maclib dsname.
PROCLIB=proclib, IMS proclib dsname.
RESLIB=reslib, IMS reslib dsname.
DYNLIB=dynlib, IMS DB dynamic allocation library
* dsname.
AMSLIB=amslib, AMS source library for
* RECONs datasets.
RECONLIB=reconlib, Recon dynamic allocation library
* dsname.
CS1RECON=cs1recon, VIC recon dsname. (One per DBRC)
CS1RECVO=cs1recvo VIC recon volume.
* Comment.
I2 IMSID=imsid, A second entry\...
\...

Description of the parameters​

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

  • IMSID=imsid

    IMSID= is the identifier of the IMS system described by the parameters that follow.

  • ALIAS=alias

    ALIAS= is a catalog (ICF) for image copies and change accumulation dsnames. All INFO-RECOVERY data sets of this type will begin with this ALIAS.

    The alias has to be less than or equal to 8 characters.

  • LEVEL=level

    specify here the IMS level used on the site; specify -B10 for IMS V11 - C10 for IMS V12 - D10 for IMS V13 -- E10 for IMS V14.

    Default parameter : B10

  • OPTIMIZE=Y/N

    OPTIMIZE= allows to optimize the choice of the IC used by the recovery. OPTIMIZE selects the most recent IC for recovery when there are no allocations between two IC's.

    Default parameter: N

  • DUMMYDB=dummydb

    DUMMYDB= allows the switch of the OLDS. No real DBD is attached; see PSBNAME below.

    Default parameter: SWITCH

  • PSBNAME= (psb1,.)

    PSBNAME= defines a pool of reserved PSBs for InfoVic. This pool defines the maximum parallelism for the product. It will wait for a free PSB if none is available.

    These PSBs are PSBs of the automatic operator and must be attached to a transaction, see TRNNAME below; each PSB is automatically created by the installation process.

  • TRNNAME= (trn1,.)

    TRNNAME= indicates different transaction names for each PSB.

  • AGNAME=agn

    specify the name of the application group that is authorized in case of security check by AGN (value AGNEXIT or RACFAGN in the SECURITY macro).

    Default parameter: NONE NONE(default) implies no AGN security is used.

  • DBRCFORC=Y/N

    DBRCFORC= indicates whether or not DBRC control is mandatory (IMS defined with DBRC=FORCE in macro IMSCTRL).

    Default parameter: N

  • DBCTL=Y/N

    to specify if the automatic operator of DBCTL commands is to be used or not. This operator is mandatory in an environment without IMS/DC and can be used from versions

    CICS/ESA Version 4.1 IMS/ESA Version 5.1 and above.

    Default parameter: N

  • DBDLIB=dbdlib

    DBDLIB= allows the automatic search of necessary information at the time of automatic JCL generation. If you have several DBDLIBs for one IMS, choose the one that is usually used by DBRC.

  • PSBLIB=psblib

    PSBLIB= will receive PSBs created by INFO-RECOVERY.

  • ACBLIB=acblib

    ACBLIB= will receive ACBs created by INFO-RECOVERY.

  • MACLIB=maclib

    MACLIB= is the maclib used by the utility PSBGEN.

  • PROCLIB=proclib

    PROCLIB= is the proclib associated to this IMS.

  • RESLIB=reslib

    RESLIB= is the reslib associated to this IMS.

  • DYNLIB=dynlib

    DYNLIB= is the IMS library that contains the dynamic allocation members attached to the databases.

  • AMSLIB=amslib

    AMSLIB= is the IMS library that contains the delete/define members attached to the RECON data sets of DBRC.

  • RECONLIB=reconlib

    RECONLIB= is the IMS library that contains the dynamic allocation members attached to the RECON data sets, including DFSMDA modules RECON1, RECON2, RECON3.

  • CS1RECON=cs1recon

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

  • CS1RECVO=cs1recov

    CS1RECVO= is the volume attached to the RECON data set of InfoVic.

IMSDSGS - Description of the IMS Data Sharing Groups​

The IMSDSGS member allows you to describe the "data sharing groups" that are defined in SYSPLEX (IMS version 6 and later).

Customize the member IMSDSGS by specifying one entry per IMS data sharing group that uses the products. If you do not use the IMS data sharing, go to the next step.

Use the EDIT mode on member IMSDSGS.

Enter each parameter that is required.

Syntax​



* Comment.
I1 IMSDSG=imsdsgid, IMS DATA SHARING GROUP.
ALIAS=alias, Cataloged alias for IC/CA dsn(s).
* (must be \<= 8 characters).
LEVEL=level, IMS level: B10 for V11,
* C10 for V12, D10 for V13,
E10 for V14.
IMSREG=IMSG, control regions for BMP of group
* (IMSGROUP in DBC procedure)
SYSGRP=*ALL, system group name for route command
CRC=/, command recognition char (DEF.\"/\")
* (CMDCHAR in IMSCTRL MACRO)
OPTIMIZE=Y/N, IC optimization choice.
DUMMYDB=dummydb, Dummy DB for OLDS switch.
PSBNAME=(psb1,\...), Pool list of AOP PSBs.
TRNNAME=(trn1,\...), Associated transactions.
AGNAME=agn, Application Group Name.
DBRCFORC=Y/N, DBRC mandatory or not mandatory (Y/N)
DBCTL=Y/N, The DBCTL automatic operator.
* to be used or not.
DBDLIB=dbdlib, IMS DBDLIB dsname.
PSBLIB=psblib, IMS PSBLIB dsname.
ACBLIB=acblib, IMS ACBLIB dsname.
MACLIB=maclib, IMS MACLIB dsname.
PROCLIB=proclib, IMS PROCLIB dsname.
RESLIB=reslib, IMS RESLIB dsname.
DYNLIB=dynlib, IMS DB dynamic allocation library
* dsname
AMSLIB=amslib, AMS source library for RECONs
* datasets.
RECONLIB=reconlib, RECON dynamic allocation library
* dsname.
CS1RECON=cs1recon, VIC RECON dsname (one per DBRC)
CS1RECVO=cs1recvo VIC RECON volume.
* Comment.
I2 IMSDSG=imsdsgid, A second entry\...
\...

Description of the parameters​

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

  • IMSDSG=imsdsgid

    identifier of the IMS data sharing group; this name can be specified within the IMSID parameter of the EXEC card. When not using SYSPLEX, specify IMSDSG=NONE.

  • ALIAS=alias

    ALIAS= is a catalog (ICF) for image copies and change accumulation dsnames. All INFO-RECOVERY data sets of this type will begin with this ALIAS.

    The alias has to be less than or equal to 8 characters.

  • LEVEL=level

    specify here the IMS level used on the site; specify -B10 for IMS V11 - C10 for IMS V12 - D10 for IMS V13 -- E10 for IMS V14.

    Default parameter : B10

  • IMSREG=imsreg

    specify the name of the control regions for the BMPs of the IMS group (parameter IMSGROUP in the DBC procedure)

  • SYSGRP=sysgrp

    specify the name of the system group for the ROUTE command

  • CRC=crc

    specify the character to recognize the IMSs of the group (DEF."/") (parameter CMDCHAR in the IMSCTRL macro)

  • OPTIMIZE=Y/N

    to optimize the choice of the IC used by the recovery. OPTIMIZE selects the most recent IC for recovery when there are no allocations between two IC's.

    Default parameter: N

  • DUMMYDB=dummydb

    to switch the OLDS. No real DBD is associated with; see PSBNAME below;

    Default parameter: SWITCH

  • AGNAME=agn

    specify the name of the application group that is authorized in case of security check by AGN (value AGNEXIT or RACFAGN in the SECURITY macro).

    Default parameter: NONE (default) implies no AGN security is used.

  • DBRCFORC=Y/N

    DBRCFORC= indicates whether or not DBRC control is mandatory (IMS defined with DBRC=FORCE in macro IMSCTRL).

    Default parameter: N

  • DBDLIB=dbdlib

    DBDLIB= allows the automatic search of necessary information at the time of automatic JCL generation. If you have several DBDLIBs for one IMS, choose the one that is usually used by DBRC.

  • PROCLIB=proclib

    PROCLIB= is the proclib associated to this IMS.

  • RESLIB=reslib

    RESLIB= is the reslib associated to this IMS.

  • DYNLIB=dynlib

    IMS library that contains the dynamic allocation members attached to the databases.

  • AMSLIB=amslib

    AMSLIB= is the IMS library that contains the delete/define members attached to the RECON data sets of DBRC.

  • RECONLIB=reconlib

    RECONLIB= is the IMS library that contains the dynamic allocation members attached to the RECON data sets, including DFSMDA modules RECON1, RECON2, RECON3.

  • CS1RECON=cs1recon

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

  • CS1RECVO=cs1recvo

    CS1RECVO= is the volume attached to the RECON data set of InfoVic.

THT - Local Time Description​

Syntax​

The THT member is used to allocate the CS1THTAB data set that is specific to IMS functions. INFO-RECOVERY uses this data set for IMS version 6 (or later) that works in NOCOEX-mode. The CS1THTAB data set is automatically created by the installation process (installation of INFOREC1 using the interactive menu).

The CS1THTAB data set is used to manage the local time/hour thus memorizing the local time/hour intervals defined by their offsets, in number of quarters of an hour, related to the universal time.

The CS1THTAB data set is not dual and does not need to be saved because INFO-RECOVERY can easily reconstruct this data set.


*
CS1THTAB=cs1thtab, dsname of the THTAB data set
*
CS1THTVO=cs1thtvo, volume of the THTAB data set
*

Description of the parameters​

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

  • CS1THTAB=cs1thtab

    dsname of the CS1THTAB data set that is specific to INFOREC1 and INFOVIC; one single data set for the whole of IMS systems.

  • CS1THTVO=cs1thtvo

    volume associated with the CS1THTAB data set.

DB2IDS - DB2 System Descriptions​

You may 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.
OWNER=owner, owner of the plan.
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
DEFINENO=N, DEFINE NO option is used: Y/N
* for creating TS or IX.
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
DBINFOT=, database INFOTEL - DBSHADOW (to be specified
* if MasterCopy is installed)
CS2RECON=cs2recon, VIC recon dsname. (One per DB2)
CS2RECVO=cs2recvo VIC recon volume.
* Comment.
D2 DB2ID=DB2ID, A second entry\...
\...

Descripton of the parameters​

{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.

  • OWNER=owner

    Specify the owner of plan to used for the BIND. NONE (default value) means "no owner".

    Default parameter: NONE

  • 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

  • DEFINENO=Y/N

    This option must be set to Y if the DEFINE NO option is used when creating DB2 objects (TS and/or IX) on the specified DB2 Subsystem. If you set DEFINENO to N, please check that no DB2 object is defined using this option, otherwise you might get unpredictable results. Generally, this option is used on subsystems running SAP.

    Default parameter: N

  • 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

  • DBINFOT=,

    only provide a value for this parameter if the image copies are done with the MasterCopy product of INFOTEL. If yes, specify the same name of the database than the one specified in the DBSHADOW parameter of MasterCopy. Thus, INFO-RECOVERY can locate the images copies of the tablespaces in the DB2 catalog that usually are not notified in the SYSCOPY table. Default parameter: NONE

  • 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; this dataset is not dual but must be included by the user into the usual procedure for saving.

  • CS2RECVO=cs2recvo

    CS2RECVO= is the volume name of the InfoVic RECON.

DB2DSGS - Defining DB2 Data Sharing Groups​

Define DB2 data sharing groups when using data sharing in your environment.

The name of the DB2DSG is used to identify the DB2 sub-system where under INFO-RECOVERY is executed according to the system where the job is started.

Syntax​



* Comment.
D1 DB2DSG=NONE, GROUP ATTACHMENT NAME
DB2NAME=(\...,\...,\...), DB2 LIST
SYSNAME=(\...,\...,\...), SYSTEM LIST
*
D2 DB2DSG=NONE, GROUP ATTACHMENT NAME
DB2NAME=(\...,\...,\...), DB2 LIST
SYSNAME=(\...,\...,\...), SYSTEM LIST
*

Descripton of the parameters​

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

  • DB2DSG=db2dsg

    identifier of the DB2 data sharing group (group attachment name); this name can be set into the DB2ID parameter of the EXEC card.

    Specify DB2DSG=NONE when using INFO-RECOVERY in a non-SYSPLEX environment.

  • DB2NAME=(db21,...)

    Specifies the list of the DB2 IDs that belong to the data sharing group mentioned above; these DB2 IDs are to be specified in the member DB2IDS.

  • SYSNAME=(sys1,...)

    Specifies the list of systems where the DB2s of the group are processed.

    sysn is related to db2n

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.

Descripton of the parameters​

{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 swapable 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 SAMS) 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

  • MAXPRIM=

    Specifies the maximal primary allocation in cylinders for multi-volume data sets. If no value is specified, the image copy data set is created on one single volume.

    Default: NONE

  • MAXUNIT=

    Specifies the maximal number of disk volumes to be used for an image copy data set.

    Default: 2 (if a value has been specified for MAXPRIM).

  • 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 that 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

Description of the parameters​

{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 - cf: User Configuration under ISPF/TP).

  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).

If new products must be installed, their installation is described in these chapters:

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.

Reading the chapter Product Installation Diagrams will provide the necessary information for environment modifications, as well as the effects of the UPGRADE command.

General Installation Menu

Once the installation of InfoRec is finished, select option I (INSTALL) from the general menu of INFO-RECOVERY (see 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 InfoRec1​

Installation from IMS V14 when the IMS management of ABC is enabled​

Inforec and Infovic only use the DBDLIB - PSBLIB - ACBLIB - libraries. The content of those libraries must be refreshed regularly.

  • Before proceeding with the installation, carry out the operations described in the prerequisites for the DFS3PU00 utility.

  • Once the installation performed, and before the checking step, execute IMS Catalog Populate utility (DFS3PU00)

  • Then, execute IMS Catalog Library Builder utility (DFS3LU00) regularly and each time new ACB, PSB, DBD are created.

For more details about the DFS3PU00 and DFS3LU00 utilities, consult the IMS Version xx System Utilities documentation.

INFOREC1 installation​

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


INFO-RECOVERY - INFOREC1 Installation Panel
COMMAND ===\>
Test Option ===\> Y
Install parmlib \.... LABO.INFOREC.IR4500P
Imsid \...\...\...\...\...\... ===\> IM7A (specify an imsid or ALL)
Generate IMS environment ===\> N (Y/N)
Create THT dataset \..... ===\> Y (Y/N)
(for all IMS)
Press Enter to validate installation request or PF3/15 for exit

When option "Generate IMS environment" is specified (value Y), the installation service provides the generation of

  • the IMS generation deck to be included into your next IMS generation for the PSB VIC pool and the DUMMYDB defined during the customization of the IMSIDS member of the parmlib (member # GENIMSID);

  • the associated SMU deck (#SMUimsid);

  • each PSB of the PSB pool; these PSBs are added to the PSBLIB library specified in IMSIDS. Ensure that the MACLIB specified in IMSIDS is the same as the SYSLIB of your PSBGEN procedure.

  • each corresponding ACB; these ACBs are added to the ACBLIB library specified in IMSIDS.

Use this service again to modify the product's PSB names, if necessary.

The IMSIDS member of the current parmlib provides the description of all IMS systems (see: IMSIDS - IMS System Description).

Checking the InfoRec1 Installation​

All InfoRec1 product functions will be available as soon as the IMS generation includes the generated deck (this applies to the CS1RRORG function).

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

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

  2. Select option 1 (INIT) of InfoRec1.

    After the copyright message, type the following parameters with appropriate values on the command line:

     DB=(ABC*),CA=MYCAGRP,SHRLEVEL=2,TEST=Y

    Use PF3/15 to leave the menu.

  3. Select option 6 (MDISK) of InfoRec1.

    After the copyright message, enter the following parameters with their appropriated values on the command line:

     DSN=IMS*.*,VOL=(IMS*)

    Use PF3/15 to exit from this menu.

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 (see: User Configuration under ISPF/TP) 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 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 (see: PRODUCTS - Products Descriptionand Parmlib Management).

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.

Appendices

Parmlib Management​

You can assign a test environment to the current environment using option P (PARMLIB) on the general INFO-RECOVERY menu. The following panel is displayed:


INFO-RECOVERY - Parmlib management Panel
COMMAND ===\>
Default parmlib \...\.....
Current parmlib \...\.....
User profile parmlib \...
Test option \...\.....===\> (Y/N)
Test parmlib \...\....===\>
Press Enter to validate user profile parmlib values or PF3/15 for exit

Only the "Test option" and "Test parmlib" fields values can be modified thus leading to an automatic update of the member PRODUCTS of the current environment. This modification will apply to all users using this parmlib.

The TEST parameter allows the user to activate (Y) or to deactivate (N) the automatic use of the test parmlib by users. Thus this feature allows testing of new product versions without modifying the production environment, and, if any problem occurs, . to immediately switch back to the previous environment.

User Configuration under ISPF/TP​

Select option C (CONFIG) on the general menu of INFO-RECOVERY to modify default values. The following panel is displayed:


INFO-RECOVERY - User Profile Configuration
COMMAND ===\>
Parmlib library \....===\>
Imsid \...\...\...\.....===\>
db2id \...\...\...\.....===\>
Debug option \...\....===\> (Y/N) (Trace the clists and skeletons)
User library \...\....===\>
User option \...\.....===\> (Y/N) (Search ISPF objects in user library before)
Output kept size \...===\> (The number of output print pages to be kept)
Press Enter to validate a new configuration or PF3/15 for exit

Different values may be provided for the current parmlib, the target IMSID, or DB2ID may be modified.

Only the current user profile will be updated accordingly.

The special value IMSID,'NONE' avoids allocating an IMS environment and may only be used by users of mixed DL1/DB2 functions who do not need to access DL1 databases.

The special value DB2ID,'NONE' avoids allocating a DB2 environment and may only be used by users of mixed DL1/DB2 functions who do not need to access DB2 databases.

A DEBUG option traces user CLISTs if any problem occurs.

A user parmlib can be specified. This parmlib contains ISPF objects CLISTs, PANELs, MSGs, or SKELETONs, as well as customization members for INFO-RECOVERY functions that are specific to the user.

The scanning of this library is activated if "User option" is set to Y. In this case, a member found in the user library is used instead of a member in the parmlib with the same name.

Thus the user can define default parameters for the different functions of INFO-RECOVERY.

Members SYSIDS, IMSIDS, DB2IDS, PRODUCTS and CUSTOM cannot be masked by user members.

The printed output is displayed on a logical terminal where the number of pages can be defined by each user. When this number is reached, the first page is used again. The terminal is cyclic, and an automatic return to the first page is made at the end of the last page.

Edit​

The products parmlib contains all parameter values. Option E (EDIT) on the general INFO-RECOVERY menu allows a direct access to edit the current parmlib.

Remember that any change made to the parmlib is general for all users and therefore requires special care. The following member names are reserved names for the products:

  ##CHANGE -        List of changes to products
  #CSJ.... -        Installation jobs of products
  CSK..... -        Skeletons for installation of products
  CSL..... -        Dlibs description of products
  CSM..... -        ISPF msgs of products
  CSP..... -        ISPF panels of products
  CSQ..... -        SQL statements for products
  CSR..... -        XPROC procedures for products
  CSS..... -        Skeletons for use of products
  CSU..... -        Clists for use of products
  CSn..... -        Default members for CSn product functions
  CTRLRUN  -        Batch control run member
  CUSTOM   -        Global customization
  DB2IDS   -        Description of DB2s
  IMSIDS   -        Description of IMSs
  JOBCARD  -        JOB card user clist
  PRODUCTS -        Description of products
  SYSIDS   -        Description of MVSs

Logical Terminal​

The INFO-RECOVERY functions use a logical terminal to communicate with the user.

The logical terminal is displayed each time you select an INFO-RECOVERY function from the TP interface.

The illustration below shows a logical terminal:


INFO-RECOVERY - Logical Terminal
COMMAND ===\>
Page 1/1 Cols 1 to 80
CS1INIT - 91/09/05 12.10 PRODUCT INFOREC1

The execution of an INFO-RECOVERY function starts when entering its parameters into the command field of the logical terminal. The execution processes and the output report is displayed on the terminal. For example: enter TS=(mydb*.myts*),ID=MYVIC to start a VIC point processing.

The number of pages to preserve is set by the user using option C (CONFIG) on the main INFO-RECOVERY menu.

The following commands are available:

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

  • PF7/19 (UP)

    to display the previous page

  • PF8/20 (DOWN)

    to display the next page

  • PF10/22

    to display the previous command

  • PF11/23

    to display the next command

  • ENTER

    to display columns 52 to 132 and to return to columns 1 to 80

During its execution, a command is automatically changed into a comment by inserting a *. To re-execute the command, blank out this character.

Calling User Procedures​

INFO-RECOVERY allows the user to call user CLISTs or REXX procedures

  • if they are located in the parmlib of INFO-RECOVERY (current parmlib or user parmlib).

  • if the two libraries of clists and REXX procedures are defined in the member SYSIDS of the parmlib by the following parameters:

    • PROCLIB for clists

    • EXECLIB for REXX procedures

These libraries will be allocated dynamically by INFO-RECOVERY with the ddnames:

  • SYSPROC and SYSEXEC in batch mode

  • PRLIB and EXLIB in interactive mode

Direct Call​

A clist or a REXX program can directly be called by a function of INFO-RECOVERY. How to do:

  • for the IMS environment

    indicate its name in the CLIST parameter

  • for the DB2 environment

    create an XPROC procedure in the parmlib with the following syntax: "EXEC=CLIST, NAME=clist or rexx procedure name" and to specify the name (CSR*) of this procedure in the PROC parameter of the function.

The search processing is performed within four libraries in the following order:

  1. user parmlib

  2. current parmlib

  3. library of user CLISTs

  4. library of user REXX programs

Indirect Call​

A later call using a clist belonging to the parmlib can be made according to the execution mode, either batch or interactive.

In batch mode, it is possible to call the clist or REXX proc. without specifying the dsname of the library that contains the member (by using %member). The search of the member will be made in SYSEXEC, and then in SYSPROC.

In interactive mode, calls have to contain dsnames of libraries (they are transmitted in CPRLIB and CEXLIB ISPF variables):

  • EXEC '&CPRLIB(clist)'

or

  • EXEC '&CEXLIB(rexx)' EXEC

If you don't want to mention the dsname of these libraries, you then need to allocate them in the TSO logon procedure.

Nevertheless, the last two calls are also valid in batch mode.

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 or PASSTARC procedure​

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 return code 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 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.