Run the installation Jobs

OMVS requirement

Before running the installation jobs:

After you have run the DFHISTAR job to create the installation jobs, submit those jobs in sequence to install CICS Transaction Server. This § describes the CICS Transaction Server installation jobs, and gives considerations that may affect how you use them.

The CICS Transaction Server jobs are in the CICSTS31.XDFHINST library as a result of running the DFHISTAR job, which you copied from the distribution tape, as described in the topic Copy RELFILE(2) from the Distribution Tape in the Program Directory.

These jobs should be run one at a time. Before you run a job, read the information about it (starting in topic DFHIHFS0).

After you have run a job, check its output before proceeding to the next job. If a job terminates abnormally, find out why it failed (the job log lists the error messages produced on each run). Correct the error, and then proceed as advised in the job description. In any case, do not attempt to run the next job until the previous job has run successfully.

Run Times of the Installation Jobs

To give you an idea what run times to expect, we ran the installation jobs on an IBM® 9672 RX5 using a single LPAR. The run times were:

Job Processor Time Elapsed Time
DFHIHFS0 1 second 7 seconds
DFHIHFS1 1 second 7 seconds
DFHISMKD 1 second 1 second
DFHINST1 3 seconds 30 seconds
DFHINST2 3 seconds 30 seconds
DFHINST3 1 second 15 seconds
DFHINST4 1 second 15 seconds
DFHINST5 1 minute 11 minutes
DFHINST6 24 minutes 49 minutes

These time values are suitable to run the installation jobs on an IBM 9672 RX5 or bigger system. If you have a system smaller than an IBM 9672 RX5, you may need to review these values.

The DFHIHFS0 Job

This job:

Notes:
  1. DFHIHFS0 only ever needs to be run once.
  2. RACF® ALTER ACCESS to the OMVS data sets must be granted before running this DFHIHFS0.
  3. The /cicsts directory is common to all releases of CICS® TS from 1.3 onwards.
  4. The /cicsts directory contains only directories, each being a mount point.
  5. CICS requires the MOUNT issued by DFHIHFS0 to access files stored in the HFS, but the MOUNT command is lost when you re-IPL MVS. SDFHINST member DFHBPXP0 contains a MOUNT command for /pathprefix/usr/lpp/cicsts. Copy this command into a BPXPRMxx member of the SYS1.PARMLIB dataset to ensure the mount is restored when MVS is IPLed.
  6. All steps of DFHIHFS0 must end with return code zero for the job to be successful.

The DFHIHFS1 Job

This job:

All steps of DFHIHFS1 must end with return code zero for the job to be successful.

CICS requires the MOUNT issued by DFHIHFS1 to access files stored in the HFS, but the MOUNT command is lost when you re-IPL MVS. SDFHINST member DFHBPXP1 contains a MOUNT command for /pathprefix/usr/lpp/cicsts/ussdir. Copy this command into a BPXPRMxx member of the SYS1.PARMLIB dataset to ensure the mount is restored when MVS is IPLed.

The DFHISMKD Job

This job creates the UNIX System Services directories.

This job must be run before any of the other installation jobs.

The highest expected return code is 0.

The DFHINST1 Job

This job allocates and catalogs CICS Transaction Server distribution and target libraries.

To ensure that this job can be rerun, it deletes (and uncatalogs) the data sets that are allocated in the second step of the job.

If the DFHINST1 job terminates abnormally, examine the job log to determine the cause, correct the problem, then rerun the job.

The highest expected return code is 0.

The DFHINST2 Job

This job allocates the CICS Transaction Server RELFILE data sets. If you run the DFHINST2 job now, you ensure that enough space has been allocated to the RELFILE data sets to allow the DFHINST5 job to complete.

To ensure that the job can be rerun, it deletes (and uncatalogs) the data sets (if they exist) that it allocates later.

If the DFHINST2 job terminates abnormally, examine the job log to determine the cause, correct the problem, then rerun the job.

The highest expected return code is 0.

DFHINST3 and DFHINST4 jobs.

DFHINST3 is a job that should be run if you have decided to allocate new SMP/E zones.

Be aware that the default specified in DFHISTAR is for the allocation of new zones. This is recommended, to ensure that existing releases of CICS Transaction Server are not deleted.

DFHINST4 is a job that will prime new SMP/E zones created in DFHINST3.

The DFHINST3 Job

This job allocates the CICS Transaction Server SMP/E data sets.

Before you run the DFHINST3 job

If you intend installing CICS Transaction Server using both existing and new CSIs, any new CSIs must have the same control interval size as the existing CSIs.

Caution:
If you intend using an existing target or distribution zone that contains an earlier release of CICS Transaction Server elements, be aware that any earlier release of CICS will be cleared before being replaced by CICS Transaction Server.

If your existing CSIs do not have a control interval size of 4096 bytes, you must edit the DFHINST3 job (before running it) to change the CONTROLINTERVALSIZE(4096) parameter on the commands used to create the VSAM data sets for the new CSIs, to specify the same control interval size as the existing CSIs.

For further information about considerations for allocating CSI data sets, see the System Modification Program Extended: Reference manual, SA22-7772.

To ensure that the job can be rerun, it deletes (and uncatalogs) the data sets (if they exist) that it allocates later.

This job also sets up the global, target, and distribution zones, depending on the parameters that you specified to the DFHISTAR job, as follows:

  1. If you specified NEW for GZONE, the global zone is deleted and redefined.
  2. The distribution zone is deleted and redefined.
  3. The target zone is deleted and redefined.
  4. Member GIMZPOOL from SYS1.MACLIB is REPROed into the zones redefined in the previous steps.
  5. If you specified OLD for GZONE, the entries for the DZONE and TZONE names are removed from the global zone.

If the DFHINST3 job terminates abnormally, examine the job log to find the cause, correct the problem, then rerun the job.

The highest expected return code is 0.

The DFHINST4 Job

This job primes the global zone, target zone, and distribution zone.

Before you run the DFHINST4 job

If you did not run the DFHINST2 job, increase the DSSPACE values in the DFHINST4 job, before submitting it.

If the DFHINST4 job terminates abnormally, examine the job log to determine the cause, correct the problem, then repeat all jobs, beginning with DFHINST1. This avoids SMP/E space problems, and consequent X37 abends, during reruns of these SMP/E jobs.

The highest expected return code is 0, if you install into new zones and 8 if you are installing into existing zones.

The DFHINST5 Job

This job RECEIVEs the CICS Transaction Server software from the distribution tape into the RELFILE data sets created by the DFHINST2 job. It is the only installation job (apart from the initial IEBCOPY job) that requires the distribution tape to be mounted.

If the DFHINST5 job terminates abnormally, examine the job log to determine the cause, correct the problem, then repeat all jobs, beginning with DFHINST1. This avoids SMP/E space problems, and consequent X37 abends, during reruns of these SMP/E jobs.

The highest expected return code is 0.

The DFHINST6 Job

This job performs the SMP/E APPLY and ACCEPT functions needed to install CICS Transaction Server into the target and distribution libraries respectively.

Before you run the DFHINST6 job

The DFHINST6 job is the longest running of all the installation jobs (see Run Times of the Installation Jobs), and produces a large amount of printed output. The region size for the DFHINST6 job is currently set to 'REGION=0M'. This is because this job requires more memory than the other install jobs. You may need to adjust your JES parameters (for example, with a JES2 /*JOBPARM LINES=99 statement) to avoid a system abend 722.

This job gives a return code of 4 when all is well. (See the "GIM23903W - LINK SUCCESSFUL . . " message, listed in the report that is output by the apply job.) DFHINST6 job may issue messages GIM23903W and GIM23913W depending on the execution environment of the installer. Both these messages are acceptable.

The binder produces IEW2454W messages during the APPLY stage for unresolved external references while some CICS Transaction Server load modules are being link-edited during installation, giving return code 4. You may also receive numerous IEW2646W and IEW2651W messages, which are conflicts with user-specified RMODE and AMODEs respectively. You can ignore these IEWxxxx messages, which are output for component object modules of executable CICS Transaction Server load modules.

Messages IEW2689W, IEW2470E, IEW2648E and IEW2303E might be displayed, and can also be ignored.

When you have run the DFHINST6 job, you should see the following SMP/E message in the output from the job:

GIM20502I  GIMSMP PROCESSING IS COMPLETE - THE HIGHEST RETURN CODE WAS 04 -

This SMP/E message can be ignored.

If any other SMP/E messages appear, see the SMP/E: Messages & Codes manual for guidance information about their meaning, and take the appropriate action.

If the DFHINST6 job terminates abnormally, examine the job log to determine the cause, correct the problem, then repeat all the jobs, beginning with DFHINST1. This avoids SMP/E space problems, and consequent X37 abends, during reruns of these SMP/E jobs.

Note:
If the DFHINST6 job fails and you are using an existing global zone (that is, you specified the GZONE parameter of the DFHISTAR job with the disposition parameter OLD), you must first REJECT the CICS Transaction Server base-level function SYSMOD before rerunning the DFHINST1 job. When you rerun the installation jobs, some steps that were successfully completed in the previous run will produce return codes with a value of ‘8’.

The DFHIJVMJ Job

This job is provided to create a customized version of member DFHJVMEV from the SDFHENV data set. This dataset contains the JVM environment variables that are needed if you want to run a JVM program in CICS. Information about the JVM environment variables is given in the CICS System Definition Guide.

[[ Contents Previous Page | Next Page Index ]]