Control-M/JCL Verify is capable of validating a given JCL job before it is submitted.
Control-M/JCL Verify tests the JCL syntax to verify that the JCL statements in the job are valid. After the job passes this basic test, additional tests can be performed.
This step allows the user to specify the default settings that determine which additional tests are performed on the JCL jobs. The parameters, described in the table below, are located in the CTJPARM member.
Table 142 CTJPARM parameters specified in Minor Step 1 - Control-M/JCL Verify Management
Parameter |
Description |
---|---|
AROUTE |
Enable auto routing. Valid values are:
|
CMNTPOS |
Where comment lines are to be positioned in JCLs that are enforced or reformatted:
|
CNDALC |
Conditional allocation considerations. Mandatory. Valid values are:
|
CTMVARS |
Resolves Control-M AutoEdit variables in the job. Valid values are:
|
CTMCJCLI |
Determines whether to handle Control-M conditional JCL statements. Control-M conditional JCL statements are conditionally submitted by Control-M based on the resolution of %%IF, %%ELSE, and %%GOTO statements. Valid values are:
|
DB2PLAN |
Control-M/JCL Verify DB2 plan name. Name of the plan used by Control-M/JCL Verify to verify the status of the user's plans. The name specified here must match the name on the BIND and GRANT EXECUTE commands in the CTJBIND job. Default value - CTJDB2 |
DB2SYS |
Default DB2 subsystem ID. The value specified is used when the DSN command does not include the SYSTEM parameter, and you do not want Control-M/JCL Verify to use the default DB2 subsystem ID specified in the DSNDECP module. Default value - None |
DSNACCSS |
Verifies that the owner of the job has access privileges to the datasets used in the job. Valid values are:
The required access privilege (for example, read and update) is verified according to the DISP parameter coded in the DD statement. If the user is not specified one of the following users are verified:
The verification is performed by the security products supported by IOA (for example, RACF, CA-Top Secret, and CA-ACF2). Note: If the JCL verification is performed while editing a job member (during the edit JCL function), the access privileges of the Control-M job owner is verified. |
DSNEXIST |
Verifies the existence of the datasets referred to in the job. Valid values are:
|
EXPREOJC |
Verify that no EOJ card (line begins with: //) appears anywhere in the external procedures used by the job, with the exception of the last card. Valid values:
Note: Setting this parameter to Y might impact the performance because the verification process will be running longer. |
J2GUSEJ |
Use JES node name as the GATE node name if not explicitly resolved by the CTJJ2G member. Valid values are:
|
JESTTMNT |
Verifies that JES2 and JES3 statements can be used in the job. Valid values are:
|
MSGID |
Display Message ID. Valid values are:
|
MSGLEVEL |
Specifies the minimum severity of messages to be issued. Messages with lower severity than specified are not printed and do not affect the final return code (RC). Valid values are:
|
PGMCHECK |
Verifies that the PGM load modules used by the job exist and can be found in the conventional search order (as follows: steplib, joblib, linklist…). Valid values are:
|
RFBRKEY |
Split positional sub-parameters of JCL keywords. Mandatory. Valid values are:
Determines whether positional sub-parameters of JCL keywords are continued on an additional line in the reformat process, when the COLS range defined is exceeded. This parameter affects keywords such as DISP and SPACE, but does not have an impact on keywords that are not sub-parameters, such as DCB. |
RMTUSER |
Remote verification user ID. Defines the user ID that will be used when a JCL verification request is received from a remote node (i.e. a verification request from a Control-M JCL Verify monitor running on an LPAR other than the local one) and the user ID that issued the verification request on the remote note is undefined in the local security system. RMTUSER must be a valid user ID and have maximum of 8 characters. If omitted, the remote verification request will fail if the requester user ID from the remote node is undefined in the local security system. Optional. |
RULETRAC |
Enables Rule Trace. Issues a message with the rule name, rule member, and environment before executing a rule.
|
SITESTDR |
Verifies that the site standard rules will be used in the JCL verification. Valid values are:
|
STMAXCPU |
The maximum CPU time, in seconds, that can be used by a session to process one JCL statement. Valid values: 1–20 Default: 10 seconds |
SUMMFRMT |
Display format for the message summary section. Valid values are:
|
SUPDB2 |
Controls activation of DB2 support. Valid values are:
|
SUPUTIL |
Verifies utilities, such as IEBGENER, IEBCOPY, and SORT. Valid values are:
|
XCF |
Use XCF for inter-Plex communication. Valid values are:
|
XCFGROUP |
CTJ monitors XCF communication group. Default value is: @CTJMON@ |
Parent Topic |