(Optional) Custom allocation exec
All CARMA server startup methods have limitations regarding data set allocation. For example, TSO prefix substitution is not available in JCL or CRASTART.
However, by creating an exec that is called after TSO or ISPF starts, and before CARMA is started, you can use the whole range of variables and services available in TSO or ISPF to do the required allocations.
Developer for z/OS® uses
an allocation exec in each of the pre-configured setups described
earlier in this chapter.
the allocation exec for CA Endevor® SCM RAM and
the allocation exec for custom RAMs, The exec allocates cataloged
temporary data sets that have the user’s TSO prefix as high-level
qualifier. The allocation exec is also responsible for calling the
optional user exit.
Customization instructions are documented within the exec. Changing the allocation exec is supported, but not advised, as customizations must be redone when PTF service updates the exec. If possible, use the CARMA user exit instead, which is described in (Optional) CARMA user exit.
- When updating an allocation exec, ensure you do not destroy allocations done earlier in the CARMA startup process by CRASTART or your startup JCL.
- Output generated by the allocation exec is shown in DD SYSTSPRT of the CARMA server.
The following samples show how to start an allocation exec that requires only TSO.
SYSPROC = my.exec.library PROGRAM = IKJEFT01 %myexec ISPSTART PGM(CRASERV) PARM(&CRAPRM1. &CRAPRM2. )
//SYSPROC DD DISP=SHR,DSN=my.exec.library //SYSTSIN DD * %myexec ISPSTART PGM(CRASERV) PARM(&CRAPRM1. &CRAPRM2. ) //*