Installing CBPDO

You install all the elements from the CICS® TS CBPDO using a single installation process. The CBPDO Memo to Users Extension contains information about the CBPDO you ordered, and the features and service it includes. It also contains CBPDO installation information.

The first planning task is to read the Memo to Users Extension thoroughly before starting any of the install tasks. If you are a new user of CBPDO, you should also read the IBM® publication, MVS Custom-Built Offerings Planning and Installation, SC23-0352.

The CICS Transaction Server for z/OS: Program Directory gives a sample IEBCOPY job that you can customize to copy RELFILE(2) from the CICS TS CBPDO tape. Modify the LABEL=3 parameter to reference the file number of RELFILE(2) as supplied on the CBPDO tape. When you have copied RELFILE(2) to DASD, you generate a single set of install jobs using the CICS TS job generator, DFHISTAR. This generates the following set of customized install jobs, based on the parameters you specify to DFHISTAR:

using the SMP/E RECEIVE, APPLY, and ACCEPT commands

The CICS Transaction Server for z/OS: Program Directory describes this process and tells you when to return to the CICS Transaction Server for z/OS Installation Guide to continue..

using the DFHISTAR process

Edit the DFHISTAR Job describes all the parameters that you can specify to customize the install jobs, and explains the jobs that are generated.

One of the most significant parameters you are asked to specify is the high-level qualifier for the data sets into which the jobs install the product. CICS TS comprises a number of elements that are installed in a single process by the DFHINSTn jobs. To ensure the element libraries are easily identified, DFHISTAR adds an element qualifier to the data set names. Using the default high-level qualifier CICSTS31, the names generated by DFHISTAR take the following form:

CICS
CICSTS31.CICS.ddname
CICSPlex® SM
CICSTS31.CPSM.ddname
Application Migration Aid
CICSTS31.AMA.ddname
REXX for CICS
CICSTS31.REXX.ddname

To enable you to customize the HFS-related jobs, the following parameters are provided in the DFHISTAR job:

HFS0DSN
The data set name of the HFS to be mounted at directory Start of change/pathprefix/usr/lpp/cicstsEnd of change. Pathprefix is variable, and optional, The other parts of this directory name structure are fixed. The default data set name is OMVS.USR.LPP.CICSTS.

This parameter is used by job DFHIHFS0.

HFS1DSN
The data set name of the HFS to be mounted at directory Start of change/pathprefix/usr/lpp/cicsts/End of changeussdir, where ussdir is a variable you specify in the ussdir parameter in DFHISTAR. If you omit the ussdir parameter it defaults to the value of the TINDEX parameter in lowercase, which in turn defaults to CICSTS31, so if both defaults are taken, the full directory path resolves to Start of change/pathprefix/usr/lpp/cicsts/End of changecicsts31.

The default data set name is OMVS.USR.LPP.CICSTS.CICSTS31.

This parameter is used by job DFHIHFS1.

HFSADSN
The data set name of the HFS to be mounted at directory Start of change/pathprefix/usr/lpp/cicsts/End of changeussdira, where ussdira is a variable you also specify in DFHISTAR. If you omit the ussdira parameter it defaults to the value (in lower case) of AINDEX, which in turn defaults to CICSTS31.A. The default data set name is OMVS.USR.LPP.CICSTS.CICSTS31.A.

This parameter is used by job DFHIHFSA.

Running the install jobs

Run the install jobs as follows:

  1. Run the HFS-related jobs to create the HFS directories down to the /cicsts31 level:
    DFHIHFS0 (required once only)
    This job creates the HFS specified on the HFS0DSN parameter and also the /cicsts directory at /pathprefix/usr/lpp.

    This job is required once only, the first time you install CICS TS, and can be skipped in subsequent releases.

    Note:
    When you install a new release of z/OS®, directories down to the /pathprefix/usr/lpp level are replaced, effectively losing the /cicsts and lower directories. Issue the make directory command (mkdir /pathprefix/usr/lpp/cicsts) to recreate mount point /pathprefix/usr/lpp/cicsts for the HFS defined in DFHIHFS0 (OMVS.USR.LPP.CICSTS). The mount command should already be in the PARMLIB member BPXPRMxx, copied from the DFHBPXP0 member of SDFHINST.
    DFHIHFS1 (required)
    This job creates, at /pathprefix/usr/lpp/cicsts, the HFS specified on the HFS1DSN parameter and also the directory specified on the parameter (default name /cicsts31).
    DFHIHFSA (optional)
    This job creates, at /usr/lpp/cicsts, the alternate HFS specified on the HFSADSN parameter and also the directory specified on the ussdira parameter (default name /cicsts31.a).
  2. Run DFHISMKD to create the directories and HFS under /pathprefix/usr/lpp/cicsts/cicsts31, required for FMID JCI640D, to contain the Java™ and IIOP classes, samples, and so on, that have to reside in HFS.
  3. Run the DFHINST1 through DFHINST4 jobs as described in the Program Directory
  4. Run the CBPDO-supplied SMP/E RECEIVE job, RCVPDO, located in the CBPDO RIMLIB dataset (this replaces the DFHINST5 job described in the Program Directory).
  5. Run the DFHINST6 job.
    Note:
    This job must run in the same MVS™ image in which you ran the DFHISMKD job to create the HFS directories. DFHINST6 uses the CICS TS HFS directories and data sets, and these are accessible only in the MVS in which you created them.

There is more detailed information about all these jobs in the CICS TS CICS Transaction Server for z/OS Program Directory, and also in the comments at the start of each job.

On completion of the installation jobs, you have all the elements installed. Note that there is no provision within the DFHISTAR job generator, or in the generated jobs, to exclude an element from the install process. When you run the jobs, SMP/E installs all the elements included on the CICS TS CBPDO tape.

By default, SMP/E installs CICS TS in new SMP/E global, target, and distribution zones. The DFHINST3 job creates a new CSI data set for each zone. If you want to vary this default SMP/E configuration, see the CICS Transaction Server for z/OS Program Directory for information about the parameters that control the SMP/E zones and the disposition of the CSI data sets.

[[ Contents Previous Page | Next Page Index ]]