Skip to content
CA Datacom/AD - 15.0
Documentation powered by DocOps

Customization and Environment Steps

Last update December 1, 2017

Perform the jobs in this section in before performing the steps in the new installation section (see New Installation Phase).

AXCUSNEW creates one of the libraries needed for the APF Authorized process.

The following is a list of the steps that are explained on the following pages:

Step Description Purpose
1 Retrieve AXCUS00 from CAAXSAMP perform changes as directed, and submit the JCL. Creates the INSTJCL PDSE and CUSTOM data sets and copies required members to modify.
2 Retrieve AXCUSNEW from INSTJCL, perform changes as directed, and submit the JCL. Assembles, and links all MUF.
3 Retrieve AXAFPADD from INSTJCL. Perform changes as directed and submit the JCL. APF authorizes the required data sets.
4 Retrieve AXRIM01 from INSTJCL, perform changes as directed, and submit the JCL. Installs the PC Calls required for the product.

The following steps are described in this section:

Step 1. Copy the JCL from Target to INSTJCL Library

This step creates the INSTJCL library and copies the new installation JCL from the target library to the INSTJCL library.

Note: If you plan to use the $DCAXEDT macro for editing the JCL members, do so before beginning the next step.
  1. Retrieve member AXCUS00 from your CAAXSAMP library.
  2. Make the required global changes (see the instruction block) but do not save this member in the CAAXSAMP library.
  3. Submit the JCL to complete this step.
  4. Review the output for successful completion.
  5. Expected condition code is 00.

Step 2. Prepare Product Custom Assemblies

This step prepares the CA DatacomĀ® customized assemblies.

  1. Retrieve member AXCUSNEW from your INSTJCL library.
  2. Make the required global changes (see the instruction block).
  3. Submit the JCL to complete this step.
  4. Review the output for successful completion.
  5. Expected condition code is less than or equal to 01 (see the following note).
  6. Review, edit, execute, and complete this step before continuing.

    Note: The only reason known to cause the Condition Code (CC) 0001 is when the CXX name is 8 bytes in length. The CXX name and the MUF name are used for this process by the same 9CXX_NAME symbolic name. The second to last step in this JOB is the step that generates a CC 1 because the name is 8 bytes in length. If CC 0000 is desired from this process, follow best practices for the CXX name. See CA Datacom/AD Environment.

Step 3. APF Authorize the Libraries

This job uses CA SYSVIEW. If you do not have this product, use any tool you have to add the CUSLIB and CAAXLOAD to the APF List.

Note: Run this step before attempting any of the new installation jobs.
  1. Retrieve member AXAPFADD from your INSTJCL library.
  2. Make the required global changes (see the instruction block).
  3. Submit the JCL to complete this step.
  4. Review the output for successful completion.
  5. Expected condition code is 00.
  6. Review, edit, execute, and complete this step before continuing.

Step 4. Load DB PC Calls Using CAIRIM

This step loads the CA DatacomĀ®/DB PC Calls using CAIRIM.

Note: Run this step before attempting any of the new installation jobs.
  1. Retrieve member AXRIM01 from your INSTJCL library.
  2. Make the required global changes (see the instruction block).
  3. Submit the JCL to complete this step.
  4. Review the output for successful completion.
  5. Expected condition code is 00.
  6. Review, edit, execute, and complete this step before continuing.

For a list of the MUF startup options that can apply to your installation, and for an updated list of DBSIDPR macro parameters, see the CA Datacom/DB Database and System Administration page.

Important! Install the PC Calls on every machine that might run the MUF region, a DBUTLTY job, or make a database request through the Cross-System Coupling Facility (XCF).
Was this helpful?

Please log in to post comments.