Question & Answer
Question
Why is CBAC, the CICS mirror task, failing with an RLEL or AKCS abend followed by abend AEXZ during peak batch processing of my CICS Batch Application Control for z/OS (CICS BAC) V1.1.1 Batch Request Utility (BRU) jobstep?
After CBAC abends my batch job fails abnormally with messages:
CBKSC8008E jobname Unknown error received from region xxxxxxxx during
EXCI request. Error codes: 0000000C 000001A6 00000000
C1C5E7E9 00000000
IEA995I SYMPTOM DUMP OUTPUT
USER COMPLETION CODE=3111
TIME=03.22.02 SEQ=38141 CPU=0000 ASID=013D
PSW AT TIME OF ERROR 078D1000 8002FA06 ILC 2 INTC 0D
ACTIVE LOAD MODULE ADDRESS=00007EE8 OFFSET=00027B1E
NAME=CBKBMAIN
DATA AT PSW 0002FA00 - 00181610 0A0D9120 A08847E0
GR 0: C0000000 1: C0000C27
2: 2385B000 3: 00000001
4: 23873000 5: 23866A00
6: 23866400 7: 00000000
8: 23800700 9: 00038B10
A: 00041000 B: 000304A0
C: 0002F4A0 D: 00043000
E: 8002F966 F: 00030930
END OF SYMPTOM DUMP
IEF472I jobname $TEPnnn jobname - COMPLETION CODE - SYSTEM=000
USER=3111 REASON=00000000
Answer
This is due to OMEGAMON Resource Limit Elapsed Time abend RLEL of the CBAC CICS mirror task.
In this instance, a CICS system dump showed almost 13 seconds of Miscellaneous TCB dispatch time (MSDISPT) which would occur on the FO TCB. This can be related to MVS catalog LOCATE calls or other delays related to accessing the data set.
An AKCS abend can also occur if the task is not subject to the RLEL OMEGAMON monitoring for elapsed time.
If you cannot determine the source of the delay or contention using RMF III, you can consider adding or increasing the DTIMOUT value associated with the CICS BAC mirror transaction id so it can run longer before getting timed out.
Note: You could increase the RLEL time, however when I discussed with the developer, he recommended no limits on the mirror as this task is performing batch updates and should be allowed to finish.
Product Synonym
CICSBAC CICS BAC
Was this topic helpful?
Document Information
Modified date:
12 January 2016
UID
dwa1243074