What is the "global" default as far as what constitutes an exception as far as condition code processing?

Document ID : KB000046302
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:

What is the "global" default as far as what constitutes an exception as far as condition code processing? 

Zero, four, etc? is there a method to specify what the site global default is?

 

Resolution:

 Exceptional Conditions

When archiving SYSOUT, each record is scanned for exceptional conditions. You can have CA View check for an IEF system code, such as IEF142I, or you can specify any string of text to search as a user-specified condition.

You specify the exception conditions with control statements to the archival started task SARSTC. Each control statement applies to one or more jobs by specific or wildcard job names.

For completion codes and abends, the control statement can be further qualified to a specific step, procedure step, or both. A default control statement is provided to override one or all of the system defaults.

To enable editing of the exceptional condition table while the started task is active, the table must be established as a member of a PDS rather than a sequential data set.

Contents

 

 

System Exceptional Conditions

The following elements are checked to set exceptional conditions:

  • Identifier of the associated error message
  • Control statement parameters associated with that message ID
  • System default parameter

System Conditions

The corresponding exception code is stored in the group control record (GCR) for the SYSOUT group. The following table lists the system conditions CA View checks:


Condition


Message ID


Parameters

System Default


Exception Code

Condition code

IEF142I

CC
CC>nnnn
CCnnnn
NOCC
NOCCnnnn

CC

nnnn
(condition code)

Data set not deleted

IEF283I

NDEL
NONDEL

NDEL

NOTDEL

Data set not cataloged

IEF287I

NCAT
NONCAT

NCAT

NOTCAT

Data set not recataloged

IEF287I

RCAT
NORCAT

RCAT

NTRCAT

Data set not uncataloged

IEF287I

UCAT
NOUCAT

UCAT

NTUCAT

JCL error

IEF452I

IEFCA452I

IEF453I

JCL
NOJCL

JCL

JCLERR

Operator cancel

IEF251I

OCNCL
NOOCNCL

OCNCL

OCNCL

System abend

IEF472I

SYS SYSxxx
NOSYS
NOSYSxxx

SYS

Sxxx
(abend code)

User abend

IEF472I

USER
USERnnnn
NOUSER
NOUSERnnnn

USER

Unnnn
(abend code)

FIRST, LAST, and HIGH Specifications

The parameters FIRST, LAST, and HIGH specify whether the exception code for the first, last, or highest exception condition for the SYSOUT group are retained in the group control record.

The FIRST, LAST, and HIGH keywords are mutually exclusive. LAST is the system default.

Note: CA View looks at the various JES data sets for messages. The three JES data sets are archived in the following order: the messages log (JESMSGLG), the JCL (JESJCL), and the system messages (JESYSMSG). The default exception code processing is LAST. The JCL error message (IEF453I) appears in the JESMSGLG. The condition code message (IEF142I) appears in the JESYSMSG, which is the LAST exception code. To see the JCL error, a global entry is in the Exception Code Table (SARXCTAB) as follows:

/*           HIGH

Control Statements for System Conditions

Control statements are input to the archival started task using the SARXCTAB DD statement and the following general structure:

/ID parameters

The slash is coded in column 1 and the job name immediately follows. One or more blanks follow the ID and separate it from the parameters. Separate individual parameters by one or more blanks, commas, or both. A statement that exceeds 71 characters is continued on additional statements. When continuing a statement, interrupt the statement only between complete parameters.

The ID identifies the job to which the statement applies. The statement is as follows:

jobname(.stepname(.procstepname))

Where

  • jobname
    Specifies the name of the job to which the statement applies
    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.
  • stepname
    Specifies the name of the job step to which the statement applies
    stepname is optional and can only be coded for completion code and/or abend exceptions. If omitted, the statement applies to all job steps.
  • procstepname
    Specifies the name of the procedure step to which the statement applies procstepname is optional and can only be coded for completion code and/or abend exceptions. If omitted, the statement applies to all procedure steps.

Because qualification by job and procedure step names only applies to completion code and abend exceptions, multiple control statements can be required for the same job. One statement specifies only the job name without further qualification.

Parameters in the Control Statements

All parameters applicable to the entire job are coded. Additional statements, qualified to a particular job and procedure steps, are also used. Only the completion code, system parameters, and user abend parameters are coded on these additional statements. You can code the following parameters:

  • CC
    Specifies the following conditions:
    • A condition code message for a nonzero condition code is treated as an exceptional condition
    • A condition code message for a zero (0) condition code is not treated as an exceptional condition
  • NOCC
    Specifies there are no condition code exception conditions.
  • CC>nnnn
    Specifies a condition code message with a condition code greater than nnnn is treated as an exceptional condition unless:
    • A NOCCnnnn parameter is also specified for the condition code. A condition code message with a condition code less than or equal to nnnn is not treated as an exceptional condition
    • A CCnnnn parameter is also specified for the condition code
  • CCnnnn
    Specifies the following conditions:
    • A condition code message with a condition code equal to nnnn is treated as an exceptional condition
    • A condition code message with a condition code not equal to nnnn is not treated as an exceptional condition unless identified as an exceptional condition by another CCnnnn or CC>nnnn parameter
  • NOCCnnnn
    Specifies the following conditions:
    • A condition code message with a condition code equal to nnnn is not treated as an exceptional condition
    • A condition code message with a condition code not equal to nnnn is treated as an exceptional condition unless identified as not being an exceptional condition by another NOCCnnnn or CC>nnnn parameter

0000 specifies when multiple exceptions occur for a SYSOUT group, the first exception code for the group is retained in the group control record.
000 specifies a JCL error message is treated as an exceptional condition.

  • NOJCL
    Specifies there are no JCL exception conditions.
  • FIRST
    Specifies when multiple exceptions occur for a SYSOUT group, the first exception code for the group is retained in the group control record.
  • LAST
    Specifies when multiple exceptions occur for a SYSOUT group, the last exception code for the group is retained in the group control record.
  • HIGH
    Specifies when multiple exceptions occur for a SYSOUT group, the one with the highest priority is retained in the group control record.
    The following list defines the XCODE priorities in highest to lowest order:
    1. SYSTEM ABEND
    2. USER ABEND
    3. JCL ERROR
    4. NONZERO CONDITION CODE
    5. OPERATOR CANCEL
    6. NOT CATALOGED
    7. NOT DELETED
    8. NOT RECATALOGED

If multiple exceptions occur with the same priority, the one with the highest numerical value is used.

  • NCAT
    Specifies a NOT CATALOGED message is treated as an exceptional condition.
  • NONCAT
    Specifies a NOT CATALOGED message is not treated as an exceptional condition.
  • NDEL
    Specifies a NOT DELETED message is treated as an exceptional condition.
  • NONDEL
    Specifies a NOT DELETED message is not treated as an exceptional condition.
  • OCNCL
    Specifies an OPERATOR CANCEL IN ALLOCATION RECOVERY message is not treated as an exceptional condition.
  • RCAT
    Specifies a NOT RECATALOGED message is treated as an exceptional condition.
  • NORCAT
    Specifies a NOT RECATALOGED message is not treated as an exceptional condition.
  • SYS
    Specifies a system abend code message for any abend code is treated as an exceptional condition.
  • NOSYS
    Specifies a system abend code message for any abend code is not treated as an exceptional condition.
  • SYSxxx
    Specifies a system abend code message for abend code xxx is treated as an exceptional condition. A message for any abend code other than xxx is not treated as an exceptional condition unless identified as an exceptional condition by another SYSxxx parameter.
  • NOSYSxxx
    Specifies a system abend code message for abend code xxx is not treated as an exceptional condition. A message for any abend code other than xxx is treated as an exceptional condition unless identified as not being an exceptional condition by another NOSYSxxx parameter.
  • UCAT
    Specifies a NOT UNCATALOGED message is treated as an exceptional condition.
  • NOUCAT
    Specifies a NOT UNCATALOGED message is not treated as an exceptional condition.
  • USER
    Specifies a user abend code message for any abend code is treated as an exceptional condition.
  • NOUSER
    Specifies a user abend code message for any abend code is not treated as an exceptional condition.
  • USERnnnn
    Specifies a user abend code message for abend code nnnn is treated as an exceptional condition. A message for any abend code other than nnnn is not treated as an exceptional condition unless identified as an exceptional condition by another USERnnnn parameter.
  • NOUSER
    nnnn

    Specifies a user abend code message for abend code nnnn is not treated as an exceptional condition. A message for any abend code other than nnnn is treated as an exceptional condition unless identified as not being an exceptional condition by another NOUSERnnnn parameter.

 

Additional Information:

As always, please contact CA Technologies support for CA View if you have further questions.