Installing the CICS TS base component

You install a base component and an activation module for the CICS® edition that you use. The activation module and the base component can be installed in any order but they must both be installed before you can run installation verification procedures. The ServerPac distribution of CICS TS base component can be installed through z/OSMF. The CBPDO distribution of CICS TS base component can be installed through customized installation jobs that are created by using DFHISTAR.

Installing the CICS TS base component from ServerPac

The ServerPac distribution of CICS TS can be installed through z/OSMF. You receive the package, customize the installation information (for example, you can define the names of the SMP/E zones into which you want to install CICS TS, define values for the installation variables used in skeleton batch jobs, and define catalog data set names and the aliases associated with them, among many other options), then deploy the installation.

z/OSMF is a driving system requirement. It must be up and running on at least one of your systems and you have the necessary authority to use it. Find information about preparing z/OSMF, downloading the ServerPac, configuring and deploying the installation in ServerPac Installation using z/OSMF.

Installing the CICS TS base component from CBPDO

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. Read the Memo to Users Extension before you start the installation tasks.

The Program Directory gives a sample IEBCOPY job that you can customize to copy RELFILE(2) from the CICS TS CBPDO.
  1. Modify the LABEL=3 parameter to reference the file number of RELFILE(2) as supplied on the CBPDO tape.
  2. When you have copied RELFILE(2) to DASD, you generate a single set of installation jobs using the CICS TS job generator, DFHISTAR.
  3. This generates the following set of customized installation jobs, based on the parameters you specify to DFHISTAR:
  • DFHIHFS0, DFHIHFS1, DFHIHFSA, and DFHISMKD, the z/OS UNIX-related jobs
  • DFHINST1 through DFHINST6

The process for using the SMP/E RECEIVE, APPLY, and ACCEPT commands is explained in the Program Directory for CICS Transaction Server. See Find the Program Directories.

DFHISTAR provides default qualifiers for the data sets into which you install CICS TS. The DFHISTAR job provides several parameters to enable you customize your settings.

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. The names that are generated by DFHISTAR have a default high-level qualifier that reflects the release of CICS TS in use. For example, for CICS TS beta, the prefix is CICSTS64. The list below uses the latest release as an example. If you use a different release, the prefix matches the number of that release.
CICS
CICSTS64.CICS.ddname
CICSPlex SM
CICSTS64.CPSM.ddname
REXX for CICS
CICSTS64.REXX.ddname
To enable you to customize the z/OS UNIX-related jobs, the DFHISTAR job provides the following parameters:
HFS0DSN
The data set name of the file system to be mounted at directory /pathprefix/usr/lpp/cicsts. 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.

The DFHIHFS0 job uses this parameter.

HFS1DSN
The data set name of the file system to be mounted at directory /pathprefix/usr/lpp/cicsts/ussdir, where ussdir is a variable that 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. In turn, TINDEX defaults to the prefix for your release of CICS TS; for example, CICSTS64 for CICS TS beta. As a result, if both defaults are taken, the full directory path resolves to /pathprefix/usr/lpp/cicsts/cicstsnn, where nn is the release of CICS TS: for example cicsts64 for CICS TS beta. The default data set name is OMVS.USR.LPP.CICSTS.CICSTSnn, where nn is the release of CICS TS: for example, CICSTS64 for CICS TS beta.

The DFHIHFS1 job uses this parameter.

HFSADSN
The data set name of the file system to be mounted at directory /pathprefix/usr/lpp/cicsts/ussdira, where ussdira is a variable that you also specify as a parameter in DFHISTAR. If you omit the ussdira parameter, it defaults to the value (in lowercase) of aindex which, in turn, defaults to CICSTSnn.A, where CICSTS64nn is the release of CICS TS: for example, the default data set name for CICS TS beta is OMVS.USR.LPP.CICSTS.CICSTS64.A.

The DFHIHFSA job uses this parameter.

Editing the DFHISTAR job describes all the parameters that you can specify to customize the installation jobs, and explains the jobs that are generated.