Previous Topic: How to Install Products Using Native SMP/E JCL

Next Topic: Run the Installation Jobs for a SAMPJCL Installation

Prepare the SMP/E Environment for SAMPJCL Installation

The members in this procedure prepare the SMP/E data sets, initialize the zones, and create the DDDEFs for CA Common Services for z/OS. External DDDEF data sets are required.

Prior to beginning this procedure, if you are installing Agent Technology, Event Management or the version of Tomcat shipped with CA Common Services, establishing a USS hierarchical file system is required as part of the product installation. If you are installing CA MSM Common Services, USS is a required feature of the product.

Since the CA Common Services software components are packaged using four pax files, it may be easier to install all the components at once versus repeating this procedure for each Common Services component or pax file.

The BASE pax file contains the SAMPJCL data set to install all the CA Common Services components. If you prefer performing multiple installations, make copies of the BASE SAMPJCL data set for each installation before you edit any of the members.

For information about the members, see the comments in the JCL.

All CA Common Services components must be installed into the same SMP/E CSI.

All the CA Common Services components found in the BASE pax file must be installed.

To prepare the SMP/E environment for your product

  1. Customize the ISPF Edit macro, AW0SEDIT found in the SAMPJCL data set unzipped from the BASE pax file with your site-specific information then copy it to your SYSPROC location.

    To customize member AW0SEDIT, replace the right-most parameters for each ISREDIT CHANGE macro command with your site specific information.

    Each time you edit an installation member, type AW0SEDIT on the TSO command line, and press Enter to replace the defaults with your specifications.

    The macro is ready to customize the SAMPJCL members.

    Important! All CA Common Services components must be installed into the same CSI and zones. If you decide to perform multiple installations for each CA Common Services component or pax file, the “change to” values specified for GLOBALHLQ and CAIT0HLQ must be the same for each installation.

    Note: Update the SREDIT Change command for DASDHLQ by replacing CAI to the same value you specified as yourHLQ in the UNZIPJCL file for the pax file. This value is used in the SMP/E receive processing.

    If you are installing CA Common Services components from multiple pax files and you specified a different value for yourHLQ in each pax file’s UNZIPJCL, you must perform the SMP/E receive for each yourHLQ you used.

    Update ISREDIT CHANGE ALL DASDHLQ CAI

    To ISREDIT CHANGE ALL DASDHLQ yourHLQ

    The following steps include instructions to execute the AW0SEDIT macro each time you open a new SAMPJCL member. To edit all SAMPJCL members simultaneously, read and follow the instructions in the AW0EDALL member

  2. Open the SAMPJCL member AW01ALL in an edit session and execute the AW0SEDIT macro from the command line.
  3. Submit AW01ALL.

    The job produces the following results:

  4. Complete the following sub-steps for each pax file that contains components you wish to install.

    xxx represents the following 3-character codes:

    CCS - LEGACY components

    NSM - MFNSM components

    1. Open the SAMPJCL member xxx1ALL in an edit session and execute the AW0SEDIT macro from the command line.
      xxx1ALL is customized.
      
    2. Submit xxx1ALL.

    These jobs produce the following results:

  5. If you are installing Agent Technology, Event Management or the version of Tomcat shipped with CA Common Services, complete the following sub-steps for each of these products you are installing:

    Note: All instances of ccc in this step represent the following three-character component codes based on the FMID.

    B6D - MFNSM - Agent Technology

    D5I - MFNSM - Event Management

    EG1 - OPTIONAL - Tomcat

    1. Open the SAMPJCL member ccc1ALLU in an edit session and execute the AW0SEDIT macro from the command line.

      ccc1ALLU is customized.

    2. Submit ccc1ALLU.

      This job allocates your zFS data sets.

    3. Open the SAMPJCL member ccc2MKD in an edit session and execute the AW0SEDIT macro from the command line.

      ccc2MKD is customized.

    4. Submit ccc2MKD.

      This job creates all directories and mounts the file system.

  6. All CA Common Services components must be installed into the same SMP/E CSI. This JCL creates the CSI for all CA Common Services components. Open the SAMPJCL member AW02CSI in an edit session and execute the AW0SEDIT macro from the command line.

    AW02CSI is customized.

  7. Submit AW02CSI.

    This job produces the following results:

  8. Complete the following sub-steps for each pax file that contains components you wish to install: xxx represents the following 3-character codes.
    1. Open the SAMPJCL member xxx2CSID in an edit session and execute the AW0SEDIT macro from the command line.

      xxx2CSID is customized.

    2. Submit xxx2CSID.

      These jobs produce the following results:

      • The DDDEF entries for Common Services component data sets are created.
  9. If you are installing Agent Technology, Event Management or the version of Tomcat shipped with CA Common Services, complete the following sub-steps for each of these products you are installing:
    1. Open the SAMPJCL member ccc3CSIU in an edit session and execute the AW0SEDIT macro from the command line.

      ccc3CSIU is customized.

      Note: All instances of ccc in this section indicate a three-character component code based on the FMID.

    2. Submit ccc3CSIU.

      This job customizes the CSI by adding the DDDEFs associated with the USS target paths.