Previous Topic: CA LMPNext Topic: Customize CA Datacom/AD for CAIENF

Install CA Datacom/AD › CA Datacom/AD Multi-User Deployment

CA Datacom/AD Multi-User Deployment

After CA Datacom/AD r14 has been successfully installed on one LPAR and CAIENF r14.1 has been started on that LPAR, you can establish fully operational CA Datacom/AD environments on any number of LPAR images.

If you used CA CSM to install Datacom/AD r14, you might be able to deploy Datacom/AD using CA CSM. Instead, you can perform the steps that are outlined in this procedure to use the IBM ADRDSSU utility to backup all needed data sets from the initially installed LPAR and restore them on a different LPAR. This procedure creates data sets on the source system that have been customized to work on the target system. These new data sets are backed up and when later restored to the target system, you have a functional and customized Datacom/AD r14 on the target system and CAIENF can be started on that system.

This procedure has eight steps. The JCL members are associated with most of the steps. Each JCL member contains a description of its function and specific instructions on the changes you must make before submitting it for execution.

Definitions:

With Datacom/AD r14, each MUF on each LPAR must have a unique MUF name. The LPAR system name can be used in the MUF name to make it easier to identify the origin of CA Datacom/AD messages and reports that are generated within a SYSPLEX.

The JCL necessary to execute this deployment procedure is found in member DEPLOY in the CAW0JCL library. Running this job creates a deployment JCL library containing all the needed members.

Note: Steps 1 through 6 must be done on the source system, while steps 7 and 8 are done on the target system.

Important! After creating the deployment JCL library, member AXDEPIPJ contains an IPOUPDTE process that can be used to perform all necessary edits to the CA Datacom/AD Deployment members described below, and must be run to perform the needed customization. Copy this member to another library then customize and submit it from that library to keep from losing changes when the deployment JCL library is updated.

To establish a fully operational CA Datacom/AD r14 Multi-User Facility (MUF) on a target LPAR:

Follow these steps:

  1. Edit the member DEPLOY in CAW0JCL. Change the JOB card to match your installation standards. Modify the SYSUT2 statement in the IEBUPDTE step, changing the DSN from SRC.DATACOM.DEPLJCL to a name that matches the SRC.DATACOM high level qualifier. The low-order qualifier is DEPLJCL to avoid having to make significant changes to the rest of the jobs in the process. Modify the UNIT and VOL=SER to match your installation standards and submit the job. This same DSN will need to be defined in the next step on the @LIBCARD DD statement.
  2. Copy member AXDEPIPJ from the deployment JCL library that is created into another library to preserve your changes. Modify each of the parameters after the SYSIN statement except the last, $/<./<. Change the value found within the angle brackets (<<) to match the value as documented in the job comments. Submit this job.

    In this example, you would change the second occurrence of SRC.SMPE.DATACOM

    SRC.SMPE.DATACOM<SRC.SMPE.DATACOM<

    Important! Do not delete or update the last entry $/<./<.

  3. Submit job AXDEP01 on the Source system to assemble and link-edit custom modules to the target custom libraries.
  4. Submit job AXDEP02 on the Source system to allocate all the MUF deployable data sets and databases.

    Important! The Source system multiuser facility (MUF) must be inactive (down) when this job is run.

  5. Submit job AXDEP03 on the Source system to back up the CA Datacom/AD product datas ets.
  6. Make the backup file that job AXDEP03 creates and the DEPLJCL library available to the target system.
  7. Submit job AXDEP04 on the Target system to restore all required CA Datacom/AD data sets to the target LPAR.
  8. APF authorize the following target system data sets on the target system: