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

Previous Topic: CA LMP

Next Topic: Customize CA Datacom/AD for CAIENF

CA Datacom/AD Multi-User Deployment

After CA Datacom/AD has been successfully installed on one LPAR, you can establish fully operational CA Datacom/AD environments on any number of additional LPAR images.

If you used CA MSM to install Datacom/AD, you may be able to deploy Datacom/AD using CA MSM or you can 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 has eight steps with one JCL member associated with each step. Each JCL member contains a description of its function as well as specific instructions on the changes to be made prior to submitting it for execution.

The source LPAR is the LPAR where the initial CA Datacom/AD new installation was performed. The target LPAR is the LPAR where an additional CA Datacom/AD multi-user environment is to be established.

Each MUF on each LPAR should 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 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 new deployment JCL library containing all the needed members.

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. You should 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 Multi-User Facility (MUF) on a target LPAR

  1. Edit member DEPLOY in CAW0JCL. Change the JOB card to match your installation standards. Modify the SYSUT2 card in the IEBUPDTE step, changing the DSN from DEPLOY.JCL to a name that matches the SRC.DATACOM high level qualifier. The low order qualifier should be 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.
  2. Copy member AXDEPIPJ from the deployment JCL library just created into another library to preserve your changes. Modify each of the parameters after the SYSIN card except the last, $/<./< . l Change the value found within the angle brackets (<<) to match the value you specified in the deployment work sheet. 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. Use AXDEP01 to backup all required CA Datacom/AD data sets from the Source LPAR.
  4. Use AXDEP02 to restore all required CA Datacom/AD data sets to the target LPAR. The data set names used on the target LPAR can be the same or different from those on the source LPAR.
  5. Use AXDEP03 to add the PROCS used by CA Datacom/AD customized to meet target LPAR needs.

    This step creates the DBDATIN1 MUF startup option SYSIN member. The DBDATIN1 member has an entry called MUF that contains a MUFNAME parameter. The value used for MUFNAME should be different from any currently deployed or yet to be deployed MUF.

  6. Use AXDEP04 to assemble the DBSYSID macro and link edit the DBSIDPR module to be installed by CAIRIM on the target LPAR. The DBSYSID macro contains a MUF_TARGET_LIST parameter. The value used must be the same as the value used for MUFNAME in step 5.

    APF authorize the following target system data sets before running this job:

  7. Use AXDEP05 to initialize and load the CA Datacom/AD CXX data set for use on the target LPAR. The initialization process contains a MUFNAME parameter. The value used must be the same as the value used in steps 5 and 6.
  8. Use AXDEP06 to execute a PROC to start the CA Datacom/AD MUF on the target LPAR.
  9. Use AXDEP07 to change the internal data set references to the target LPAR names. These internal data set references are contained in the CXX data sets that were initialized and loaded in step 7.
  10. Use AXDEP08 to execute a PROC to stop the CA Datacom/AD MUF on the target LPAR.