The Starter Set configuration

The Starter Set contains examples of configuration relationships and of BAS, WLM, RTA, and monitoring specifications and definitions. You can use these examples to model your own definitions.

Figure 22. The Starter Set configuration. The Starter Set provides a small but comprehensive set of CICSPlex SM components on which you can model your own CICSPlex SM environment.
A picture showing the Starter Set configuration across two MVS images. On system A, there are four MASs, a CMAS (EYUCMS1A) and a CAS (EYUCAS1A). On system B, there are four MASs, a CMAS (EYUCMS1B) and a CAS (EYUCAS1B). . All MASs on system A and one MAS on system B belong to CICSplex EYUPLX01. Three MASs on system B belong to CICSplex EYUPLX02. There are CAS-to-CAS links and CMAS-to-CMAS links

Figure Figure 22 shows the main components of the CICSPlex® SM Starter Set configuration, which consists of:

The Starter Set installation requirements

The Starter Set is supplied in two samples libraries that are installed automatically when CICSPlex SM itself is installed.

The two libraries, whose default names are CICSTS31.CPSM.SEYUJCL and CICSTS31.CPSM.SEYUDEF, are described in the remainder of this topic.

Starter Set library CICSTS31.CPSM.SEYUJCL

The samples library CICSTS31.CPSM.SEYUJCL contains sample JCL for creating and running the Starter Set CASs, CMASs, and MASs. It also includes JCL for creating the CMAS data repositories.

This JCL has been provided chiefly so that you don’t have to create it yourself before you can use the Starter Set. However, you might also find it useful to refer to when you are creating JCL for your own CICSPlex SM environment (for which you are recommended to use the skeleton JCL supplied with CICSPlex SM).

CICSTS31.CPSM.SEYUJCL also includes sample JCL for deleting the Starter Set components from an MVS image.

Starter Set library CICSTS31.CPSM.SEYUDEF

The samples library CICSTS31.CPSM.SEYUDEF contains an assortment of sample definitions required to establish not only the Starter Set itself, but also the environment in which it can be used. (The data required to set up the environment is mostly of a routine nature, and is supplied primarily so that you don’t have to define it yourself. However, as with the Starter Set JCL, you might find these samples to be a useful checklist or aid when you are making these changes in a real CICSPlex SM environment.)

Definitions in CICSTS31.CPSM.SEYUDEF include:

Configuring part of the Starter Set

Start of changeThe Starter Set configuration of seven CICS systems distributed across two MVS images was designed to demonstrate all of CICSPlex SM’s facilities. However, not having this exact environment doesn’t mean that you can’t use at least a part of the Starter Set. As an alternative to configuring the whole Starter Set in three MVS images, you can configure:

How to configure the Starter Set is described in the CICS Transaction Server for z/OS® Installation Guide.End of change

The Starter Set and the IVPs

Configuration of the Starter Set is not essential. However, part of the Starter Set constitutes the CICSPlex SM MVS/ESA installation verification procedures (IVPs): if you run an IVP on an MVS image (as you are recommended to do), you will, during the IVP, perform most of the configuration tasks required to make the Starter Set usable. The IVPs ensure that:

There are two IVPs, which are referred to as IVP1 and IVP2. IVP1 is run on the first (or only) MVS image on which CICSPlex SM is installed and uses the system A components of the Starter Set. IVP2 is run on the second and subsequent MVS images on which CICSPlex SM is installed. It uses both the system A and system B components of the Starter Set, and tests communication between CASs and CMASs. The IVPs are described in detail in the CICS Transaction Server for z/OS Installation Guide.

[[ Contents Previous Page | Next Page Index ]]