crastart*.conf, the CRASTART server startup
RSE starts the
CRASTART load module, which uses the definitions in
crastart*.conf to create a valid environment to execute batch TSO and ISPF
commands. Developer for z/OS® uses this environment to run the CARMA server,
crastart*.conf is located in
/etc/zexpl/, unless you specified
a different location when you customized and submitted job
For more details, see Customization setup. You can edit the file with the TSO
crastart*.confconfiguration files. Each of these sample files is preconfigured for a specific customization scenario:
crastart.endevor.confis configured for CRASTART startup with CA Endevor® SCM RAM.
crastart.confis configured for CRASTART startup with sample RAMs.
crastart*.conffile is similar in concept to a JCL job stream, but is more restrictive.
- The following samples show valid line formats:
Note: The BPXWDYN command is documented in Using REXX and z/OS UNIX System Services (SA22-7806) and allows complex allocation constructs.
ddname=dsn1,dsn2,dsn3 * comment
ddname=SYSOUT(c) * comment
ddname=DUMMY * comment
-COMMAND=<any bpxwdyn command> * comment
PROGRAM = progname parms * comment
- All input is changed to uppercase.
- Line continuations are not supported.
- There is no limitation on line length.
- One or more blank spaces are allowed around the equal sign (=).
- DD allocations must precede the related
- DD names allocated here are freed at the end of program execution. They do not accumulate.
- DD names allocated by the called programs are not freed.
- Multiple data sets can be concatenated to a DD name. The data set names must be separated by a comma (,), and the concatenation is searched in the listed order.
- All data set allocations are done with DISP=SHR, except for allocations done using
- Inline data is not supported. All data must be in cataloged files.
- Variables can be used only on the right side of the equal sign (=).
- The following variables are supported:
Variable Description &CRAUSER. Client user ID &CRADATE. Current® date in
Dyyyydddformat (7 char Julian)
&CRATIME. Current time in
Thhmmssformat (hour min sec)
&CRAPRM1. Port number &CRAPRM8. Site-specific value set by the user exit referenced by the
system.exitdirective in CRASRV.properties.
System symbol Any
-<ddname> A hyphen (-) followed by a previously defined DD name acts like a
*.ddnamebackward reference in JCL. The original DD must be allocated using the
–COMMANDstatement.Note: There is no variable for the TSO prefix because TSO is not active when the configuration file is interpreted. If you have a need for the TSO prefix or other variable that is not available, see (Optional) Custom allocation exec.
Figure 1 shows a basic
crastart*.conf skeleton that includes ISPF services.
- Due to page width limitations, some lines in the sample wrapped onto the next line. All lines that start with an indentation should be added to the end of the previous line.
- If you alter the PROGRAM line, ensure that there is at least one blank before the closing round bracket (“)”) of the PARM() statement to simplify processing of the string.
- You can add your own DD statements and data set concatenations to customize the CARMA TSO environment, thus mimicking a TSO logon procedure.
- The DD name
STEPLIBin JCL. Its DD name must match the value specified for
CRASRV.properties, which is described in CRASRV.properties, the RSE interface to CARMA.
- Regular APF rules apply for
TASKLIBallocations. Libraries lose their APF authorization when a non-APF authorized library is part of the concatenation.
- System abend 522 for module
CRASERVoccurs if the
JWTparameter in the
SMFPRMxxparmlib member is set to a value lower than the
CRASRV.properties. The system abend does not impact CARMA operations because the server is restarted automatically if needed.
- Details of the CARMA server startup are shown in
rsecomm.logwhen the server ends. For more information on setting the detail level of
rsecomm.log, see the IBM® Explorer for z/OS Host Configuration Guide (SC27-8437).