Summary of DBCTL abends and return codes

The schedule failure codes and abends in a DBCTL environment are listed, together with the conditions that can arise on a PSB schedule request because DBCTL is not available or the PSB cannot be found.

With DBCTL, your program specification block (PSB) scheduling request might fail either because DBCTL is not available, or because the PSB cannot be found. However, after a successful PSB schedule, CICS® might be disconnected from DBCTL for some reason, and subsequent DBCTL requests will fail. This situation, which is unique to a DBCTL environment, causes an ADCJ abend to be issued. Table 1 summarizes the schedule failure codes and abends in a DBCTL environment, and the conditions that can arise on a PSB schedule request because DBCTL is not available or the PSB cannot be found.

Table 1. Summary of abends and return codes
Request EXEC abend CALL UIBDLTR CALL UIBFCTR CALL abend Explanation
PSB schedule or DL/I request ADCA ---- ---- ADCA Error detected in DBCTL.
DL/I request ADCB ---- ---- ADCB PSB not scheduled.
PSB schedule request ADCC ---- ---- ADCC PSB already scheduled detected in DBCTL.
DL/I request ADCD ---- ---- ADCD Deadlock detected.
PSB schedule or DL/I request ADCE ---- ---- ADCE Bad response code has been returned from DFHDBAT.
DL/I request ADCI ---- ---- ADCI Lock outstanding.
DL/I request ADCJ ---- ---- ADCJ DBCTL not available on DL/I request 1.
PSB schedule or DL/I request ADCN ---- ---- ADCN FORCEPURGE issued while running in DBCTL.
PSB schedule request ADCP ---- ---- ADCP The user is not authorized to use the PSB.
PSB schedule request ADCQ ---- ---- ADCQ The SYSSERVE keyword or the I/O PCB option was not specified, and the PSB does not contain any DB PCBs.
DL/I request ADCR ---- ---- ADCR DL/I request (other than PSB schedule) issued when DBCTL not connected.
PSB schedule request ADDA ---- ---- ADDA An error response from the storage domain.
PSB schedule or DL/I request ADDK ---- ---- ADDK CICS Lock manager call failed.
Terminate request ASPR ---- ---- ASPR Single-phase commit request issued but CICS unable to report outcome. IMS updates are either backed out, or committed. IMS is not indoubt about the UOW.
Terminate request ASP7 ---- ---- ASP7 Single-phase commit request failed. IMS backed out any updates in the UOW.
PSB schedule request DHTA X'01' (PSBNF) X'08' (INVREQ) ---- PSB not found 2.
PSB schedule request DHTC X'03' (PSBSCH) X'08' (INVREQ) ---- PSB already scheduled detected in CICS.
PSB schedule request DHTE X'05' (PSBFAIL) X'08' (INVREQ) ---- PSB initialization failed.
Terminate request DHTG X'07' (TERMNS) X'08' (INVREQ) ---- PSB not scheduled.
DL/I request DHTH X'08' (FUNCNS) X'08' (INVREQ) ---- PSB not scheduled, detected by CICS.
PSB schedule request DHTJ X'FF' (DLINA) X'08' (INVREQ) ---- DBCTL not available on PSB scheduling 3.
PSB schedule, DL/I, and terminate requests DHxx ---- ---- ---- Many reasons. xx is the PCB status code. (See also Preventing DHxx abends after EXEC DLI SCHD PSB failure .)
PSB schedule or DL/I request ---- X'00' (INVARG) X'08' (INVREQ) ---- Invalid argument.
PSB schedule or DL/I request ---- TR status code in DIB- STAT X'14' (NOTDONE) X'08' (INVREQ) ---- Global user exit XDLIPRE indicates that DL/I request should not be run.
Note:
  1. DBCTL is in use, and a PSB has been scheduled. However, the connection between CICS and DBCTL has since been broken.
  2. The PSB was not found in PDIR and DBCTL was not ready. Alternatively, the PSB was not found in PDIR and DBCTL was ready but the PSB was not found in DBCTL APPLCTN.
  3. DBCTL was not ready at the time of the DL/I request.

If you use remote DL/I with DBCTL, you might also receive Axxx and DHxx abends that are not listed here.

For details of DL/I status codes, and information about DH xx abends (where xx indicates the DL/I status code), see IMS messages and codes in IMS product documentation.