Code Processing

SA z/OS displays the panel shown in Figure 1 if you enter the action code Cod (K) in the Cmd column on the Message Processing panel.

If you enter Cod (K) against message CAPMSGS, a different panel is displayed. See Code Processing of Message ID CAPMSGS.

Use this panel to specify a series of code definitions. Each code definition consists of up to three code values and an associated Value Returned.

The code definitions can be used by automation procedures to check, if a set of up to three given values matches with one of the code definitions in the automation policy. The values to be checked may be extracted variable values from an automated message or any other retrieved values, for which a matching code definition is searched. The associated Value Returned of the matching code definition can be used to decide about the further processing in the automation procedure.

Code definitions are used by SA z/OS, for example, to determine the severity of received WTORs. Further on, when processing termination messages of resources, SA z/OS uses code definitions to decide what status to place the resource in. In your own automation routine, you can use the common routine CDEMATCH to compare a set of given values with a series of code definitions in the automation policy and to gather the Value Returned from the matching code definition. For more details about common routine CDEMATCH, see IBM Z® System Automation Programmer's Reference.

You can use line commands in the Cmd field to manipulate the entries on this panel as described in Line Commands on Message Processing Panels in How to View Long Input Fields in Full Length.

The fields on this panel are used by the CDEMATCH routine.

Code 1, 2, 3

Patterns in these fields are compared with a set of up to three given values that are provided by the calling procedure. If one of the defined sets of code patterns matches, the content of the corresponding Value Returned field is returned to be used for further processing and no further comparison is done.

If no match is found, a null string is returned.

If the pattern is a single token, string comparison is performed. Such a pattern can contain wildcard characters in any position and combination. An asterisk (*) matches a string of arbitrary length and a percent sign (%) matches a single character.

Preceding the asterisk or percent sign with a backslash (\) prevents these characters from being considered as wildcard characters.

A pattern can also consist of two tokens. In this case, the first token is a string or numeric comparison operator and the second is the value to be compared to (wildcard characters are not supported).

The following string comparison operators are supported:

$EQ

equal to

$NE

not equal to

$GT

greater than

$GE

greater than or equal to

$LT

less than

$LE

less than or equal to

String comparison is done by character and in binary format after all the values have been translated to uppercase. For strings with different lengths, the shorter string is padded with blank characters at the end of the string to make it the same length as the longer string. Strings that consist of whole numbers with or without leading zeros are not considered as equal.

The following numeric comparison operators are supported:

@EQ

equal to

@NE

not equal to

@GT

greater than

@GE

greater than or equal to

@LT

less than

@LE

less than or equal to

Whole numbers up to an absolute value of 2³¹–1 are accepted.

For numeric comparison, whole numbers with or without leading zeros are considered as equal.

Value Returned

If all the specified values in the code fields match the passed values from the calling procedure, the value in this field is returned to be used for further processing.