CHECK command syntax

• In a CHECK command, CHECK PLUS considers any line beginning with an asterisk (*) in column 1 to be a comment and ignores it.
• When encountering two consecutive hyphens in a line (except within a delimited token), CHECK PLUS considers the remainder of the line to be a comment, which CHECK PLUS ignores.
• When you use a signed token, do not place a space between the sign and the value.
• You can split a token (such as a keyword, identifier, or constant) across a line. However, CHECK PLUS ignores anything in columns 73 through 80.

• A blank, or a delimiter if the token is delimited, indicates the end of the token. If an undelimited token ends in column 72, column 1 on the next line must be a blank.

  Important

  If you use applications that automate JCL submission and resolve symbolic variables within your JCL, the resulting control cards might not appear as they do in the JCL that you created. These applications might produce an invalid command statement.

• If you specify the same command option more than once, CHECK PLUS uses only the last specification of the option. For example, if you specify the following command, CHECK PLUS accepts CHECKTSLEVEL2 as the processing option:

  CHECK INDEX (ACK.ACKP0511)
        CHECKTSLEVEL1 CHECKTSLEVEL2
• In the syntax diagrams in this section, underlined options indicate default options.

Specifying object names

In addition to the token information in the syntax rules section, note the following limitations on specifying object names in your CHECK PLUS syntax:

• CHECK PLUS does not support Unicode table or index names.
• CHECK PLUS does not support delimited object names that do not have a character representation in EBCDIC. 

Alphabetical listing of CHECK PLUS options

The following table lists the CHECK PLUS command options in alphabetical order with hyperlinks to the topic that contain descriptions and usage information:

This section contains the following topics: