Creating the Starter Set environment

To configure the Starter Set on any MVS™ image, you must have access on that MVS image to:

Selecting the Starter Set configuration

The complete Starter Set is installed across two MVS images and comprises two CICSplexes, EYUPLX01 and EYUPLX02. You can install the complete Starter Set, or you can install a specific subset of it. That is, you can install:

When you have identified those parts of the Starter Set you want to install, locate the appropriate tables of JCL and definitions in this chapter. For example, to define and start the system A components only, you will:

When you have identified the JCL and sample definitions you will be using, follow the procedure described in Defining the Starter Set environment.

Defining the Starter Set environment

This section describes the tasks you must perform to incorporate the Starter Set in your MVS environment.

Notes:
  1. If you have already run an IVP (as described in CICSPlex SM installation verification procedures) on the MVS image on which you are planning to configure the Starter Set, you will already have performed most of the steps described below. You do not need to repeat those steps, unless the Starter Set components created during the IVP have been deleted.
  2. The Starter Set MAS JCL and the CSD update job do not support languages other than assembler. If you require support for other languages, please make appropriate changes to DFHRPL (for the MAS JCL) and to DFHCSDUP.

Carry out the following steps as appropriate:

  1. Versions of CICS in CICS Transaction Server for OS/390® and CICS Transaction Server for z/OS® use MVS log streams for their system logs and require appropriate MVS and CICS definitions to be in place. If you already have CICS TS levels of CICS installed, and if you use the default naming convention of userid.applid.DFHLOG and userid.applid.DFHSHUNT for the system log streams, you can proceed to the next step without taking any further action. However, you might want to review the coupling facility space implications of creating new CICS system logs.

    If you do not use the default naming convention for your system logs, or you have never previously brought up a CICS Transaction Server level of CICS, you should seek assistance from your CICS and MVS system programmers to set up the logger definitions for the sets of system logs that you require. For a full description of how to create the required MVS and CICS definitions for MVS log streams, see Defining the logger environment for CICS journaling and the CICS System Definition Guide.

    Whichever naming convention you adopt, do not define the CICS system log as type DUMMY, as this would compromise data integrity on the CICSPlex® SM data repository.

  2. Run the EYUISTRT job to tailor the Starter Set JCL for your environment. EYUISTRT runs the EYUINST EXEC to tailor the Starter Set members. For more information about using EYUISTRT, see Using the EYUINST EXEC to tailor skeleton jobs. Table 35 identifies those EYUINST EXEC parameters that are applicable to the Starter Set.
    Table 35. EYUINST EXEC parameters required for the Starter Set
    Parameter CMAS MAS Default
    Start of changeBLKUEnd of change Start of changeYesEnd of change Start of changeYesEnd of change Start of change6144End of change
    CINDEXnnn Yes Yes None
    CMASNAME Yes   None
    CRELEASE Yes Yes 6.4.0
    DSINFO Yes Yes index dsvlsr dsunit
    ENVIRONMENT Yes Yes None
    INDEX Yes Yes CICSTS31.CPSM
    JOB Yes Yes //XXXXXXXX JOB
    LIB Yes Yes index.XEYUINST
    PREFIX Yes Yes EYU
    SCEESAMP Yes   SYS1.SCEESAMP
    SCOPE Yes Yes POST
    Note:
    The SCOPE value must be set to STARTER.
    SELECT Yes   None
    TEMPLIB Yes Yes index.SEYUJCL
    Note:
    For more information about TEMPLIB, see EYUINST EXEC parameters
    Start of changeWORKUNITEnd of change Start of changeYesEnd of change Start of changeYesEnd of change Start of changeSYSDAEnd of change
    Start of changeWORKVOLEnd of change Start of changeYesEnd of change Start of changeYesEnd of change Start of changeEnd of change
  3. Add VTAM® definitions for the CAS, CMAS, and MASs (as appropriate) to the VTAM table. For example, for the system A Starter Set components, the relevant VTAM definitions are in members EYUDVTMA, EYUDCDMA, and EYUDCDSA of CICSTS31.CPSM.SEYUDEF.
    Note:
    If you use Advanced Communications Function (ACF) Network Control Programs (NCPs), you may need to create a mode table, using the sample entry shown in EYUMDTAB, in order to control the VTAM RUSIZE (request unit size) parameter.
  4. Run the JCL EYUJBBIx to define the CAS data sets.
  5. Run the JCL EYUJCMSx to define the CMAS data sets.
  6. Run the JCL EYUJCICx to define the MAS data sets.
  7. Run the JCL EYUJDRPx to define the CMAS data repository.
  8. Run the JCL EYUJCSDx to define, initialize, and load the CSD.
  9. Make any necessary site-specific changes to the CSD. For example, you might need to add TYPETERMs, TERMINALs, or AUTOINSTALL MODELs.
  10. Assemble the sample CICS tables (EYUTxxxx) into a load library.
  11. Update ISPF to reflect the addition of CICSPlex SM. A sample of the changes required is in EYU@ISPF and EYU@PRIM in CICSTS31.CPSM.SEYUDEF.

Starting the Starter Set components

Before you can use the Starter Set, you must:

These steps must be performed on system A or system B (or both).

Start EYUCAS1A or EYUCAS1B

To start the CAS, you submit JCL EYUJCSx or EYUJCSSx (to start the CAS as a started task). For example, to start EYUCAS1B as a started task, you use JCL EYUJCSS2.

Start EYUCMS1A or EYUCMS1B

Check the SIT parameters in JCL EYUJCM1A or EYUJCM1B (as appropriate), in particular the SVC numbers and the default user, to ensure that they are suitable for your environment. To start the CMAS, submit JCL EYUJCM1x. For example, to start CMAS EYUCMS1B, you submit JCL EYUJCM1B.

Add definitions to the data repository

You define CICSplex EYUPLX01 or EYUPLX02, or both, via the CICSPlex SM user interface. Then you use the batched repository update facility to load the remaining Starter Set definitions.

Note:
If you have run an IVP on the target MVS image (system A or system B), and have not deleted the IVP components from that image, you must run step 4 and step 7 in the section Defining the Starter Set environment before continuing with steps 1 through 4 below.
  1. On system A, define CICSplex EYUPLX01, specifying EYUCMS1A as the maintenance point CMAS. Also on system A, identify EYUCMS1B as a secondary CMAS for EYUPLX01 if you are planning to define the system B components of the Starter Set. For more information about defining CICSplexes, see the CICSPlex System Manager Administration manual. (Alternatively, you can follow the instructions in Starting up and verifying CICSPlex SM components on system A.)
  2. If you are installing the system B components, define EYUPLX02 on system B; EYUCMS1B is the maintenance point CMAS.
  3. If you have defined both EYUCAS1A and EYUCAS1B, you must define a link from EYUCAS1A to EYUCAS1B, and from EYUCAS1B to EYUCAS1A. For information about defining CAS-to-CAS links, see the CICSPlex System Manager Administration manual. (Alternatively, you can follow the instructions in 3: Checking CAS-to-CAS connections.)
  4. To add the Starter Set CICSPlex SM definitions to the data repository on system A or system B (or both), you run the batched repository update facility. Definitions to be added to the data repository on system A are in member EYUDDRPA of CICSTS31.CPSM.SEYUDEF, and those to be added to the data repository on system B are in member EYUDDRPB of CICSTS31.CPSM.SEYUDEF. For information about the batched repository update facility, see the CICSPlex System Manager Administration manual . (Alternatively, see the instructions for using the batched repository update facility during the IVPs in CICSPlex SM installation verification procedures.)

Start the MASs

To start the MASs, submit the JCL EYUJMSnx. For example, to start MAS EYUMNS2B, submit the JCL EYUJMS2B. JCL for starting the MASs is identified in Table 29 and Table 30. The CICSPlex SM Starter Set is now ready to use.

If errors occur while defining or using the Starter Set

If errors occur while you are setting up the Starter Set or while you are using it, one or more error messages might be issued. Please refer to the the CICSPlex System Manager Messages and Codes manual for a detailed description of any CICSPlex SM error message.

[[ Contents Previous Page | Next Page Index ]]