Customizing Control-M/JCL Verify

Verifies that the owner of the job has access privileges to the datasets used in the job.

Valid values are:

• Y – Yes. Default.

• N – No.

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:

when a JCL job is verified - the user that invoked Control-M/JCL Verify

when a Control-M job definition is verified - the Control-M job owner

The verification is performed by the security products supported by IOA (for example, RACF, CA-Top Secret, and CA-ACF2).

Verifies the existence of the datasets referred to in the job.

Valid values are:

• Y – Yes. Default.

• N – No.

Verifies that JES2 and JES3 statements can be used in the job.

Valid values are:

• Y – Yes. Default.

• N – No.

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:

• Y – Yes. Default.

• N – No.

Verifies that site standard rules can be used for JCL verification.

Valid values are:

• Y – Yes. Default.

• N – No.

Verifies utilities, such as IEBGENER, IEBCOPY, and SORT.

Valid values are:

• Y – Yes. Default.

• N – No.

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.

Controls activation of DB2 support. Valid values are:

• Y - Yes.

• N - No. Default.

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

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

Resolves Control-M AutoEdit variables in the job.

Valid values are:

• Y – Yes. Default.

• N – No.

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:

• Y - Control-M Conditional JCL statements are processed normally. Default.

• N - Control-M Conditional JCL statements are ignored by Control-M JCL Verify and are not processed.

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:

• I – Information messages (lowest severity) and above (all messages). Default.

• W – Warning messages and above.

• E – Error messages (highest severity) only.

Enables Rule Trace. Issues a message with the rule name, rule member, and environment before executing a rule.

• Y – Issue the Rule Trace message.

• N – Do not issue the Rule Trace message. Default.

Defines a prefix for a flat file that contains saved reports. Up to 19 characters.

Besides this prefix, the file name also includes the date and time when saved and the name of the verifying JCL.

Defines the VOLUME where reports are saved.

To use SMS to manage the saving location, leave this parameter blank.

If you specify a value for JREPVOL, you must also specify a value for JREPUNIT.

Defines the UNIT where reports are saved.

To use SMS to manage the saving location, leave this parameter blank.

Display format for the message summary section. Valid values are:

• T - Table format. Default.

  • Consisting of 2 or 3 columns:

    - Label

    - Message ID

    (this column is displayed/hidden depending on parameter MSGID below)

    - Message text

• M - Text message format.

         Consisting of 2 lines per message

        - First line - type of message and label

        - Second line - message text and Message ID (optionally, depending on parameter MSGID below)

• N - The message summary section is not displayed.

Display Message ID. Valid values are:

• Y - Yes. Show JCL verify messages and summary with message ID. Default.

• N - No. Show JCL verify messages and summary without message ID.

Use XCF for inter-Plex communication. Valid values are:

• Y - Yes. Default.

• N - No.

CTJ monitors XCF communication group.

Default value is: @CTJMON@

Enable Auto Routing. Valid values are:

• Y - Yes.

• N - No. Default.

Use JES node name as the GATE node name if not explicitly resolved by the CTJJ2G member. Valid values are:

• Y - Yes. - If the JES node name was not explicitly resolved by member CTJJ2G and a GATE with an identical name exists, use it for routing. If no such matching gate exists, perform the verification locally.

• N - No. - If the JES node name was not explicitly resolved by member CTJJ2G, perform the verification locally (that is, do not perform routing even if a GATE that matches the JES node name exists). Default.

Conditional allocation considerations. Mandatory. Valid values are:

• Y - Yes, consider conditional allocation.

• N - No, do not consider conditional allocation. Default.

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:

• N – No. Default.

• Y – Yes.

Split positional sub-parameters of JCL keywords. Mandatory. Valid values are:

• Y - Yes. Default.

• N - No.

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.

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