DFHDXxxxx messages

Start of change
DFHDX8300I
applid GETMAIN REQUEST FAILED. NOT ATTEMPTING TO CONNECT TO ALTERNATE SYSTEMS.
Explanation:

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).

System action:

CICS attempts to connect only to the DBCTL subsystem defined in the DBCTL start-up table.

User response:

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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDXAX

End of change
Start of change
DFHDX8301I
applid LOAD REQUEST FAILED FOR rstname. NOT ATTEMPTING TO CONNECT TO ALTERNATE SYSTEMS.
Explanation:

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.

System action:

CICS will attempt to connect only to the DBCTL subsystem defined in the DBCTL start-up table.

User response:

Check that the RST suffix in the SIT is correct and that the RST is actually present in the authorized library.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDXAX

End of change
Start of change
DFHDX8302I
applid VALIDATION FAILED FOR rstname. NOT ATTEMPTING TO CONNECT TO ALTERNATE SYSTEMS.
Explanation:

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.

System action:

CICS will attempt to connect only to the DBCTL subsystem defined in the DBCTL start-up table.

User response:

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.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDXAX

End of change
Start of change
DFHDX8303
applid DELETE REQUEST FAILED FOR rstname.
Explanation:

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.

System action:

CICS continues normally.

User response:

If the error is persistent it may be necessary to cancel CICS with a dump to resolve the problem.

Note:
This message cannot be changed with the message editing utility.
Destination:

Console

Modules:

DFHDXAX

End of change
Start of changeDFHDX8304End of change
Start of changeapplid CICS/DBCTL RECONNECTION IN PROGRESS.End of change
Start of change
Explanation:

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.

End of change
Start of change
System action:

CICS continues to attempt to reconnect.

End of change
Start of change
User response:

Check why DBCTL is not restarting. You can cancel the connection using the CDBC transaction.

Note:
This message cannot be changed with the message editing utility.
End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHDXAXEnd of change

DFHDX8309
applid Unable to detach subtask during CICS termination.
Explanation:

CICS has detected that a subtask, attached during CICS XRF support of DBCTL, cannot be detached during CICS termination.

System action:

CICS abends with code A03.

Message DFHME0116 is normally produced containing the symptom string for this problem.

User response:

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.

Destination:

Console

Modules:

DFHAPDM

XMEOUT Parameter: applid

DFHDX8310I
applid Initiating catch-up tasks.
Explanation:

The catch-up transaction, CXCU, has received control.

System action:

The catch-up transaction is about to initiate the catch-up tasks for specific functional areas.

User response:

None. This is simply a "work is in progress" message. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHCXCU

XMEOUT Parameter: applid

DFHDX8311I
applid System initialized with XRF=NO. Catch-up transaction CXCU took no action.
Explanation:

The catch-up transaction, CXCU, was invoked but the CICS system specified XRF=NO. Catchup functions are not relevant.

System action:

The catch-up transaction terminates normally without taking any action.

User response:

None.

Destination:

Console

Modules:

DFHCXCU

XMEOUT Parameter: applid

DFHDX8312I
applid Catch-up transaction failed to run program progname. Catch-up is incomplete.
Explanation:

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).

System action:

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.

User response:

Retry by entering ‘CXCU’ from a terminal. If the error persists check that the routine progname is present in the load library.

Destination:

Console

Modules:

DFHCXCU

XMEOUT Parameters: applid, progname

DFHDX8313I
applid Catch-up transaction failed.
Explanation:

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.

System action:

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.

User response:

Retry by entering ‘CXCU’ from a terminal. If the error persists diagnose problem from the dump.

Destination:

Console

Modules:

DFHCXCU

XMEOUT Parameter: applid

DFHDX8315I
applid XRF DBCTL state catch-up starting.
Explanation:

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.

System action:

None.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHDXCU

XMEOUT Parameter: applid

DFHDX8316I
applid XRF DBCTL state catch-up ending.
Explanation:

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.

System action:

None.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHDXCU

XMEOUT Parameter: applid

DFHDX8317I
applid XRF DBCTL state catch-up ignored for reason nn.
Explanation:

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.

Reason
Meaning
01
DBCTL has not been used yet.
02
XRF DBCTL has not been used yet.
03
There is no connection state information to send.
04
The system is running with XRF=NO.
05
There is no alternate CICS to which to send state data.
System action:

None. No catch-up is needed.

User response:

None. You can suppress this message with the system initialization parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHDXCU

XMEOUT Parameters: applid, nn

DFHDX8318I
applid XRF DBCTL state catch-up failed for reason nn.
Explanation:

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.

Reason
Meaning
01
The CAVM message service returned an unidentifiable return code.
02
The CAVM message service returned an unexpected exception return code.
03
The CAVM message service returned an unexpected failure reason code.
System action:

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.

User response:

Check for any other messages relating to CAVM data set problems for further information and guidance.

Destination:

Console

Modules:

DFHDXCU

XMEOUT Parameters: applid, nn

DFHDX8319I
applid XRF DBCTL state catch-up failed.
Explanation:

The XRF DBCTL catch-up transaction has been invoked on the CICS system with the given specific applid.

The transaction has failed.

System action:

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.

User response:

Diagnose the error from the dump.

Destination:

Console

Modules:

DFHDXCU

XMEOUT Parameter: applid

DFHDX8320I
applid DBCTL Restart processing completed after DBCTL failure.
Explanation:

The user exit XXDFA requested a restart of DBCTL. The restart was initiated successfully.

System action:

The active CICS continues normally and will attempt to reconnect to DBCTL.

User response:

None. You can suppress this message with the SIT parameter, MSGLVL=0.

Destination:

Console

Modules:

DFHDBCT

XMEOUT Parameter: applid

DFHDX8321
applid Unable to determine JES affiliation of DBCTL subsystem for reason X'nn'.
Explanation:

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.

nn
Meaning
X'09'
MVS GETMAIN failure.
X'10'
MVS ATTACH failure.
System action:

The active CICS continues, but, in the event of failure, CICS will not attempt to restart DBCTL automatically.

User response:

None.

Destination:

Console

Modules:

DFHDBCT

XMEOUT Parameters: applid, X'nn'

DFHDX8322
applid LOAD request failed for xxxxxxxx. DBCTL/XRF support will not be provided for this connection.
Explanation:

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.

System action:

CICS continues as if no XRF support had been requested for the failing DBCTL subsystem.

User response:

Re-link-edit a valid RST into STEPLIB. DBCTL may have to be restarted manually.

Destination:

Console

Modules:

DFHDBCT

XMEOUT Parameters: applid, xxxxxxxx

DFHDX8323
applid Unable to complete search for DBCTL alternate.
Explanation:

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.

System action:

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.

User response:

You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

Note:
It may be necessary to restart DBCTL manually.
Destination:

Console

Modules:

DFHDBCT

XMEOUT Parameter: applid

DFHDX8324
applid Unable to restart DBCTL xxxxxxxx for reason X'nn'.
Explanation:

CICS was unable to restart DBCTL owing to an internal failure indicated by the value of n. n may be one of the following.

n
Meaning
X'08'
An MVS GETMAIN failed.
X'09'
An MVS ATTACH failed.
System action:

The active CICS continues but was not able to restart DBCTL automatically. However, it will attempt to reconnect to DBCTL in the normal way.

User response:

It may be necessary to restart DBCTL manually.

Destination:

Console

Modules:

DFHDBCT

XMEOUT Parameters: applid, xxxxxxxx, X'nn'

DFHDX8325
applid Restart command issued unsuccessfully to subsysid for reason X'xx' X'yy'.
Explanation:

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'.

System action:

The active CICS continues normally and will attempt to reconnect to DBCTL.

User response:

It may be necessary to restart DBCTL manually.

Destination:

Console

Modules:

DFHDBCT

XMEOUT Parameters: applid, subsysid, X'xx', X'yy'

DFHDX8326
applid DBCTL state message lost owing to message services error.
Explanation:

The active CICS system was unable to report a change of DBCTL connection status to the alternate.

System action:

The active system writes an error entry in its CAVM status record, but otherwise continues normally.

User response:

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.

Destination:

Console

Modules:

DFHDBCT

XMEOUT Parameter: applid

DFHDX8327
applid DBCTL state message lost owing to CAVM services failure.
Explanation:

The active CICS system was unable to report a change of DBCTL connection status to the overseer.

System action:

Processing continues.

User response:

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.

Destination:

Console

Modules:

DFHDBCT

XMEOUT Parameter: applid

DFHDX8328
applid Unable to determine Jes affiliation of (jobname, jobid).
Explanation:

CICS can offer full XRF support only if the DBCTL to which it is connected is running under the same JES as CICS itself.

System action:

The active CICS continues, but, in the event of failure, CICS will not attempt to restart DBCTL automatically.

User response:

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.

Destination:

Console

Modules:

DFHDBCT

XMEOUT Parameters: applid, jobname,jobid

DFHDX8329
applid Restart request after DBCTL failure ignored for reason X'nn'.
Explanation:

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.

nn
Meaning
X'09'
There is no alternate DBCTL to be restarted.
X'10'
Possibly, the DBCTL subsystem is under a different JES from the active CICS system.
X'11'
The DBCTL subsystem was an IMS DB/DC system.
System action:

The active CICS continues as if the user exit had indicated ‘no action’.

User response:

Check that the user exit is performing as intended and that the CICS and DBCTL systems have been set up with the correct options.

Destination:

Console

Modules:

DFHDBCT

XMEOUT Parameters: applid, X'nn'

DFHDX8330
applid IMS DB/DC region has requested XRF support.
Explanation:

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.

System action:

The system continues to run without XRF.

User response:

Either enable IMS/DC for XRF, or remove SSID from RST.

Destination:

Console

Modules:

DFHDBCT

XMEOUT Parameter: applid

DFHDX8331
applid CAVM message input service error xxxxxxxx, X'nn', xxxxxxxx.
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHDBCR

XMEOUT Parameters: applid, xxxxxxxx, X'nn', xxxxxxxx

DFHDX8332I
applid Connection to xxxxxxxx notified after xxxxxxxx failure initiated takeover.
Explanation:

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.

System action:

The takeover continues. If the message is a notification of a successful connection, then the global user exit XXDTO may be driven.

User response:

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.

Destination:

Console

Modules:

DFHDBCR

XMEOUT Parameters: applid, xxxxxxxx, xxxxxxxx

DFHDX8333
applid Unrecognized message type xxxxxxxx received by DBCTL tracking task.
Explanation:

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.

System action:

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.

User response:

In the event of a takeover it may be necessary to restart DBCTL manually.

Destination:

Console

Modules:

DFHDXCU

XMEOUT Parameters: applid, xxxxxxxx

DFHDX8334
applid Error detected in xxxxxxxx for reason nn.
Explanation:

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.

nn
Meaning
01
The CICS SVC detected an error in the RST. Refer to the accompanying DFHXG64xx or DFHXA65xx message for the reason for the error.
02
The RST could not be loaded by the XRF/DBCTL tracking task, or the XRF/DBCT tracking task detected that the RST was invalid.
03
The CICS SVC detected an error in the RST during initialization. Refer to the accompanying DFHXG64xx or DFHXA65xx message for the reason for the error.
04
The CICS SVC detected an error in the RST during connect time. Refer to the accompanying DFHXG64xx or DFHXA65xx message for the reason for the error.
System action:

The tracking transaction continues as if no XRF support had been requested via the RST for the connected DBCTL.

User response:

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.

Destination:

Console

Modules:

DFHDBCR

XMEOUT Parameters: applid, xxxxxxxx, nn

DFHDX8335
applid Unable to complete search for DBCTL alternate.
Explanation:

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.

System action:

The tracking transaction continues as if no DBCTL alternate had been found. An ADMD transaction dump will be produced.

User response:

In the event of a takeover it may be necessary to restart DBCTL manually.

Destination:

Console

Modules:

DFHDBCR

XMEOUT Parameter: applid

DFHDX8336
applid Unable to provide DBCTL/XRF support for reason: X'nn'.
Explanation:

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.

nn
Meaning
X'46'
No valid RST was found. Refer to DFHDX8334.
X'50'
DBCTL subsystem is an IMS DB/DC system.
X'51'
There is no alternate DBCTL to be restarted.
X'52'
The DBCTL subsystem is, or may be, under a different JES from the active CICS system.
X'53'
The active CICS system has already attempted a restart of DBCTL.
System action:

The alternate CICS continues as if the user exit had indicated ‘no action’.

User response:

Check that the user exit is performing as intended and that the CICS and DBCTL systems have been set up with the correct options.

Destination:

Console

Modules:

DFHDBCR

XMEOUT Parameters: applid, X'nn'

DFHDX8337
applid Takeover request rejected by CAVM, reason code X'nn'.
Explanation:

The user exit XXDFB requested a takeover as a result of a DBCTL failure, but the CAVM rejected the takeover request.

System action:

The alternate CICS continues as if the user exit had indicated ‘no action’.

User response:

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.

Destination:

Console

Modules:

DFHDBCR

XMEOUT Parameters: applid, X'nn'

DFHDX8338
applid Unable to issue command command to subsysid for reason X'nn'.
Explanation:

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.

nn
Meaning
X'09'
MVS GETMAIN failure
X'10'
MVS ATTACH failure.
System action:

The takeover continues.

User response:

Restart the DBCTL subsystem manually.

Destination:

Console

Modules:

DFHDBCR

XMEOUT Parameters: applid, command,subsysid, X'nn'

DFHDX8339
applid command command issued unsuccessfully to subsysid for reason X'nn'.
Explanation:

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.

System action:

The takeover continues.

User response:

Restart the DBCTL subsystem manually.

Destination:

Console

Modules:

DFHDBCR

XMEOUT Parameters: applid, command,subsysid, X'nn'

DFHDX8340
applid DBCTL tracking task started in an invalid environment reason X'nn'.
Explanation:

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.

nn
Meaning
X'65'
XRF=NO specified in the SIT.
X'67'
CICS system is running as active.
X'69'
MVS GETMAIN failure.
System action:

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.

User response:

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.

Destination:

Console

Modules:

DFHDBCR

XMEOUT Parameters: applid, X'nn'

DFHDX8341I
applid Takeover request accepted.
Explanation:

The DBCTL/XRF tracking task issued a takeover request due to a request from user exit XXDFB. The request has been accepted.

System action:

The takeover continues.

User response:

None. You can suppress this message with the system initialization parameter MSGLVL = 0.

Destination:

Console

Modules:

DFHDBCR

XMEOUT Parameter: applid

DFHDX8342I
applid Restart command issued successfully.
Explanation:

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.

System action:

Takeover continues.

User response:

None. You can suppress this message with the system initialization parameter MSGLVL = 0.

Destination:

Console

Modules:

DFHDBCR

XMEOUT Parameter: applid

[[ Contents Previous Page | Next Page Index ]]