Unified Install Process › 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.

The file UNZIPJCL in the product directory contains a sample job to GIMUNZIP the installation package. You edit and submit the UNZIPJCL job to create z/OS data sets.

Follow these steps:

1. 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.
2. Edit the job card to include a valid job class, MSGCLASS, and accounting information, according to your site's standards.
3. Change all occurrences of "<instlib_hlq>" to the high-level qualifier (HLQ) for z/OS data sets that the installation process uses.

   All occurrences of "<instlib_hlq>" are set to your high-level qualifier for z/OS data sets.

4. Change the "<yourUSSpaxdirectory>" to the product-specific directory created by the pax command.

   All occurrences of "<yourUSSpaxdirectory>" are set to the product-specific directory created by the pax command.

5. Change "<yourUSSinstalldirectory>" to the USS directory path where the USS files for CA Compliance Manager, CA LDAP, and CA Datacom are copied. This must be an existing path. Specify the entire path except for the trailing "/".
6. To use the default SMS class for interim files, leave volume="*" as is. To use a specific volser, change volume="*" to volume="packname". The files being downloaded are an entire SMP/E environment. We recommend that you specify a volume for permanent retention of the SMP/E environment.
7. If ICSF is not active, perform the following steps:
   1. Change the "<yourjavahome>" to your Java runtime directory. This directory varies from system to system.
   2. Perform one of the following steps:
      • Change the "<yourclasspath>" to your 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.

8. Submit the UNZIPJCL job.
9. The UNZIPJCL job unloads all the target and DLIB libraries and associated CSI which contains the following products:
   • CA Compliance Manager
   • CA LDAP Server
   • CA DSI Server
   • CA Datacom/AD
   • CA Easytrieve

   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).

10. Update the CSI parameters and DDDEFs. The UPDCSI job in the SAMPJCL library created by the previous step updates the CSI parameters and DDDEFS to complete the SMP/E environment.
    • Change the JOB statement to conform to your site standards.
    • Change all occurrences of "<instlib_hlq>" to the same high level qualifier that was specified for “instlib_hlq” in the UNZIPJCL job.
    • Change "<yourUSSinstalldirectory>" to the USS directory path that was specified for "yourUSSinstalldirectory" in the UNZIPJCL job. Specify the entire path except for the trailing "/".
    • Change "<yourjavahome>" to the same path that was specified for "yourjavahome" in the UNZIPJCL job. Specify the entire path except for the trailing "/".
    • Change "<STORCLASS=STRCLS>" to specify valid SMS information or valid volume information for your system.
11. Run the UPDCSI job.

Import an SMP/E Environment to CA CSM (Optional)

Future maintenance for the CA Chorus for Security and Compliance Management can be applied using SMP/E or CA CSM. This procedure steps you through applying maintenance using CA CSM. You can use CA CSM to maintain products that were installed previously using SMP/E by placing the relevant SMP/E environments under CA CSM management. A wizard is available to guide you through the process.

Some zones of the migrated SMP/E environment can have missing or partially populated DDDEF entries. CA CSM requires DDDEFs to maintain previously installed products successfully. For those SMP/E environment zones, you obtain the missing DDDEFs from the original product SMP/E installation JCL during SMP/E environment migration. This JCL is the member that is used to install the SMP/E product using the receive or apply and accept functions.

Note: We recommend that you use your product installation JCL when migrating an SMP/E environment to ensure product SMP/E environment integrity.

Follow these steps:

1. From the SMP/E Environments tab, click the Migrate SMP/E Environment link in the Actions section.

   You are prompted to identify the SMP/E environment.

2. Define a meaningful name for the environment. Specify the data set name of the SMP/E environment you want to migrate, and click Next.

   The functions in the SMP/E environment are listed.

3. Review the information and select Next.

   A list of zones with DDDEF associations appears.

4. (Optional) Review and update the DDDEFs obtained from JCL for each zone individually:
   • Click Manage DDDEFs for the zone whose DDDEFs you want to review individually.

     A pop-up window displays a list of DDDEFs for the zone.

   • Review the list of DDDEFs and select (to add to a zone) or clear (to remove from a zone) the corresponding check boxes.

     Note: If some DDDEFs from the list cannot be added to the zone or they exist in the zone, the corresponding check boxes are disabled. You cannot select the DDDEFs from the list.

   • Click Close to save changes and return to the wizard.
5. Click Next.

   If any file systems mounted to the path specified in the DDDEFs are found, a list of the file systems is displayed.

6. Review the file systems.

   Zones of the migrated SMP/E environment are listed.

   Note: Only the existing zones and the zones to which you have access appear.

7. Click next

   Verify a prefix for each zone and click Next. Prefixes are only used as HLQ defaults during future base installations into the same SMP/E environment. If necessary, these defaults can be overridden during the base installation.

   A list of advanced settings appears.

8. Add SMP/E Environment to Working Set

   Adds the migrated SMP/E environment to your working set. A working set is a selected group of SMP/E environments which you want to work. Future displayed information is based on the working set. For example, maintenance information is shown. The information is not shown for environments outside the set.

9. Click Next.

   The summary page appears.

10. Review the information and click Migrate.

A dialog that shows the progress of the task opens. When the task completes, you can click Show Results on the Progress tab to close this dialog. The task output browser opens and you can view the action details. Click Close to close the task output browser.

Note: You can perform other work while a task is in progress. Click Hide to exit the dialog and view the task status later on the Tasks tab.

After the migration is successfully completed, information about the SMP/E environment and associated products is saved in the CA CSM database. The migrated environment appears on the tree in the SMP/E Environments section on the left side.