Dbctl Tracking Program Exits Xxdfb And Xxdto - IBM SC34-6814-04 Customization Manual

XPI calls

DBCTL tracking program exits XXDFB and XXDTO

Exit XXDFB
When invoked
Exit-specific parameters
Return codes
XPI calls
Exit XXDTO
When invoked
46
Customization Guide
UERCABDU
Abend CICS with a dump.
TRANSACTION_DUMP must not be used.
By the alternate CICS when it receives a message from the active CICS
indicating that connection to DBCTL has failed. The alternate and active
CICS systems are running in different MVS images, perhaps in different
central processing complexes (CPCs). More information about these exits is
provided in the CICS IMS Database Control Guide.
UEPDBXR
Address of CICS XRF information for use with DBCTL. The CICS
XRF information can be mapped using the DSECT DFHDXUEP.
UERCNOAC
Take no action.
UERCSWCH
Switch to the alternate DBCTL.
UERCABNO
Abend CICS without a dump.
UERCABDU
Abend CICS with a dump.
The return code 'UERCNORM' is not available for use at this exit point.
The following must not be used:
v INQUIRE_MONITORING_DATA
v MONITOR
v TRANSACTION_DUMP
v WRITE_JOURNAL_DATA.
By an alternate CICS when it performs takeover under the following
conditions:
v The active and alternate CICS systems are in different MVS images,
perhaps in different processors.
v The active CICS was connected to, or trying to connect to, a DBCTL
subsystem. (This does not include disconnecting from one DBCTL and
reconnecting to another.)
v The takeover was not initiated by the XXDFB exit, or the takeover was
initiated by XXDFB but the active system reestablished a DBCTL
connection before takeover occurred and XXDTO was driven for a new
DBCTL takeover decision.