DADS Plus production batch interface job fails with DADSB966 DADSAPI error message abend code AEYQ.
Article ID: 189977
An existing DADS Plus batch interface job failed with a DADSB966 DADSAPI error abend code AEYQ in DADS plus modules DADSAD8 and DADSBI1.
The client is running CTS 5.2 and no changes were recently made to the environment. The batch job is using the DADS Plus GROUP parameter to target the files in six CICS regions. The DADS batch job abends in three of the six regions.
In the batch job you see the GROUP parameter being used and the DADSAPI error message with a return code 008
In the DADSLOG and MSGUSR you see the following DADSAPI error messages followed by the AEYQ abend in DADS Plus modules DADSAD8 and DADSBI1.
DADSB962 05:49:05 PFORPAID JOBN=JDCR073D REQUEST(S) STARTED FOR APPLID=PFORPAID 04/26/2020 JOB#=0010343 DADSB963 05:49:05 PFORPAID JOBN=JDCR073D REQUESTS DEALLOCATE OF CLASS=DCRSPLNA JOB#=0010343 DADSB966 05:49:05 PFORPAID JOBN=JDCR073D DADSAPI ABENDED PROCESSING REQUEST
05.49.05 S0010303 +GSVC118W (Task) TRAN dump AEYQ 4/0001 Tran DADB 146 Program DADSAD8 Term * Userid PFORPAID AbCode * 05.49.05 S0010303 OPS1000I MSG.GSVC118W: NOT AEXY TRAN CKTI...EXITING 05.49.05 S0010303 +GSVC118W (Task) TRAN dump AEYQ 4/0002 Tran DADB 146 Program DADSBI1 Term * Userid PFORPAID AbCode * 05.49.05 S0010303 OPS1000I MSG.GSVC118W: NOT AEXY TRAN CKTI...EXITING .
The cause of the problem was a timing error. The client has a DADS Plus custom user exit that requires other CICS regions not specified in the GROUP parameter to be active on the LPAR when these batch jobs run. On this particular night the batch processing jobs started at a different time not the regularly scheduled time. Because of this not all the CICS regions on the LPAR were initialized. When the custom exit tried to communicate with a remote CICS region that was not active the DADSAPI program failed with the AEYQ abends in the DADS Plus modules.
When the client engaged the DADS support team the problem could not be reproduce since all the CICS regions were now active and available on the LPAR.
Analysis at the time showed that the client had defined a DADS PREOPEN and PRECLOSE (PCPPXFOR) exit that was remotely defined to another region, but that region was down causing the AEYQ abend. Once the client started the remote CICS regions the batch jobs ran without error.
The DADS Plus custom exits are store in the DADS01 control file. These exits can be displayed in CICS by entering the DADC transaction on a clear screen and pressing enter. The exits are listed below.
PREOPEN ==> PRECLOSE ==>
APPLID A11IC4S5 CA-DADS/PLUS 4.0 GLOBAL ALLOCATION OPTIONS DISPLAY COMMAND ===> OPTION STATUS: CURRENT CNTL FILE CURRENT CNTL FILE --------|--------- --------|--------- DADS APPLID ==> A11IC4S6 BATCH INTERFACE => N N VERIFY ==> Y Y BATCHQUEUECOLD ==> N N ALTDSNAME ==> N N BATCHQUEUEWARM ==> N N SUBTASKING ==> N N BATCHQUEUEEMER ==> N N SVC NUMBER ==> 230 230 FCTUPDATE ==> A A ONLINE EXITS => N N ACTIVEPSB ==> N N (EXIT PROGRAM NAMES LISTED BELOW) (N=NORMAL|B=BYPASS|MM=WAIT MINS) PREREQUEST ==> POSTREQUEST ==> PREALLOCATE ==> PREDEALLOCATE ==> PREOPEN ==> PCPPXFOR PRECLOSE PCPPXFOR MIGRATEDDSN ==> N N GENLEVEL = 0507.------------------------------------------------------------- PF3-END PF4-EXIT PF9-UPDTE