The client added this entry to their SARXCTAB exception table:
/OFATKERR.RUN$IT.CHKEMPT2 NOCC0000 NOCC0004
Their job in question had the following results:
JOB08449 -STEPNAME PROCSTEP RC
JOB08449 -JOBTRMS RMS@2X 00
JOB08449 -RUN$IT CHKEMPT1 04
JOB08449 -RUN$IT SAMSAM3 FLUSH
JOB08449 -RUN$IT CHKEMPT2 04
JOB08449 -RUN$IT SAMSAM6 FLUSH
JOB08449 -RUN$IT MSGSTEP FLUSH
JOB08449 -$J FLUSH
View highlighted the following statement on the console and syslog:
*SARSTC99 JOB08449 OFATKERR COND CODE 0004
Why is this message appearing, despite the entry in the table?
Release : 12.2
Component : CA View
The client had this in their SARXCTAB, exception code table:
/DEFAULT LAST NONDEL NONCAT NORCAT
/OFATKERR.RUN$IT.CHKEMPT2 NOCC0000 NOCC0004
The job output was as follows:
JOB08449 -STEPNAME PROCSTEP RC
JOB08449 -JOBTRMS RMS@2X 00
JOB08449 -RUN$IT CHKEMPT1 04
JOB08449 -RUN$IT SAMSAM3 FLUSH
JOB08449 -RUN$IT CHKEMPT2 04
JOB08449 -RUN$IT SAMSAM6 FLUSH
JOB08449 -RUN$IT MSGSTEP FLUSH
JOB08449 -$J FLUSH
The "/OFATKERR.RUN$IT.CHKEMPT2 ..." statement resolves the CHKEMPT2 output and condition.
The SARXCTAB statement of "/DEFAULT LAST ...", would be the next statement of effect.
The message of "SARSTC99 JOB08449 OFATKERR COND CODE 0004", then, refers to the above CHKEMPT1 step.
The client will add statement "OFATKERR.RUN$IT.CHKEMPT1 NOCC0000 NOCC0004", for that condition.