Use this procedure to invoke the SMP/E GIMUNZIP utility to create MVS data sets from the files in the product-specific directory.
- 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.
- 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.
- Change the SMPDIR DD PATH to the product-specific directory created by the pax command.
Your view is of the product-specific directory.
- If ICSF is not active, perform the following steps:
- Change the SMPJHOME DD PATH to your Java runtime directory. This directory varies from system to system.
- 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.
- 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.
- 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).