Requirements for CICS TS

A major part of your planning effort involves looking at the software and hardware required for the system that you are installing.

Hardware requirements for installing CICS TS

Whether you choose the CBPDO method or the ServerPac method, the hardware requirement is the same.

Hardware requirements are more fully described in the CICS® Transaction Server for z/OS® Release Guide

You need a hardware configuration that runs the required levels of MVS™, provided the configuration has a terminal and a tape device capable of reading one of the following types of tape on which CICS TS is supplied:

Software requirements for installing CICS TS

The system software requirements for installing CICS TS using the ServerPac method or the CBPDO method is the same except for the addition of SMP/E for CBPDO.

Software requirements are more fully described in the CICS Transaction Server for z/OS Release Guide

The products shown in Table 3 must be installed on the system you use to install both the ServerPac and the CBPDO.

Table 3. Program products required on the installing system for ServerPac and CBPDO
Program Product Minimum Level
z/OS (5694-A01) Version 1 Release 4.

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 eNetwork Communications Server: SNA and IP (previously VTAM® and TCP/IP).
  • z/OS UNIX system services (see HFS and PDSE requirements for more information.

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

  • System Modification Program/Extended (SMP/E)
  • High Level Assembler/MVS & VM & VSE.
Service note::
See the CICS Transaction Server for z/OS Program Directory for information about the service which should be applied on z/OS Version 1 Release 4 to ensure that CICS TS installs correctly.

HFS and PDSE requirements

Some components of CICS TS are installed in PDSE data sets and HFS files. CICS TS for z/OS, Version 3.1 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. The components concerned are part of the CICS support for Java™ programs and for IIOP inbound to Java applications. For FMID JCI640D, which contains the HFS-dependent code, the OMVS address space must be active in full-function mode, otherwise the install of this function fails.

In the set of installation jobs, there are some new initial jobs to create the HFS files and the directories shown in Figure 2. You run these jobs before any of the normal DFHINSTn jobs. Note that the user ID running these jobs requires superuser authority.

Start of changeFigure 2. The HFS directory structure for CICS java and IIOP files
 The figure shows a hierarchy with a top level name of "/pathprefix". It has four subordinate branches. At the second level, these four branches are identified as "/usr1","/usr2", "/usr3", and "/usrn" The first of these "/usr1", is the only branch which shows more detail. It has one subordinate branch with "/lpp" as the detail at the third level. Again, only one branch leads to "/cicsts" at the forth level. This has four branches: "/cicsts13",  "/cicsts22", "/cicsts23", "/cicsts31", and "/cicstsnn". Each of these has two subordinate branches, they are not named.
End of change
Notes:
  1. If you normally maintain additional SMP/E target zone libraries for the purpose of applying service, you can also create additional directories at the /cicsts31 level to create the HFS equivalent. See the DFHIHFSA job for more information.
  2. Start of changeThe pathprefix in Figure 2 is optional.End of change
[[ Contents Previous Page | Next Page Index ]]