Installing from Pax Files Using the SAMPJCL Method › Copy Installation Files to z/OS Data Sets

Previous Topic: Sample Job to Execute the Pax Command (Unpackage.txt)

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

Copy Installation Files to z/OS Data Sets

Use this procedure to invoke the SMP/E GIMUNZIP utility to create MVS data sets from the files in the product-specific directory. Since CA Common Services software components are packaged using four pax files, it may be easier to perform this procedure for all the pax files you require now versus coming back to this procedure later. Each pax file contains its own UNZIPJCL file.

To copy the Pax-Enhanced ESD installation files to z/OS data sets

  1. Locate and read the product readme file or installation notes, if applicable, which resides in the product-specific directory that the pax command created. This file contains product-specific details you need to complete the installation procedure.

    You have identified product-specific installation details.

  2. Use ISPF EDIT or TSO ISHELL to edit the UNZIPJCL sample job. You can perform this step in one of the following ways:

    The job is edited.

  3. Change the SMPDIR DD PATH to the product-specific directory created by the pax command.

    Your view is of the product-specific directory.

  4. If ICSF is not active, perform the following steps:
    1. Change the SMPJHOME DD PATH to your Java runtime directory. This directory varies from system to system.
    2. Perform one of the following steps:
      • Change the SMPCPATH DD PATH to your SMP/E Java application classes directory, usually /usr/lpp/smp/classes/.
      • Change HASH=YES to HASH=NO on the GIMUNZIP parameter.

    One of the following occurs: ICSF is active or you are using Java.

  5. Change all occurrences of YourHLQ to the high-level qualifier (HLQ) for z/OS data sets used by the installation process. We suggest that you use the same HLQ for each expanded CA Common Services pax file. Using the same HLQ will allow you to perform one installation for all CA Common Services components. Each CA Common Services pax file has its own UNZIPJCL file. If you use a different HLQ for YourHLQ value in each UNZIPJCL file, at a minimum, you would have to perform multiple SMP/E receives to bring the unzipped files into your SMP/E installation environment. Do not use the same value for YourHLQ as you will use for the SMP/E RELFILEs.

    All occurrences of YourHLQ are set to your high-level qualifier for z/OS data sets.

  6. Submit the UNZIPJCL job.

    The UNZIPJCL job should complete with a zero return code. Messages GIM69158I and GIM48101I in the output and IKJ56228I in the JES log are acceptable.

    GIMUNZIP creates z/OS data sets with the high-level qualifier you specified in the UNZIPJCL job. You use these data sets to perform the product installation. The pax file and product-specific directory are no longer needed at this point.

    Note: For more information, see the IBM Reference Manual, SMP/E for z/OS Reference (SA22-7772).