Archival › Exceptional Condition Checking (System and User-Specified Conditions) › User-Specified Conditions

User-Specified Conditions

Control statements are input to the archival started task using the SARXCTAB DD statement. For each statement, the percent sign is coded in column 1 and the ID immediately follows. One or more blanks follows the ID and separate it from the parameters. One or more blanks, commas, or both separate individual parameters. A statement that exceeds 71 characters is continued on additional statements. When continuing a statement, interrupt the statement only between complete parameters. The control statements have the following general structure:

Syntax:

%ID 'string' COL(bbbbb:eeeee) LINE(bbbbbb:eeeeee) 
             XCODE(xxxxxx) STOP EXC(job1,job2,...)

Where

%

Specifies the user-specified condition.

• For each statement, the % sign is coded in column 1 and the ID immediately follows.

ID

Specifies the job name of the SYSOUT job containing the user- defined string.

You can specify a generic job name by appending an asterisk to the generic name. For example, a job name of PROD* specifies that the statement applies to any job having the first four characters of its name being PROD. A statement beginning with %* includes all jobs.

'string'

Specifies the string of alphanumeric data to be found in the SYSOUT that signifies the exceptional condition.

• Enclose the string in single quotes.

COL(UMN)

Specifies the column number (bbbbb) or range (bbbbb:eeeee) where the string begins in the SYSOUT record.

• The default is COL(1) where the string begins in column 1. COLUMN includes the assumed carriage control in the column position. Specification of this field is not sensitive to the CCONDISP initialization parameter, which controls the viewing of carriage control characters in online logical viewing. COLUMN can be abbreviated as COL.

LINE

Specifies the beginning line number (bbbbbb) or range of lines (bbbbbb:eeeeee) to include in the search for the string.

The default is LINE(1:999999) that specifies that the entire SYSOUT group is searched. LINE does not include the assumed carriage control and it operates on the printed line, not the actual line.

XCODE

Specifies the 1 to 6 character exception code to be stored in the GCRXCODE field when the string is matched.

The EXCLUDE statement overrides XCODE. The default is CODE() to blank out the XCODE().

STOP

Specifies to the archiving task to freeze the XCODE for the SYSOUT group after a string match.

Exceptional conditions are bypassed for the remainder of the group except for updates to GCRXCODE by a customized SARSTCUX or SARXCTUX exit. This parameter is optional.

EXCLUDE()

Specifies to exclude specific jobs when a generic name (with wildcard, *) is present in the ID field.

Repeat this parameter on additional statements if required. EXCLUDE overrides the XCODE statement, if it is specified. EXCLUDE() can be abbreviated EXC(). The parentheses are required.

The following example describes where exceptional condition checking is required:

• System abends 122 and 222 are not considered exceptions
• For job JOB1, condition codes lower than 8 are ignored
• For job names starting with PAY, except for PAY11 and PAY22, store CANCEL as the XCODE for system message IEF251I and bypass any other exceptions

The control statements are coded as follows:

/DEFAULT NOSYS122 NOSYS222
/JOB1 CC>7
%PAY* 'IEF251I' COL(1) XCODE(CANCEL) STOP
       EXC(PAY11 PAY22)