Running the installation jobs

Check that you are ready to run the installation jobs and then submit the jobs in sequence. When you have successfully run all of the installation jobs, CICS® is loaded.

Before you run the installation jobs, read and run the included README file. Ensure the following settings are in place:
  • The z/OS® image was IPLed with OMVS in full-function mode.
  • The user ID under which you are running the jobs has superuser authority.

After you have run the DFHISTAR job to create the installation jobs, submit those jobs in sequence to install CICS Transaction Server.

The CICS Transaction Server jobs are in the CICSTSnn.XDFHINST library, where nn reflects the release of CICS. For example, CICSTS64.XDFHINST for CICS TS beta This is as a result of running the DFHISTAR job, which you copied from the distribution tape, as described in Copy RELFILE(2) from the Distribution Tape in the Program Directory.

Run these jobs one at a time. Before you run a job, read the information about it, starting with Running the DFHIHFS0 job.

The sample job, DFHINSTJ, is supplied for loading optional features. CICS contains no optional features at General Availability but you can use the sample job if any optional features are shipped at a later date.

After you run a job, check its output before proceeding to the next job. If a job ends abnormally, find out why it failed by looking at the job log, which lists the error messages produced on each run. Correct the error and then proceed as advised in the job description. Do not attempt to run the next job until the previous job has run successfully.

After you run all the jobs, CICS Transaction Server is installed on your DASD. Back up the volume on which CICS Transaction Server resides. If any errors occur during customization later, you do not have to re-run the installation jobs.