With DBCTL, your PSB scheduling request might fail either because DBCTL is not available, or because the PSB could not 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 9 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.
Request | EXEC abend | CALL UIBDLTR | CALL UIBFCTR | CALL abend | Explanation |
---|---|---|---|---|---|
PSB schedule request | DHTA | X'01' (PSBNF) | X'08' (INVREQ) | ---- | PSB not found1. |
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 in DBCTL only. |
PSB schedule request | DHTJ | X'FF' (DLINA) | X'08' (INVREQ) | ---- | DBCTL not available on PSB scheduling2. |
PSB schedule request | ADCC | ---- | ---- | ADCC | PSB already scheduled detected 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. |
PSB schedule request | ADDA | ---- | ---- | ADDA | An error response from the storage domain. |
DL/I request | DHTH | X'08' (FUNCNS) | X'08' (INVREQ) | ---- | PSB not scheduled, detected by CICS. |
DL/I request | ADCB | ---- | ---- | ADCB | PSB not scheduled. |
DL/I request | ADCD | ---- | ---- | ADCD | Deadlock detected. |
DL/I request | ADCI | ---- | ---- | ADCI | Lock outstanding. |
DL/I request | ADCJ | ---- | ---- | ADCJ | DBCTL not available on DL/I request3. |
DL/I request | ADCR | ---- | ---- | ADCR | DL/I request (other than PSB schedule) issued when DBCTL not connected. |
Terminate request | ASPR | ---- | ---- | ASPR | Single-phase commit request issued but CICS unable to report outcome. IMS™ updates will either have been backed out, or committed. IMS is not in-doubt about the UOW. |
Terminate request | ASP7 | ---- | ---- | ASP7 | Single-phase commit request failed. IMS backed out any updates in the UOW. |
Terminate request | DHTG | X'07' (TERMNS) | X'08' (INVREQ) | ---- | PSB not scheduled. |
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'04' (NOTDONE) | X'08' (INVREQ) | ---- | Global user exit XDLIPRE indicates that DL/I request should not be executed. |
PSB schedule or DL/I request | ADCA | ---- | ---- | ADCA | Error, detected in DBCTL. |
PSB schedule or DL/I request | ADCE | ---- | ---- | ADCE | Bad response code has been returned from DFHDBAT. |
PSB schedule or DL/I request | ADCN | ---- | ---- | ADCN | FORCEPURGE issued while executing in DBCTL. |
See the CICS Messages and Codes manual for details of these abends, and see the IMS Application Programming: EXEC DLI Commands manual for details of DL/I status codes.
If you use remote DL/I with DBCTL, you may also receive Axxx and DHxx abends not listed here. For information about DHxx abends (where 'xx' indicates the DL/I status code), see the IMS Application Programming: EXEC DLI Commands manual.