Requirements and checklist

You need the assistance of a security administrator and a TCP/IP administrator to complete this customization task, which requires the following resources or special customization tasks:

• (Optional) TCP/IP port range for internal communication
• (Optional) Security rule to allow developers update capability to CARMA VSAM files
• (Optional) Security rule to allow users to submit CRA* jobs
• (Optional) LPA update

To start using CARMA at your site, do the following tasks. Unless otherwise indicated, all tasks are mandatory.

1. Choose a method to start CARMA and choose which RAMs should be activated. Several combinations of RAMs and server startup methods are available as a preconfigured setup. For details, see Select the server startup method and active RAM.
2. Create CARMA VSAM data sets. For details, see CARMA VSAM data sets and CARMA Repository Access Managers (RAMs).
3. Initial customization of the RSE configuration files to interface with CARMA. The complete customization is dependent on the method chosen to start CARMA. For details, see CRASRV.properties, the RSE interface to CARMA.
4. Depending on the chosen CARMA startup method and the chosen RAMs, do the required customization of the related configuration files. For details see:
   • crastart*.conf, the CRASTART server startup
   • CRASUB*, the batch submit server startup
5. Optionally, customize the CA Endevor® SCM-specific configuration members. For details see CRACFG, CRASCL, CRASHOW and CRATMAP, the CA Endevor® SCM RAM configuration files and CA Endevor® SCM RAM batch actions.
6. Optionally, update the data set allocation exec. For details, see CRANDVRA, the CA Endevor® SCM RAM initial allocation exec, CRAALLOC, the custom RAM allocation exec, and (Optional) Custom allocation exec.
7. Optionally, create a startup user exit. For details, see (Optional) CARMA user exit.
8. Optionally, create CRAXJCL as replacement for IRXJCL. For details, see (Optional) IRXJCL versus CRAXJCL.