Installing Your Product from Pax-Enhanced ESD › Copy Installation Files to z/OS Data Sets

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.

Follow these steps:

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 the product-specific details that you require to complete the installation procedure.

   You have identified the 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:
   • Use ISPF EDIT. Specify the full path name of the UNZIPJCL file.
   • Use TSO ISHELL. Navigate to the UNZIPJCL file and use the E line command to edit the file.

   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, typically /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 that the installation process uses. We suggest that you use a unique HLQ for each expanded pax file to identify uniquely the package. Do not use the same value for yourHLQ as you 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 completes 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 that 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.

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

How to Install Products Using Native SMP/E JCL

The following steps describe the process to install products using native SMP/E JCL:

1. Allocate product data sets and SMP/E data sets.
2. Create SMP/E CSI.
3. Receive base functions.
4. Apply base functions.
5. Accept base functions.

Configure the product according to your site requirements

Prepare the SMP/E Environment for Pax Installation

The members in this procedure prepare the data sets, initialize the zones, and create the DDDEFs for Dispatch.

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

To prepare the SMP/E environment for your product

1. Customize the macro ADSSEDIT with your site-specific information and then copy the macro to your SYSPROC location. Replace the rightmost parameters for each ISREDIT CHANGE macro command. Each time you edit an installation member, type ADSSEDIT on the TSO command line, and press Enter to replace the defaults with your specifications.

   The macro is ready to customize the SAMPJCL members.

   Note: Set the DASD HLQ to the same value specified for the unzip to DASD ESD JCL.

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

2. Open the SAMPJCL member ADS1ALL in an edit session and execute the ADSSEDIT macro from the command line.

   Note: If you are upgrading into an existing CSI you must comment out existing data sets from the ADS1ALL member prior to submission.

   ADS1ALL is customized.

3. Submit ADS1ALL.

   This job produces the following results:

   • The target and distribution data sets for CA Dispatch are created.
   • Unique SMPLTS, SMPMTS, SMPSCDS, and SMPSTS data sets for this target zone are created.
4. Open the SAMPJCL member ADS2CSI in an edit session and execute the ADSSEDIT macro from the command line.

   Note: If you are upgrading into an existing CSI, prior to submission, do the following in ADS2CS1:

   • Comment out existing SMP data sets and the CSI allocate step
   • Change the UCLIN DDDEF ADD statements to REP statements for the allocated data sets . 

   For r11.0 upgrades into an existing CSI do the following:

   • Manually add the r11.0 Target and Distribution library DDDEFs to the ADS2CSI JCL and change CAIT0 to CAITGT and CAID0 to CAIDLIB. 
   • Delete SMPLOG from the CSI.

     You can manually remove this from your CSI or you can add the following to the ADS2CSI job in the target and distribution library DDDEFs

     DEL DDDEF(SMPLOG).  
     

     above the REP DDDEF(SMPLOG) statements.

     ADS2CSI is customized.

5. Submit ADS2CSI.

   This job produces the following results:

   • The CSI data set is defined.
   • The SMPPTS and SMPLOG data sets are allocated.
   • The global, target, and distribution zones are initialized.
   • The DDDEF entries for your product are created.
   • The DDDEFs for the required SMP/E data sets are created.