Setting up the CICSPlex SM environment on system A

Perform the following steps to prepare the MVS™ environment on system A for CICSPlex® SM:

  1. Run EYUISTRT on system A to tailor the skeleton jobs for the Starter Set (and thereby for the IVPs). EYUISTRT runs the EYUINST EXEC to tailor the Starter Set members. For more information about EYUISTRT, see Using the EYUINST EXEC to tailor skeleton jobs. Table 47 identifies those EYUINST EXEC parameters that are applicable to the Starter Set.
    Table 47. EYUINST EXEC parameters required for the Starter Set
    Parameter CMAS MAS Default
    CINDEXnnn Yes Yes None
    CMASNAME Yes   None
    CRELEASE Yes Yes None
    DSINFO Yes   index dsvlsr dsunit
    ENVIRONMENT Yes Yes None
    INDEX Yes Yes CICSTS31.CPSM
    JOB Yes Yes //XXXXXXXX JOB
    LIB Yes Yes CICSTS31.CPSM.XEYUINST
    PREFIX Yes Yes EYU
    SCEESAMP Yes   SYS1.SCEESAMP
    SCOPE Yes Yes STARTER
    Note:
    The SCOPE value should be set to STARTER.
    SELECT Yes   None
    TEMPLIB Yes Yes CICSTS31.CPSM.SEYUJCL
    Note:
    For more information about TEMPLIB, see EYUINST EXEC parameters.
  2. Add VTAM® definitions for EYUCAS1A, EYUCMS1A, and EYUMAS1A to the VTAM table on system A. An example of the VTAM definitions for these three CICSPlex SM components is provided in sample EYUDVTIA.

    You need not add the VTAM definitions now to system B if you plan to not run IVP2. (Remember that IVP2 should be run when you will have CMAS-to-CMAS communication links.)

    EYUDVTIA is a subset of the VTAM definitions required on system A for the complete Starter Set. It holds the basic definitions required to run IVP1.

    Note:
    The sample VTAM definitions use MODETAB(EYUMDTAB). The source of this is in CICSTS31.CPSM.SEYUDEF, member EYUMDTAB. If you use the starter set VTAM definitions, you must assemble this table and put it into the VTAMLST library.

    If you use Network Control Programs (NCP), 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.

  3. Run the JCL EYUIBBIA, which defines the BBIPARM data set for CAS EYUCAS1A.
  4. Run the JCL EYUICMSA, which defines all data sets required by CMAS EYUCMS1A.
  5. Run the JCL EYUICICA, which defines all data sets required by MAS EYUMAS1A.
  6. Run the JCL EYUIDRPA, which defines the CICSPlex SM data repository on system A.
    Note:
    This data repository can be used with the Starter Set on system A: it does not need to be recreated after the IVPs have been run.)
  7. Run the JCL EYUICSDA, which defines, initializes, and loads the CSD to be used by both EYUCMS1A and EYUMAS1A.
  8. Make any necessary site-specific changes to the CSD created in step 7. For example, you might need to add TYPETERMs, TERMINALs or AUTOINSTALL MODELs.
  9. Assemble the following sample CICS® tables into a load library:
    Notes:
    1. Ensure that you have a model installed for the system log stream. The default naming convention is userid.applid.DFHLOG and userid.applid.DFHSHUNT for a system log stream, and userid.applid.DFHJnn (where nn is 01 through 99) for a user journal. See Defining the logger environment for CICS journaling and the CICS System Definition Guide for more information about creating log streams.
    2. TDQ definitions are added to the CSD when the CSD is created or upgraded.
    3. For details on assembling CICS control tables, see the CICS/ESA System Definition Guide.
  10. Update ISPF on system A to reflect the addition of CICSPlex SM. You can find an example of the required changes in EYU@ISPF and EYU@PRIM. Note that any changes you make to ISPF are generally applicable on system A and are not confined to IVP1 only. Therefore, you should try to make a permanent change at this stage so that you don’t have to repeat this step later. For more information, see Preparing user access to CICSPlex SM.
[[ Contents Previous Page | Next Page Index ]]