The CICS system, with specific applid given, was unable to obtain working storage to control the sequencing of DBCTL connection attempts defined in the RST. (Recovery Service Table).
CICS attempts to connect only to the DBCTL subsystem defined in the DBCTL start-up table.
The working storage can be above the 16MB line so the GETMAIN request is unlikely to fail for genuine lack of space. If the error is persistent it may be necessary to cancel CICS with a dump to resolve the problem.
Console
DFHDXAX
The CICS system, with the specific applid given, was unable to load the RST rstname while looking for the names of alternative DBCTL subsystems to which to connect.
CICS will attempt to connect only to the DBCTL subsystem defined in the DBCTL start-up table.
Check that the RST suffix in the SIT is correct and that the RST is actually present in the authorized library.
Console
DFHDXAX
The CICS system, with the specific applid given, found that the RST rstname was invalid.
It is unable to use it to look for the names of alternative DBCTL subsystems to which to connect.
CICS will attempt to connect only to the DBCTL subsystem defined in the DBCTL start-up table.
Check that the RST suffix in the SIT is correct and that the RST has been correctly prepared using the DFHRST macro that is supplied as part of the CICS product.
Console
DFHDXAX
The CICS system, with the specific applid given, was unable to delete the RST rstname after completing an attempt to connect to a DBCTL subsystem.
CICS continues normally.
If the error is persistent it may be necessary to cancel CICS with a dump to resolve the problem.
Console
DFHDXAX
This message occurs in an XRF environment only. It occurs when CICS attempts to connect to DBCTL but believes that DBCTL is restarting.
The message is displayed two minutes after the attempted connection, and then after each subsequent minute.
CICS continues to attempt to reconnect.
Check why DBCTL is not restarting. You can cancel the connection using the CDBC transaction.
Console
DFHDXAX
CICS has detected that a subtask, attached during CICS XRF support of DBCTL, cannot be detached during CICS termination.
CICS abends with code A03.
Message DFHME0116 is normally produced containing the symptom string for this problem.
None. This abend occurs as a result of a previous error. Check for earlier DFHDX832x, DFHDX833x, or DFHDX834x error messages for further information and guidance.
Console
DFHAPDM
XMEOUT Parameter: applid
The catch-up transaction, CXCU, has received control.
The catch-up transaction is about to initiate the catch-up tasks for specific functional areas.
None. This is simply a "work is in progress" message. You can suppress this message with the system initialization parameter, MSGLVL=0.
Console
DFHCXCU
XMEOUT Parameter: applid
The catch-up transaction, CXCU, was invoked but the CICS system specified XRF=NO. Catchup functions are not relevant.
The catch-up transaction terminates normally without taking any action.
None.
Console
DFHCXCU
XMEOUT Parameter: applid
The catch-up transaction, CXCU, running on the CICS system with specific applid given, was unable to call the specific catch-up service routine progname. This may be either DFHDXCU (DBCTL catch-up) or DFHZXCU (terminal catch-up).
The catch-up associated with routine progname is not performed.
The active and alternate CICS systems continue, but the alternate will be less effective in the event of a takeover.
Retry by entering ‘CXCU’ from a terminal. If the error persists check that the routine progname is present in the load library.
Console
DFHCXCU
XMEOUT Parameters: applid, progname
The catch-up transaction, CXCU, running on the CICS system with specific applid given, has failed. CXCU runs either in response to a transaction request from an end-user, or automatically by an active CICS system in response to the appearance of an alternate CICS system. Its purpose is to inform the alternate of the active’s state regarding terminals and DBCTL connection.
The CXCU transaction abends with a dump and transaction abend code ACXA.
Both active and alternate CICS systems continue, but the alternate will be less effective in the event of a takeover. For example, terminal backup sessions may not be established.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Retry by entering ‘CXCU’ from a terminal. If the error persists diagnose problem from the dump.
Console
DFHCXCU
XMEOUT Parameter: applid
The catch-up transaction to transmit the active’s DBCTL state to the alternate has been started on the CICS system with specific applid named.
None.
None. You can suppress this message with the system initialization parameter, MSGLVL=0.
Console
DFHDXCU
XMEOUT Parameter: applid
The catch-up transaction to transmit the active’s DBCTL state to the alternate has been completed on the CICS system with specific applid given.
None.
None. You can suppress this message with the system initialization parameter, MSGLVL=0.
Console
DFHDXCU
XMEOUT Parameter: applid
The XRF DBCTL catch-up transaction has been invoked on the CICS system with the given specific applid.
Although this system has DL/I installed, and an RST has been specified in the SIT, catch-up for DBCTL has proved unnecessary for reason nn, where nn may be one of the following.
None. No catch-up is needed.
None. You can suppress this message with the system initialization parameter, MSGLVL=0.
Console
DFHDXCU
XMEOUT Parameters: applid, nn
The XRF DBCTL catch-up transaction has been invoked on the CICS system with the given specific applid.
The transaction has failed for reason nn, where nn may be one of the following.
The DBCTL catch-up transaction is terminated with a dump. The transaction abend code is ADXB.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Check for any other messages relating to CAVM data set problems for further information and guidance.
Console
DFHDXCU
XMEOUT Parameters: applid, nn
The XRF DBCTL catch-up transaction has been invoked on the CICS system with the given specific applid.
The transaction has failed.
The DBCTL catch-up transaction is terminated with a dump. The transaction abend code is ADXA.
Message DFHME0116 is normally produced containing the symptom string for this problem.
Diagnose the error from the dump.
Console
DFHDXCU
XMEOUT Parameter: applid
The user exit XXDFA requested a restart of DBCTL. The restart was initiated successfully.
The active CICS continues normally and will attempt to reconnect to DBCTL.
None. You can suppress this message with the SIT parameter, MSGLVL=0.
Console
DFHDBCT
XMEOUT Parameter: applid
CICS can offer full XRF support only if the DBCTL to which it is connected is running under the same JES as CICS itself.
nn may be one of the following.
The active CICS continues, but, in the event of failure, CICS will not attempt to restart DBCTL automatically.
None.
Console
DFHDBCT
XMEOUT Parameters: applid, X'nn'
CICS has been notified of a DBCTL failure, but has been unable to load the specified Recovery Service Table (RST) to determine if XRF support is required.
CICS continues as if no XRF support had been requested for the failing DBCTL subsystem.
Re-link-edit a valid RST into STEPLIB. DBCTL may have to be restarted manually.
Console
DFHDBCT
XMEOUT Parameters: applid, xxxxxxxx
CICS has been notified of a DBCTL failure, but has been unable to complete the search for a DBCTL alternate, possibly due to an unexpected return code from an IEFSSREQ request.
CICS continues as if no DBCTL alternate had been found. An ADDI transaction dump will be produced. Message DFHME0116 is normally produced containing the symptom string for this problem.
You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.
Console
DFHDBCT
XMEOUT Parameter: applid
CICS was unable to restart DBCTL owing to an internal failure indicated by the value of n. n may be one of the following.
The active CICS continues but was not able to restart DBCTL automatically. However, it will attempt to reconnect to DBCTL in the normal way.
It may be necessary to restart DBCTL manually.
Console
DFHDBCT
XMEOUT Parameters: applid, xxxxxxxx, X'nn'
The user exit XXDFA requested a restart of DBCTL. The restart request was issued to subsysid but was rejected with hexadecimal reason codes X'xx' and X'yy'.
The active CICS continues normally and will attempt to reconnect to DBCTL.
It may be necessary to restart DBCTL manually.
Console
DFHDBCT
XMEOUT Parameters: applid, subsysid, X'xx', X'yy'
The active CICS system was unable to report a change of DBCTL connection status to the alternate.
The active system writes an error entry in its CAVM status record, but otherwise continues normally.
Check for any other messages relating to CAVM data set problems.
Were the CICS alternate to take over now it might try to restart the wrong DBCTL. There would be no database integrity exposure but there might some loss of availability as well as operational inconvenience. It may be preferable to cancel the alternate and restart it, either manually or via an overseer.
Console
DFHDBCT
XMEOUT Parameter: applid
The active CICS system was unable to report a change of DBCTL connection status to the overseer.
Processing continues.
Check for any other CICS messages relating to CAVM data set problems (DFH66xx).
Were the overseer to oversee a takeover now it might try to restart the wrong DBCTL. There would be no database integrity exposure but there might some loss of availability as well as operational inconvenience.
If the overseer is being used to control XRF takeovers then disconnecting and reconnecting to the DBCTL will cause a re-write of the status record.
Console
DFHDBCT
XMEOUT Parameter: applid
CICS can offer full XRF support only if the DBCTL to which it is connected is running under the same JES as CICS itself.
The active CICS continues, but, in the event of failure, CICS will not attempt to restart DBCTL automatically.
It is recommended that DBCTL should be run under the same JES as the active CICS system.
The message indicates that either a system or set-up problem has occurred. If there is a system problem then message DFHDX8321 will also be displayed.
Console
DFHDBCT
XMEOUT Parameters: applid, jobname,jobid
The user exit XXDFA requested a restart of DBCTL. This request has been ignored for the reason indicated by nn.
The reason code nn should be one of the following.
The active CICS continues as if the user exit had indicated ‘no action’.
Check that the user exit is performing as intended and that the CICS and DBCTL systems have been set up with the correct options.
Console
DFHDBCT
XMEOUT Parameters: applid, X'nn'
This message is produced when CICS connects to an IMS system for which the user has requested XRF support (via the RST), but which is unable to participate in XRF. For example, in an IMS/DC system without the XRF option.
The system continues to run without XRF.
Either enable IMS/DC for XRF, or remove SSID from RST.
Console
DFHDBCT
XMEOUT Parameter: applid
The alternate CICS system task responsible for tracking the DBCTL connection status of the active CICS has received an error response from the CAVM message input service.
The tracking transaction terminates. No further action will be taken in response to DBCTL status changes. The global exits XXDFB and XXDTO will never be invoked and no attempt at a DBCTL restart will be made in the event of a takeover. An ADMA transaction dump is produced.
Check for any other messages relating to CAVM data set problems. In the event of a takeover it may be necessary to restart DBCTL manually.
Console
DFHDBCR
XMEOUT Parameters: applid, xxxxxxxx, X'nn', xxxxxxxx
The alternate CICS system task responsible for tracking the DBCTL connection status of the active CICS has received a message from the CAVM message input service, after a takeover decision from the global user exit XXDFB has been accepted.
This problem is usually caused by a setup or an operational error.
The takeover continues. If the message is a notification of a successful connection, then the global user exit XXDTO may be driven.
In order for the active CICS system to reconnect to an element of the RSE, a DBCTL must have been restarted in the active CEC. Consequently, the alternate CICS will not be able to restart an element of the RSE in the alternate CEC without terminating this new active DBCTL.
The global user exit XXDTO will be driven as part of CICS takeover processing. This exit could be used to request a takeover of the DBCTL that was restarted in the active CEC.
Locate and correct any setup or operational errors.
Console
DFHDBCR
XMEOUT Parameters: applid, xxxxxxxx, xxxxxxxx
The alternate CICS system task responsible for tracking the DBCTL connection status of the active CICS has received an unrecognized message from the CAVM message input service.
The tracking transaction terminates. No further action will be taken in response to DBCTL status changes. The global exits XXDFB and XXDTO will never be invoked and no attempt at a DBCTL restart will be made in the event of a takeover. An ADMB transaction dump is produced. Message DFHME0116 is normally produced containing the symptom string for this problem.
In the event of a takeover it may be necessary to restart DBCTL manually.
Console
DFHDXCU
XMEOUT Parameters: applid, xxxxxxxx
The alternate CICS system task responsible for tracking the DBCTL connection status of the active CICS has detected an invalid recovery service table (RST) during processing of a CICS|DBCTL failure.
nn may be one of the following.
The tracking transaction continues as if no XRF support had been requested via the RST for the connected DBCTL.
In the event of a takeover it may be necessary to restart DBCTL manually. When the failure is detected during the initialization of the XRF/DBCTL tracking task the RST should be assembled and link-edited to resolve the problem.
Console
DFHDBCR
XMEOUT Parameters: applid, xxxxxxxx, nn
The alternate CICS system task responsible for tracking the DBCTL connection status of the active CICS has been unable to complete its search for a DBCTL alternate, possibly due to an unexpected return code from an IEFSSREQ request.
The tracking transaction continues as if no DBCTL alternate had been found. An ADMD transaction dump will be produced.
In the event of a takeover it may be necessary to restart DBCTL manually.
Console
DFHDBCR
XMEOUT Parameter: applid
The user exit XXDFB or XXDTO requested a restart of DBCTL. This request has been ignored for the reason indicated by the value of nn.
n may be one of the following.
The alternate CICS continues as if the user exit had indicated ‘no action’.
Check that the user exit is performing as intended and that the CICS and DBCTL systems have been set up with the correct options.
Console
DFHDBCR
XMEOUT Parameters: applid, X'nn'
The user exit XXDFB requested a takeover as a result of a DBCTL failure, but the CAVM rejected the takeover request.
The alternate CICS continues as if the user exit had indicated ‘no action’.
Check that the user exit is performing as intended and that the CICS and DBCTL systems have been set up with the correct options. The message indicates that a CICS internal error has occurred, normally as a result of an earlier problem. It may be necessary to initiate a manual CICS takeover.
Console
DFHDBCR
XMEOUT Parameters: applid, X'nn'
The user exit XXDFB/XXDTO issued a restart request to the DBCTL/XRF tracking task, the task was unable to process the request for the reason indicated in the message.
The issued command should either be a switch system backup command or an ERE command.
The reason code X'nn' should be one of the following.
The takeover continues.
Restart the DBCTL subsystem manually.
Console
DFHDBCR
XMEOUT Parameters: applid, command,subsysid, X'nn'
The DBCTL/XRF tracking task issued a restart command (either switch or ERE) to an alternate DBCTL subsystem but the request was rejected for reason nn.
XXDFA or XXDTO requested CICS takeover with DBCTL. The error was detected when the request was made.
The takeover continues.
Restart the DBCTL subsystem manually.
Console
DFHDBCR
XMEOUT Parameters: applid, command,subsysid, X'nn'
The alternate CICS system task responsible for tracking the DBCTL connection status of the active CICS has been started in an environment which does not support DBCTL/XRF.
Reason code X'nn' may be one of the following.
The tracking transaction terminates. No further action will be taken in response to DBCTL status changes. The global exits XXDFB and XXDTO will never be invoked and no attempt at a DBCTL restart will be made in the event of a takeover.
The user response depends on the reason code issued.
For reasons X'65' and X'67', there is a possible error in CICS code. In this case you will need further assistance from IBM. See CICS Problem Determination Guide for guidance on how to proceed.
For reason X'69', specify a smaller overall size limit for the EDSAs.
Console
DFHDBCR
XMEOUT Parameters: applid, X'nn'
The DBCTL/XRF tracking task issued a takeover request due to a request from user exit XXDFB. The request has been accepted.
The takeover continues.
None. You can suppress this message with the system initialization parameter MSGLVL = 0.
Console
DFHDBCR
XMEOUT Parameter: applid
The DBCTL/XRF tracking task issued a restart command to an alternate DBCTL subsystem due to a request from user exit XXDFB/XXDTO. The request was issued successfully.
Takeover continues.
None. You can suppress this message with the system initialization parameter MSGLVL = 0.
Console
DFHDBCR
XMEOUT Parameter: applid