Starting Your Product › How to Configure Without CA CSM › Tailor the Startup JCL

Tailor the Startup JCL

The SYS1.OPS.CCLXCNTL data set contains four JCL members that required to run the CA OPS/MVS started tasks:

• OPSMAIN (main CA OPS/MVS address space)
• OPSOSF (TSO server address spaces)

  For more information, see Regulating OSF Servers in the Technical Notes in the CA OPS/MVS Administration Guide.

• OPSECF (Enhanced Console Facility address spaces)
• OPSUSS (UNIX System Services server address space)

To tailor the startup JCL

1. Copy the OPSMAIN, OPSOSF, OPSECF, and OPSUSS members into your started task procedures library. (which must be SYS1.PROCLIB if you intend to start OPSMAIN under the master subsystem).

   These members can now be tailored as described in the following steps.

2. Change the OPSMAIN Member JCL as follows:
   • Change the LOADLIB parameter in the PROC statement to the name of the deployed runtime OPS.CCLXLOAD library. If you placed the CA OPS/MVS load library (OPS.CCLXLOAD) into the linklist or LPALST, remove the STEPLIB statement and the LOADLIB parameter from the PROC statement.
   • Change the SYSPROC data set name to the name of the deployed runtime OPS.CCLXCLS0 data set.
   • Change the SYSEXEC data set names to the name of the deployed runtime OPS.CCLXEXEC library, along with your hlq.USER.REXX library.

• If your installation does not support VIO data sets, change the UNIT=VIO in the SYSTSPRT DD statement to a valid unit name. Ensure that VIO OPSPARM has a defined, esoteric name such as SYSDA, or properly allocate your OPSTSO DD.
• If use of above the bar 64-bit storage is automatically restricted by your installation using SMFPRMxx parmlib members or the SMF exit IEFUSI, then you may have to add the parameter ‘MEMLIMIT=4G’ to the OPSMAIN EXEC JCL statement or insure that CA OPS/MVS is not subject to any MEMLIMIT restrictions.

Note: The CAHBEXCL DD statement prevents the CA Hyper Buf product from interfering with VSAM processing requests within the CA OPS/MVS address space.

1. Change the OPSOSF and OPSECF JCL as follows:
   • Change the DSN parameter in the STEPLIB statement to the name of the deployed runtime OPS.CCLXLOAD library. Remove the STEPLIB statement completely if you placed the CA OPS/MVS load library (OPS.CCLXLOAD) into the linklist or LPALST.
   • Change the SYSPROC data set name to the name of the deployed runtime OPS.CCLXCLS0 data set.
   • Change the SYSEXEC data set names to the name of the deployed runtime OPS.CCLXEXEC library, along with your hlq.USER.REXX library.

   The startup JCL members are tailored and ready to run the CA OPS/MVS started tasks.