Prerequisites for installing CICS TS

Hardware requirements

Whether you choose the CBPDO method or the ServerPac method, the hardware requirement is the same. The amount of storage required for all the target and distribution data sets is detailed in the space table in the Program Directory.

You require a z196 or subsequent 64 bit z/Architecture processor with a configuration that has a terminal, and a tape device capable of reading the following type of tape on which CICS® TS is supplied:

1/2 CST-IBM 3590-128 Track

Software requirements

The system software requirements for installing CICS TS using the ServerPac method or the CBPDO method are the same except for the addition of SMP/E for CBPDO. You must install z/OS®, Version 2 Release 2 or a later release on the system that you use to install both the ServerPac and the CBPDO.

z/OS includes the following elements that are required for installing CICS TS:

  • Interactive System Productivity Facility (ISPF)
  • Time Sharing Option/Extended (TSO/E)
  • DFSMS/MVS
  • Language Environment®
  • Two components of z/OS Communications Server: SNA and IP (previously VTAM® and TCP/IP)
  • z/OS UNIX System Services

If you are installing CICS TS using the CBPDO method, you also require:

  • System Modification Program/Extended (SMP/E)
  • High Level Assembler/MVS & VM & VSE.

For information about optional supported software and the service that you must apply to ensure that CICS TS installs correctly, see Detailed system requirements.

z/OS UNIX file system and PDSE requirements

Some components are installed in PDSE data sets and z/OS UNIX files, which affects the installation process.

CICS TS for z/OS, Version 5.5 requires PDSE data set support for installation to complete successfully. DFSMS/MVS, which is supplied as an element of z/OS, provides this support for PDSE data sets. For FMID HCI7200, which contains the z/OS UNIX-dependent code, the OMVS address space must be active in full-function mode, otherwise the installation of this function fails.

In the set of installation jobs, some initial jobs create the z/OS UNIX files and the directories shown in Figure 1. Run these jobs before any of the normal DFHINSTn jobs. The user ID running these jobs requires superuser authority.

Figure 1. The z/OS UNIX directory structure for CICS
The figure shows a directory hierarchy with a top level name of /pathprefix. It has a subordinate directory identified as /usr. The /usr directory has one subordinate directory identified as /lpp. The /lpp directory contains a /cicsts directory at the fourth level. This contains a directory for each release of CICS.
  1. If you normally maintain additional SMP/E target zone libraries to apply service, you can also create additional directories at the /cicsts55 level to create the z/OS UNIX equivalent. See the DFHIHFSA job for more information.
  2. The /pathprefix in Figure 1 is optional.