DFHDBxxxx messages

Start of changeThe DFHDBxxxx messages are issued by the CICS-DB2 and CICS-DBCTL interfaces. Messages for the CICS-DB2 interface are in the range 2000-2999.End of change

Start of changeCICS-DB2 messages that are documented to be output to transient data destination CDB2, are in fact output to whatever destinations are specified in the MSGQUEUE1, MSGQUEUE2 and MSGQUEUE3 parameters of the DB2CONN. MSGQUEUE1 must be specified, and its default is CDB2.End of change Start of changeThis manual documents the default destination.End of change

DFHDB2001
date time applid CICS-DB2 resynchronization with db2id for unit of work X'uowid' cannot take place due to initial start of CICS.
Explanation:

CICS cannot resolve the disposition of unit of work (UOW) uowid that DB2 subsystem db2id holds from a previous connection because CICS was initial started. Start of changeA CICS initial start should be avoided when resynchronization is outstanding. CICS cold, warm and emergency starts do not affect resynchronization, which occurs automatically when CICS and DB2 are connected.End of change

System action:

The CICS is connected to DB2 but UOW uowid will remain indoubt in DB2.

User response:

The UOW uowid will have to be resolved manually using DB2 -DISPLAY THREAD and -RECOVER INDOUBT operator commands.

Destination:

Console and Transient Data Queue CDB2

Modules:

DFHD2EX1

XMEOUT Parameters: date, time,applid, db2id, X'uowid'

Start of changeDFHDB2003End of change
Start of changedate time applid The CICS-DB2 attachment facility is already active.End of change
Start of change
Explanation:

The CICS-DB2 attachment is already active and enabled to CICS.

End of change
Start of change
System action:

The CICS-DB2 attachment facility initialization does not complete.

End of change
Start of change
User response:

Only one CICS-DB2 attachment facility may be active in a CICS region.

End of change
Start of change
Destination:

CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2STREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHDB2004End of change
Start of changedate time applid No threads were found for plan plan-nameEnd of change
Start of change
Explanation:

This message is in response to a CICS-DB2 attachment facility DSNC DISPLAY or DISCONNECT command. No threads were found using the specified plan name plan-name. The plan-name may be blank if a specific plan was not requested.

End of change
Start of change
System action:

The CICS-DB2 attachment facility command is not processed.

End of change
Start of change
User response:

Reenter the command with the correct plan name.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CCEnd of change

Start of changeDFHDB2005End of change
Start of changedate time applid RCT does not contain transaction tranEnd of change
Start of change
Explanation:

This message is in response to a CICS-DB2 attachment facility DSNC DISPLAY or MODIFY command. The transaction tran specified in the command was not found in the RCT. That is, there was no DB2TRAN defined for the transid, or the DB2TRAN referred to a DB2ENTRY that does not exist, or the case of the DISPLAY command, no threads were found for the transaction.

End of change
Start of change
System action:

The CICS-DB2 attachment facility command is not processed.

End of change
Start of change
User response:

Reenter the command with the correct transaction name.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2006End of change
Start of changedate time applid The dest destination ID is invalid.End of change
Start of change
Explanation:

This message is in response to a CICS-DB2 attachment facility DSNC MODIFY DESTINATION command. The destination ID dest specified on the command to be modified is not one of the destinations currently defined in the DB2CONN as a message queue.

End of change
Start of change
System action:

The CICS-DB2 attachment facility command is not processed.

End of change
Start of change
User response:

Reenter the command with the correct destination ID.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2007End of change
Start of changedate time applid The command verb is missing or invalid.End of change
Start of change
Explanation:

The CICS-DB2 attachment facility does not recognize the verb entered on the DSNC command.

End of change
Start of change
System action:

The command is not processed.

End of change
Start of change
User response:

Reenter the command with the correct syntax.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2008End of change
Start of changedate time applid Keyword missing or invalid.End of change
Start of change
Explanation:

The CICS-DB2 attachment facility DSNC command contains an unknown positional keyword or a keyword is missing.

End of change
Start of change
System action:

The command is not processed.

End of change
Start of change
User response:

Reenter the command with the correct syntax.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2009End of change
Start of changedate time applid The value in the command is invalid.End of change
Start of change
Explanation:

The numeric value in the DSNC modify command is invalid. The error is caused by one of the following:

End of change
Start of change
System action:

The CICS-DB2 attachment facility command is not processed.

End of change
Start of change
User response:

Reenter the command with a correct value.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2010End of change
Start of changedate time applid tranid Transaction abended because DB2 thread tcbs are unavailable.End of change
Start of change
Explanation:

The transaction was abnormally terminated because a DB2 thread TCB was not available on which to create a thread for the transaction.

End of change
Start of change
System action:

The transaction is abnormally terminated.

End of change
Start of change
User response:

Determine if more subtask TCBs should be made available to the CICS-DB2 connection by increasing the TCBLIMIT value of the DB2CONN. The TCBLIMIT value can be altered using a SET DB2CONN command.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranidEnd of change

Start of changeDFHDB2011End of change
Start of changedate time applid tranid Transaction abended because threads are unavailable for resource resnameEnd of change
Start of change
Explanation:

The transaction was abnormally terminated because a thread connection to DB2 was not available for the transaction. Resname identifies the name of the DB2ENTRY or the POOL from which the thread was to be allocated. This error can occur when:

End of change
Start of change
System action:

The transaction is abnormally terminated.

End of change
Start of change
User response:

Determine if more threads can be made available to the DB2ENTRY or the POOL by increasing the THREADLIMIT value on the DB2ENTRY or the DB2CONN respectively. The THREADLIMIT value can be increased using SET DB2ENTRY and SET DB2CONN commands.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changeresnameEnd of change

Start of changeDFHDB2012End of change
Start of changedate time applid Stop quiesce of the CICS-DB2 attachment facility from DB2 subsystem db2-id is proceeding.End of change
Start of change
Explanation:

A DSNC STOP command entered by the master terminal operator is being processed. CICS is disconnected from DB2 subsystem db2-id. When the disconnect is complete message DFHDB2025 is output to the terminal.

End of change
Start of change
System action:

New CICS transactions attempting to issue SQL commands is abended or receives a negative SQL reason code dependent on the CONNECTERROR setting in the DB2CONN definition.

Existing transactions using the CICS-DB2 interface are allowed to complete before the CICS-DB2 attachment facility is stopped.

End of change
Start of change
User response:

If the quiesce is not completed within an acceptable time period, a DSNC STOP FORCE command should be issued from another terminal.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2013End of change
Start of changedate time applid Display report follows for threads accessing DB2 db2-idEnd of change
Start of change
Explanation:

A CICS-DB2 attachment display plan or display tran command was requested and the results follow this message. If not blank, db2-id is the name of the DB2 subsystem involved.

The following information is displayed for each thread:

DB2ENTRY
The name of the DB2ENTRY which contains the thread.
S
The thread status:
*
The thread is active within a unit of work and is currently executing in DB2.
A
The thread is active within a unit of work but is not currently executing in DB2.
I
The thread is inactive. It is a protected thread waiting for new work.
PLAN
The current plan name.
PRI-AUTH
The DB2 primary authorization ID.
SEC-AUTH
The DB2 secondary authorization ID.
CORRELATION
The DB2 thread correlation ID.

For active threads only:

TRAN
The CICS transaction ID.
TASK
The CICS task number.
UOW-ID
The CICS unit-of-work ID.
End of change
Start of change
System action:

Processing continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2CCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedb2-idEnd of change

Start of changeDFHDB2014End of change
Start of changedate time applid Statistics report follows for db2conn-name accessing DB2 db2-idEnd of change
Start of change
Explanation:

A CICS-DB2 attachment facility statistics display was requested and follows this message. The name of the DB2CONN that is currently in use is db2conn-name and db2-id, if not blank, is the name of the DB2 subsystem involved.

The statistics displayed are those that have been accumulated after the expiry of the last statistics collection interval, end of day expiry, or requested reset. These statistics represent a subset of those available as CICS-DB2 Global and resource statistics collected via the CICS statistics spi commands.

The following information is displayed for each DB2ENTRY and for the command and pool sections of the DB2CONN:

End of change
Start of change
System action:

Processing continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2CCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedb2conn-name, End of changeStart of changedb2-idEnd of change

Start of changeDFHDB2015End of change
Start of changedate time applid The CICS-DB2 attachment facility is in standby for DB2 subsystem db2-idEnd of change
Start of change
Explanation:

The CICS-DB2 attachment facility has dropped into standby mode because DB2 subsystem db2-id has stopped and STANDBYMODE=RECONNECT was specified in the DB2CONN.

End of change
Start of change
System action:

The CICS-DB2 attachment facility waits for the DB2 subsystem to become active again, at which time it automatically reconnects. While in standby mode, all SQL requests receive a negative SQLCODE or an AEY9 abend depending on whether CONNECTERROR=SQLCODE or CONNECTERROR=ABEND was specified in the DB2CONN.

End of change
Start of change
User response:

Notify the system programmer.

End of change
Start of change
Destination:

Console and Transient Data Queue CDB2

End of change
Modules:

Start of changeDFHD2TMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedb2-idEnd of change

Start of changeDFHDB2016End of change
Start of changedate time applid The connection of CICS to DB2 {subsystem | group} db2-id failed with reason X'reason-code'.End of change
Start of change
Explanation:

The CICS-DB2 attachment facility startup cannot complete because an error occurred while connecting to DB2 sub-system or group db2-id. The response from DB2 was reason-code.

End of change
Start of change
System action:

The CICS-DB2 attachment facility initialization does not complete.

End of change
Start of change
User response:

Analyze the DB2 reason code given and any prior messages issued to the attachment error destination or CDB2 TS queues to determine the source of the error. Some possible causes include:

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2STR, DFHD2CM1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=subsystem, End of changeStart of change2=group}, End of changeStart of changedb2-id, End of changeStart of changeX'End of changeStart of changereason-codeEnd of changeStart of change'End of change

Start of changeDFHDB2018End of change
Start of changedate time applid db2-id DB2 {subsystem is not active. | group has no active members.}End of change
Start of change
Explanation:

The CICS-DB2 attachment facility startup cannot complete because the db2-id group or subsystem is not active.

End of change
Start of change
System action:

The CICS-DB2 attachment facility stops.

End of change
Start of change
User response:

Restart the CICS-DB2 attachment facility after starting DB2.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2STR, DFHD2CM1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedb2-id, End of changeStart of change{1=subsystem is not active., End of changeStart of change2=group has no active members.}End of change

DFHDB2019
date time applid The modify command is complete.
Explanation:

Start of changeThe DSNC MODIFY command completed successfully.End of change

System action:

Processing continues.

User response:

None.

Destination:

Terminal End User

Modules:

DFHD2CM1

Start of changeDFHDB2020End of change
Start of changedate time applid The display command is complete.End of change
Start of change
Explanation:

The DSNC DISPLAY command completed successfully.

End of change
Start of change
System action:

Processing continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2CCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHDB2021End of change
Start of changedate time applid The disconnect command is complete.End of change
Start of change
Explanation:

The DSNC DISCONNECT command completed successfully.

End of change
Start of change
System action:

Processing continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CCEnd of change

Start of changeDFHDB2022End of change
Start of changedate time applid Stop force of the CICS-DB2 attachment facility from db2-id is proceeding.End of change
Start of change
Explanation:

A DSNC STOP FORCE command entered by the master terminal operator is being processed. CICS will be disconnected from DB2 subsystem db2-id. When the disconnect is complete, message DFHDB2025 is output to the terminal.

End of change
Start of change
System action:

New CICS transactions attempting to issue SQL commands are abended or receive a negative SQL reason code dependent upon the CONNECTERROR setting in the DB2CONN definition.

Existing transactions using the CICS-DB2 interface will be force purged.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2023IEnd of change
Start of changedate time applid The CICS-DB2 attachment has connected to DB2 subsystem db2-id{ | group }db2-groupEnd of change
Start of change
Explanation:

The CICS-DB2 attachment facility startup has successfully connected to DB2 subsystem db2-id group db2-group

End of change
Start of change
System action:

The CICS-DB2 attachment facility is active.

End of change
Start of change
User response:

If a group name does not appear then group attach is not active. You can suppress this message with the SIT parameter, MSGLVL = 0.

End of change
Start of change
Destination:

Console and Transient Data Queue CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2STR, DFHD2CM1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedb2-id, End of changeStart of change{1= , End of changeStart of change2= group }, End of changeStart of changedb2-groupEnd of change

Start of changeDFHDB2024IEnd of change
Start of changedate time applid The CICS-DB2 attachment is in standby. For resync purposes only, connection has been made to DB2 restart-light subsystem db2-id{ | group }db2-groupEnd of change
Start of change
Explanation:

The CICS-DB2 attachment facility startup has temporarily connected to DB2 subsystem db2-id group db2-group. The DB2 subsystem is running in restart-light mode and connection has been made purely to allow resynchronisation to take place.

End of change
Start of change
System action:

The CICS-DB2 attachment facility remains in standby for new work, but allows resynchronisation tasks to complete. The DB2 restart-light subsystem is terminated when resynchronisation is complete. If STANDBYMODE(RECONNECT) has been specified in the DB2CONN definition and when the DB2 restart-light subsystem is terminated, the CICS-DB2 attachment facility reverts to standbymode and connection to another active DB2 subsystem is made.

End of change
Start of change
User response:

If a group name does not appear, group attach is not active. You can suppress this message with the SIT parameter, MSGLVL = 0.

End of change
Start of change
Destination:

Console and Transient Data Queue CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2STR, DFHD2CM1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedb2-id, End of changeStart of change{1= , End of changeStart of change2= group }, End of changeStart of changedb2-groupEnd of change

Start of changeDFHDB2025IEnd of change
Start of changedate time applid The CICS-DB2 attachment has disconnected from DB2 subsystem db2-id{ | group }db2-groupEnd of change
Start of change
Explanation:

The CICS-DB2 attachment facility has successfully disconnected from DB2 db2-id subsystem group db2-group

End of change
Start of change
System action:

The CICS-DB2 attachment facility is inactive.

End of change
Start of change
User response:

If a group name does not appear then group attach was not being used. You can suppress this message with the SIT parameter, MSGLVL = 0.

End of change
Start of change
Destination:

Console and Transient Data Queue CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2STP, DFHD2CM1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedb2-id, End of changeStart of change{1= , End of changeStart of change2= group }, End of changeStart of changedb2-groupEnd of change

Start of changeDFHDB2027End of change
Start of changedate time applid CICS-DB2 attachment is shutting down. DSNC DB2 commands may not be entered.End of change
Start of change
Explanation:

The CICS-DB2 attachment facility cannot accept commands directed to DB2 during or after the termination of the CICS-DB2 attachment facility.

End of change
Start of change
System action:

The command is rejected.

End of change
Start of change
User response:

Issue the command via the DB2 console instead.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2028End of change
Start of changedate time applid The user is not authorized to issue DB2 commands via DSNC.End of change
Start of change
Explanation:

DB2 rejected the command request during sign-on of the user. Therefore, the user is assumed not to be authorized for the requested function in the command.

End of change
Start of change
System action:

The command is rejected.

End of change
Start of change
User response:

Notify the system programmer.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2029End of change
Start of changedate time applid tranid DB2 command failed with IFCARC1=rc, IFCARC2=X'reason-code'End of change
Start of change
Explanation:

The DB2 command submitted by transaction received IFI return code rc and reason code reason-code

End of change
Start of change
System action:

The command processing stops.

End of change
Start of change
User response:

Refer to the DB2 Messages and Codes for a description of the rc and reason-code.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changerc, End of changeStart of changeX'reason-codeEnd of changeStart of change'End of change

Start of changeDFHDB2031End of change
Start of changedate time applid CICS-DB2 command is invalid. No DB2CONN is installed.End of change
Start of change
Explanation:

A DSNC command cannot be executed as there is no DB2CONN installed. For all DSNC commands (including the STRT command) a DB2CONN definition must be installed before issuing the command. CICS no longer supports running with a macro RCT. All macro RCTs should be migrated to the CSD and the resulting definitions installed before attempting to startup the CICS-DB2 Attachment Facility.

Likewise a CEMT or EXEC CICS SET DB2CONN CONNECTED command cannot be issued to startup the CICS-DB2 Attachment Facility if no DB2CONN definition is installed.

End of change
Start of change
System action:

The command is rejected.

End of change
Start of change
User response:

Install the necessary DB2CONN. The command can then be re-issued.

End of change
Start of change
Destination:

CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2CM1, DFHD2STREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHDB2032End of change
Start of changedate time applid Alternate destination display command complete.End of change
Start of change
Explanation:

The DSNC DISPLAY command to an alternate destination is complete. The output should be available at the requested destination.

End of change
Start of change
System action:

Processing continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2CCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHDB2033End of change
Start of changeapplid Terminal termid is not supported by BMS or is invalid.End of change
Start of change
Explanation:

This message is issued in response to a CICS-DB2 attachment facility command, or DB2 command that requested an alternative destination for the response. CICS basic mapping support (BMS) encountered an error while routing to the requested terminal named termid.

End of change
Start of change
System action:

Output from the command may be suppressed.

End of change
Start of change
User response:

Ensure that the terminal ID was correctly entered. Otherwise notify the system programmer. This message may occur if the destination device is not supported by BMS, or is not defined to CICS.

End of change
Start of change
Destination:

Console and Terminal End User

End of change
Modules:

Start of changeDFHD2CCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changetermidEnd of change

Start of changeDFHDB2035End of change
Start of changedate time applid Indoubt resolution for Unit of Work X'uowid' is incomplete for DB2 subsystem db2idEnd of change
Start of change
Explanation:

CICS indicates that recovery should not be required for uowid but DB2 subsystem db2id is indoubt.

End of change
Start of change
System action:

The CICS is connected to DB2 but the UOW remains indoubt in DB2.

End of change
Start of change
User response:

The indoubt UOW will have to be resolved manually using DB2 -DISPLAY THREAD and -RECOVER INDOUBT operator commands. You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console and Transient Data Queue CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changeuowid', End of changeStart of changedb2idEnd of change

Start of changeDFHDB2037End of change
Start of changedate time applid DB2 {subsystem |group} db2-id{is not active. | has no active members.} The CICS-DB2 attachment facility is waiting.End of change
Start of change
Explanation:

The CICS-DB2 attachment facility is waiting for notification from DB2. For a DB2 group no active sub-systems have been found. If a DB2 sub-system was specified then that sub-system is not active. The CICS-DB2 attachment facility completes initialization after either

has been started.

End of change
Start of change
User response:

Notify the system programmer that a DB2 subsystem requires to be started according to the information supplied.

End of change
Start of change
Destination:

Console and Transient Data Queue CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2STR,DFHD2CM1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=subsystem, End of changeStart of change2=group}, End of changeStart of changedb2-id, End of changeStart of change{1= is not active. ,End of changeStart of change2= has no active members.}End of change

Start of changeDFHDB2038End of change
Start of changedate time applid The command is invalid while waiting for db2idEnd of change
Start of change
Explanation:

The CICS-DB2 attachment facility cannot accept commands directed to DB2 while it is waiting for the DB2 subsystem to start. The name of the DB2 subsystem that is not yet operational is db2id.

End of change
Start of change
System action:

The command is rejected.

End of change
Start of change
User response:

Re-issue the command when DB2 has been started and the attachment facility has connected to DB2.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2039End of change
Start of changedate time applid The error destinations are: dest1 dest2 dest3.End of change
Start of change
Explanation:

This message is in response to a CICS-DB2 attachment facility DSNC MODIFY DESTINATION command and lists the currently active message destinations known to the attachment facility. Null entries show as '****' and can be modified so they identify actual destinations.

End of change
Start of change
System action:

Processing continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2040End of change
Start of changedate time applid tranid Module modname could not be found.End of change
Start of change
Explanation:

During CICS-DB2 attachment facility initialization, an attempt was made to locate and load the named module, but it was not found in any of the libraries accessible to MVS through the MVS LOAD macro.

End of change
Start of change
System action:

CICS-DB2 attachment facility initialization does not complete.

End of change
Start of change
User response:

Check the CICS JOBLIB/STEPLIB and ensure that the required DB2 library is defined there and contains the named module. Alternatively, ensure the required DB2 library is in the MVS linklist.

End of change
Start of change
Destination:

CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2STREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changemodnameEnd of change

Start of changeDFHDB2041End of change
Start of changedate time applid No active threads found.End of change
Start of change
Explanation:

A DSNC DISPLAY TRANSACTION or DSNC DISPLAY PLAN command was entered, but there were no active threads found. The CICS-DB2 attachment facility might have identified and signed on some subtasks, but a create thread was not issued for any of the subtasks. Likewise, threads may have been created previously on the subtasks but were subsequently terminated when there were no more DB2 requests to service.

End of change
Start of change
System action:

Processing continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CCEnd of change

Start of changeDFHDB2042End of change
Start of changedate time applid Connection not authorized to db2-idEnd of change
Start of change
Explanation:

The attempt to connect to the db2-id DB2 subsystem or group failed because the user was not authorized to access DB2. Authorization was denied by either RACF or a user-written connection exit.

End of change
Start of change
System action:

The CICS-DB2 attachment does not connect to DB2.

End of change
Start of change
User response:

The userid specified on the CICS job was not authorized to connect to the named DB2 subsystem or group. Refer to the DB2 Administration Guide and the CICS DB2 Guide for information on how to authorize a user to access DB2.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2STREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedb2-idEnd of change

Start of changeDFHDB2044End of change
Start of changedate time applid Authorization parameters for resname have been corrupted.End of change
Start of change
Explanation:

THe CICS-DB2 attachment facility detected that the AUTHTYPE or AUTHID parameters for resname have been corrupted since it was last installed or updated by a SET command. Resname is the name of the DB2ENTRY involved, or it is set to 'POOL' or 'COMMAND' if it is the pool or command thread authorizations of the DB2CONN that are involved.

End of change
Start of change
System action:

The transaction is abnormally terminated.

End of change
Start of change
User response:

If it is a DB2ENTRY involved, the DB2ENTRY needs to be reinstalled, or the AUTHID or AUTHTYPE parameters reset using a SET command to make the DB2ENTRY usable.

For pool or command thread authorizations, a SET DB2CONN command needs to be issued to reset the AUTHID or AUTHTYPE parameters, or the DB2CONN needs to be reinstalled. Note however that a DB2CONN cannot be re-installed without stopping the CICS-DB2 attachment facility first.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeresnameEnd of change

Start of changeDFHDB2045End of change
Start of changedate time applid Resource Manager rmi-name is unknown to the CICS-DB2 Attachment facility.End of change
Start of change
Explanation:

The CICS-DB2 Attachment facility received a request for a resource manager with entryname rmi-name. This resource name is not known by the CICS-DB2 attachment facility.

End of change
Start of change
System action:

The transaction is abnormally terminated with abend code AD21. A CICS system dump is taken.

End of change
Start of change
User response:

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

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changermi-nameEnd of change

Start of changeDFHDB2047IEnd of change
Start of changedate time applid The CICS-DB2 Attachment cannot find DB2 {subsystem | group} idEnd of change
Start of change
Explanation:

The CICS-DB2 attachment facility failed to connect because the DB2ID or DB2GROUPID id cannot be found.

End of change
Start of change
System action:

The CICS-DB2 attachment facility is inactive.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Console and Transient Data Queue CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2STREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of change{1=subsystem, End of changeStart of change2=group}, End of changeStart of changeidEnd of change

Start of changeDFHDB2048End of change
Start of changedate time applid Unable to interpret SQL call while formatting an EDF display for transaction transid task taskidEnd of change
Start of change
Explanation:

The CICS attachment facility was unable to call its EDF processor DFHD2EDF or the CICS attachment facility was unable to decipher storage associated with an SQL statement for CICS transaction transid and task taskid. Either the SQL communications area (SQLCA) or the RDS input parameter list (RDI) storage could not be interpreted by the CICS-DB2 attachment facility.

End of change
Start of change
System action:

If the CICS attachment facility was unable to call its EDF processor DFHD2EDF and a transaction dump is taken with dump code AD29.

If DFHD2EDF was called but it was unable to decipher storage, a transaction dump of the storage in question is taken with dump code AD22.

End of change
Start of change
User response:

For an AD29 dump, analyze the trace in the CICS transaction dump to determine why the call to DFHD2EDF failed. For an AD22 dump, analyze the CICS transaction dump of the storage in question. In this situation the information supplied by the Execution Diagnostic Facility (EDF) of CICS for SQL statements consists of:

No other information is provided about the SQL statement.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetransid, End of changeStart of changetaskidEnd of change

Start of changeDFHDB2049End of change
Start of changedate time applid CICS-DB2 resynchronization for db2-id Unit of Work X'uowid' failed with reason code X'reason-code'End of change
Start of change
Explanation:

A resolve indoubt request passed to DB2 from CICS for Unit of Work uowid failed with DB2 reason code reason-code. The DB2 subsystem involved is db2id.

End of change
Start of change
System action:

The UOW remains indoubt in DB2 and CICS keeps hold of the UOW disposition. A CICS system dump is taken with dumpcode 00C30003.

End of change
Start of change
User response:

Use the reason code to determine why the resolve indoubt request failed.

End of change
Start of change
Destination:

Console and Transient Data Queue CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedb2-id, End of changeStart of changeX'End of changeStart of changeuowid', End of changeStart of changeX'reason-codeEnd of changeStart of change'End of change

Start of changeDFHDB2050End of change
Start of changedate time applid tranid termid Abend abcode has occurred in dynamic plan exit program prognameEnd of change
Start of change
Explanation:

Dynamic plan exit program progname has abnormally terminated with abend code abcode.

End of change
Start of change
System action:

Normal transaction abend processing continues.

End of change
Start of change
User response:

See the description of abend code abcode for further guidance.

If the code is not a CICS transaction abend code, it is a user abend code. Request an explanation from the programmer responsible for this area.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changetermid, End of changeStart of changeabcode, End of changeStart of changeprognameEnd of change

Start of changeDFHDB2051End of change
Start of changedate time applid tranid termid Abend abcode in DFHD2EX1 - Dynamic plan exit program progname must be AMODE 31.End of change
Start of change
Explanation:

The CICS-DB2 attachment facility has failed to link to dynamic plan exit program progname because it is not link edited AMODE 31.

End of change
Start of change
System action:

Normal transaction abend processing continues.

End of change
Start of change
User response:

Relinkedit the dynamic plan exit program AMODE 31.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changetermid, End of changeStart of changeabcode, End of changeStart of changeprognameEnd of change

Start of changeDFHDB2053End of change
Start of changedate time applid tranid termid Abend abcode in DFHD2EX1 - Dynamic plan exit program progname is disabled.End of change
Start of change
Explanation:

The CICS-DB2 attachment facility has failed to link to dynamic plan exit program progname because it is disabled.

End of change
Start of change
System action:

Normal transaction abend processing continues.

End of change
Start of change
User response:

Enable the dynamic plan exit program.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changetermid, End of changeStart of changeabcode, End of changeStart of changeprognameEnd of change

Start of changeDFHDB2054End of change
Start of changedate time applid tranid termid Abend abcode in DFHD2EX1 - Link to the dynamic plan exit progname failed.End of change
Start of change
Explanation:

An unexpected return code was returned from the link to the dynamic plan exit program progname by the CICS-DB2 attachment facility.

End of change
Start of change
System action:

Normal transaction abend processing continues.

End of change
Start of change
User response:

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

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changetermid, End of changeStart of changeabcode, End of changeStart of changeprognameEnd of change

Start of changeDFHDB2055End of change
Start of changedate time applid Single phase commit failed with reason code X'reason-code' for transaction transid task taskidEnd of change
Start of change
Explanation:

CICS requested a single-phase commit from DB2, but DB2 was unable to comply. The request failed with DB2 reason code reason-code.

End of change
Start of change
System action:

The CICS-DB2 attachment facility abnormally terminates the transaction with abend code AD2W. CICS recovery manager will supersede the AD2W abend code with abend code ASPR.

End of change
Start of change
User response:

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

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changereason-code', End of changeStart of changetransid,End of changeStart of changetaskidEnd of change

Start of changeDFHDB2057End of change
Start of changedate time applid tranid termid Abend abcode in DFHD2EX1 - PPT entry for dynamic plan exit program progname was not found.End of change
Start of change
Explanation:

CICS was unable to find a PPT entry for the dynamic plan exit program progname.

End of change
Start of change
System action:

Normal transaction abend processing continues.

End of change
Start of change
User response:

Ensure that the dynamic plan exit program progname has been correctly defined to CICS.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changetermid, End of changeStart of changeabcode, End of changeStart of changeprognameEnd of change

Start of changeDFHDB2058End of change
Start of changedate time applid tranid termid Abend abcode in DFHD2EX1 - Fetch for dynamic plan exit program progname failed.End of change
Start of change
Explanation:

CICS was unable to load the dynamic plan exit program progname.

End of change
Start of change
System action:

Normal transaction abend processing continues.

End of change
Start of change
User response:

Ensure that the dynamic plan exit program progname has been correctly defined and is in a load library accessible to CICS.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changetermid, End of changeStart of changeabcode, End of changeStart of changeprognameEnd of change

Start of changeDFHDB2061End of change
Start of changedate time applid The INITPARM specified for the CICS-DB2 attachment is invalid. The attachment facility cannot start.End of change
Start of change
Explanation:

The initparm for the CICS-DB2 attachment facility is not in the correct format. The format of the INITPARM should be:

    INITPARM=(DFHD2INI='yyyy')

where yyyy is a one to four character DB2 subsystem id. CICS no longer supports running with a macro RCT, so an RCT suffix should not be specified in the initparm string.

End of change
Start of change
System action:

The CICS-DB2 attachment facility initialization does not complete.

End of change
Start of change
User response:

Correct the INITPARM and restart the CICS region, or specify a DB2 subsystem id on a DSNC STRT command or in the DB2CONN. INITPARM is only used when the DB2CONN definition does not contain a DB2ID and a DB2ID is not specified on the startup command.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2STR, DFHD2CM1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHDB2063End of change
Start of changedate time applid Authorization failure starting the CICS-DB2 attachment with RESP=xxxx and RESP2=yyyyEnd of change
Start of change
Explanation:

An authorization error occurred when starting the CICS-DB2 attachment. The SET DB2CONN CONNECTED responses for RESP (xxxx) and RESP2 (yyyy) indicate the specific error.

End of change
Start of change
System action:

The CICS-DB2 attachment initialization does not complete.

End of change
Start of change
User response:

Ensure that the DSNC transaction definition in group DFHDB2 is the installed definition.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changexxxx, End of changeStart of changeyyyyEnd of change

Start of changeDFHDB2064End of change
Start of changedate time applid Resynchronization outstanding for subsystem db2id after DB2 Group Attach has connected to subsystem db2id2End of change
Start of change
Explanation:

CICS indicates that resynchronization is outstanding for subsystem db2id after DB2 Group Attach has connected to subsystem db2id2.

End of change
Start of change
System action:

The CICS is connected to DB2 subsystem db2id but UOWs remain outstanding for DB2 subsystem db2id2.

End of change
Start of change
User response:

The DB2CONN definition either has RESYNCMEMBER(NO) specified, or RESYNCMEMBER(YES) is specified but CICS detected that all the UOWs outstanding are shunted indoubt meaning that resynchronisation with DB2 cannot take place immediately. Both these situations allow group attach to proceed, and the result is CICS has connected to a different DB2 subsystem than previously. The user must manually reconnect to the original DB2 subsystem which automatically resynchronizes the outstanding (non shunted) units of work. Shunted units of work wait to be unshunted at which point resynchronisation takes place if CICS is connected to the original DB2 subsystem.

End of change
Start of change
Destination:

Console and Transient Data Queue CDB2

End of change
Modules:

Start of changeDFHD2STREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changedb2id, End of changeStart of changedb2id2End of change

Start of changeDFHDB2065End of change
Start of change INVALID LENGTH. DATA NOT DISPLAYABLE.End of change
Start of change
Explanation:

The module running under the CICS Execution Diagnostic Facility (EDF) attempted to display an input or output variable that had an incorrect length indicator.

End of change
Start of change
System action:

EDF processing continues, but the value of the variable is not displayed.

End of change
Start of change
User response:

Examine the SQL statement in the application program.

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

Terminal End User

End of change
Modules:

Start of changeDFHD2EDFEnd of change

Start of changeDFHDB2066End of change
Start of changedate time applid tranid termid Abend abcode in DFHD2EX1 - PPT entry for dynamic plan exit program progname defines the program as remote.End of change
Start of change
Explanation:

The PPT entry for the dynamic plan exit program progname defines the program as remote. The dynamic plan exit program must be local to this CICS system.

End of change
Start of change
System action:

Normal transaction abend processing continues.

End of change
Start of change
User response:

Correct the PPT entry to define the program as local.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changetermid, End of changeStart of changeabcode, End of changeStart of changeprognameEnd of change

Start of changeDFHDB2067End of change
Start of changedate time applid The CICS-DB2 attachment facility is already inactive.End of change
Start of change
Explanation:

A DSNC STOP command or an EXEC CICS SET DB2CONN NOTCONNECTED command was issued when the CICS-DB2 interface was already inactive.

End of change
Start of change
System action:

The CICS-DB2 attachment facility stop processing is ended.

End of change
Start of change
User response:

If this was unexpected, examine earlier messages to determine why the CICS-DB2 attachment facility is inactive.

End of change
Start of change
Destination:

CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2STPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplidEnd of change

Start of changeDFHDB2068End of change
Start of changeapplid Send text command to terminal termid failed with eibresp X'eibresp'.End of change
Start of change
Explanation:

While processing a DSNC command, an EXEC CICS SEND TEXT command to terminal termid failed with EIBRESP eibresp.

End of change
Start of change
System action:

Processing of the command terminates.

End of change
Start of change
User response:

Examine the eibresp value eibresp to determine why the SEND TEXT command failed.

End of change
Start of change
Destination:

Console and Terminal End User

End of change
Modules:

Start of changeDFHD2CCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changetermid,End of changeStart of changeX'End of changeStart of changeeibrespEnd of changeStart of change'End of change

Start of changeDFHDB2069End of change
Start of changeapplid Send page command to terminal termid failed with eibresp X'eibresp'.End of change
Start of change
Explanation:

While processing a DSNC command, an EXEC CICS SEND PAGE command to terminal termid failed with EIBRESP eibresp.

End of change
Start of change
System action:

Processing of the command terminates.

End of change
Start of change
User response:

Examine the eibresp value to determine why the SEND PAGE command failed.

End of change
Start of change
Destination:

Console and Terminal End User

End of change
Modules:

Start of changeDFHD2CCEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changetermid,End of changeStart of changeX'End of changeStart of changeeibrespEnd of changeStart of change'End of change

Start of changeDFHDB2070End of change
Start of changedate time applid Syncpoint rollback failed for transaction transid with eibresp2 X'eibresp2'End of change
Start of change
Explanation:

DB2 detected a deadlock and the CICS-DB2 attachment facility attempted a syncpoint rollback command for transaction transid because DROLLBACK(YES) was specified for the DB2ENTRY or POOL. The syncpoint rollback command failed with EIBRESP2 set to eibresp2.

End of change
Start of change
System action:

The transaction is abnormally terminated with abend code AD2Z.

End of change
Start of change
User response:

Examine the eibresp2 value eibresp2 to determine why the syncpoint rollback request failed. One possible reason could be that the transaction running is a DPL server transaction which was DPLed to by a client transaction without specifying the SYNCONRETURN parameter. In this case syncpoints or syncpoint rollbacks cannot be taken by the server transaction, so DROLLBACK(YES) is invalid in this case.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetransid, End of changeStart of changeX'End of changeStart of changeeibresp2End of changeStart of change'End of change

Start of changeDFHDB2071End of change
Start of changedate time applid The first error destination cannot be null.End of change
Start of change
Explanation:

This message is in response to a CICS-DB2 attachment facility DSNC MODIFY DESTINATION command. An attempt was made to nullify the first error destination by setting it to '****'. The CICS-DB2 attachment facility does not allow a null first error destination. The second and third error destinations may be nullified.

End of change
Start of change
System action:

The CICS-DB2 attachment facility command is not processed.

End of change
Start of change
User response:

Re-enter the command with a correct destination ID.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2072End of change
Start of changedate time applid Transaction transid , task tasknum has been directed to the pool as DB2ENTRY db2ename is disabled.End of change
Start of change
Explanation:

Transaction transid is associated with DB2ENTRY db2ename. However DB2ENTRY db2ename is disabled or disabling and the DISABLEDACT keyword on the DB2ENTRY specifies that new work should be directed to the pool.

End of change
Start of change
System action:

The transaction will use a DB2 thread from the pool.

This message is output for each task that attempts to use the disabled DB2ENTRY.

End of change
Start of change
User response:

Determine why the DB2ENTRY has been disabled. If appropriate re-enable the DB2ENTRY.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetransid, End of changeStart of changetasknum, End of changeStart of changedb2enameEnd of change

Start of changeDFHDB2073End of change
Start of changedate time applid Transaction transid has been directed to the pool as DB2TRAN db2tname refers to DB2ENTRY db2ename which is not installed.End of change
Start of change
Explanation:

Transaction transid is associated with DB2TRAN db2tname which is turn refers to DB2ENTRY db2ename. However DB2ENTRY db2ename is not installed in the CICS system. The DB2TRAN db2tname is an 'orphan' in that it refers to a DB2ENTRY that does not exist. A DB2TRAN cannot be installed unless its associated DB2ENTRY has been installed first. Hence either the DB2ENTRY has subsequently been discarded or the DB2TRAN modified by a SET command to refer to a non existent DB2ENTRY.

End of change
Start of change
System action:

The transaction will use a DB2 thread from the pool.

This message is output only when an attempt is made to locate a DB2ENTRY for the transaction. Having decided to use the pool, the CICS-DB2 attachment facility will use the pool for all subsequent transactions of the same name without locating the DB2ENTRY each time. When any DB2TRAN or DB2ENTRY is installed or modified will this force a relocate of the DB2ENTRY next time the transaction is run.

End of change
Start of change
User response:

Determine why the DB2ENTRY is not installed. If appropriate re-install the DB2ENTRY.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2EX1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetransid, End of changeStart of changedb2tname, End of changeStart of changedb2enameEnd of change

DFHDB2074
date time applid CICS-DB2 Attachment facility startup cannot proceed as the currently installed DB2CONN is not useable.
Explanation:

The CICS-DB2 Attachment facility detected that the currently installed DB2CONN is marked for discard. This implies that a previous discard of the DB2CONN did not complete successfully. A discard of a DB2CONN involves CICS discarding all DB2TRANs and DB2ENTRYs first before discarding the DB2CONN. The discard request failed before finally deleting the DB2CONN.

System action:

Startup of the CICS-DB2 interface does not complete.

User response:

Start of changeIf an RDO-defined RCT is being used, re-issue the discard for the DB2CONN. When it has been successfully discarded, re-install the required DB2CONN, DB2ENTRYs and DB2TRANs and then retry the startup of the CICS-DB2 interface.End of change

If a macro RCT is to be used, issue a discard for the current DB2CONN and then retry the startup of the CICS-DB2 interface.

Destination:

CDB2 and Terminal End User

Modules:

DFHD2STR

XMEOUT Parameters: date, time,applid

Start of changeDFHDB2100End of change
Start of changeapplid Program DFHD2RP cannot be found.End of change
Start of change
Explanation:

CICS cannot link to the CICS/DB2 restart program (DFHD2RP).

CICS cannot find DFHD2RP in any data set concatenated in the DFHRPL DD statement in the CICS startup job stream.

End of change
Start of change
System action:

CICS initialization terminates with message DFHSI1521 and a dump is taken.

End of change
Start of change
User response:

To correct this error, place DFHD2RP in a partitioned data set in the DFHRPL DD statement.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHD2IN2End of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHDB2101End of change
Start of changedate time applid terminal userid tranid DB2CONN db2conn-name has been added.End of change
Start of change
Explanation:

This is an audit log message indicating that DB2CONN db2conn-name has been added to the CICS system using the INSTALL command or EXEC CICS CREATE. Where:

There can be only one DB2CONN installed in the CICS system at a time. A DB2CONN is the minimum required for an RCT.

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2TMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeterminal, End of changeStart of changeuserid, End of changeStart of changetranid, End of changeStart of changedb2conn-nameEnd of change

Start of changeDFHDB2102End of change
Start of changedate time applid terminal userid tranid DB2CONN db2conn-name has been replaced.End of change
Start of change
Explanation:

This is an audit log message indicating that DB2CONN db2conn-name has been replaced in the RCT using the INSTALL command or EXEC CICS CREATE. Where:

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2TMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeterminal, End of changeStart of changeuserid, End of changeStart of changetranid, End of changeStart of changedb2conn-nameEnd of change

Start of changeDFHDB2103End of change
Start of changedate time applid terminal userid tranid DB2CONN db2conn-name has been deleted.End of change
Start of change
Explanation:

This is an audit log message indicating that DB2CONN db2conn-name has been deleted from the CICS system using the DISCARD command. Where:

Deleting of a DB2CONN means that the whole RCT is deleted. This message will have been preceded by messages indicating the deletion of any currently installed DB2ENTRYs and DB2TRANs which by definition are always associated with the currently installed DB2CONN.

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2TMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeterminal, End of changeStart of changeuserid, End of changeStart of changetranid, End of changeStart of changedb2conn-nameEnd of change

Start of changeDFHDB2104End of change
Start of changedate time applid terminal userid tranid DB2ENTRY db2entry-name has been added.End of change
Start of change
Explanation:

This is an audit log message indicating that DB2ENTRY db2entry-name has been added to the CICS system using the INSTALL command or EXEC CICS CREATE. Where:

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2TMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeterminal, End of changeStart of changeuserid, End of changeStart of changetranid, End of changeStart of changedb2entry-nameEnd of change

Start of changeDFHDB2105End of change
Start of changedate time applid terminal userid tranid DB2ENTRY db2entry-name has been replaced.End of change
Start of change
Explanation:

This is an audit log message indicating that DB2ENTRY db2entry-name has been replaced in the RCT using the INSTALL command or EXEC CICS CREATE. Where:

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2TMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeterminal, End of changeStart of changeuserid, End of changeStart of changetranid, End of changeStart of changedb2entry-nameEnd of change

Start of changeDFHDB2106End of change
Start of changedate time applid terminal userid tranid DB2ENTRY db2entry-name has been deleted.End of change
Start of change
Explanation:

This is an audit log message indicating that DB2ENTRY db2entry-name has been deleted from the CICS system using the DISCARD command. Where:

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2TMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeterminal, End of changeStart of changeuserid, End of changeStart of changetranid, End of changeStart of changedb2entry-nameEnd of change

Start of changeDFHDB2107End of change
Start of changedate time applid terminal userid tranid DB2TRAN db2tran-name has been added.End of change
Start of change
Explanation:

This is an audit log message indicating that DB2TRAN db2tran-name has been added to the CICS system using the INSTALL command or EXEC CICS CREATE. Where:

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2TMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeterminal, End of changeStart of changeuserid, End of changeStart of changetranid, End of changeStart of changedb2tran-nameEnd of change

Start of changeDFHDB2108End of change
Start of changedate time applid terminal userid tranid DB2TRAN db2tran-name has been replaced.End of change
Start of change
Explanation:

This is an audit log message indicating that DB2TRAN db2tran-name has been replaced in the RCT using the INSTALL command or EXEC CICS CREATE. Where:

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2TMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeterminal, End of changeStart of changeuserid, End of changeStart of changetranid, End of changeStart of changedb2tran-nameEnd of change

Start of changeDFHDB2109End of change
Start of changedate time applid terminal userid tranid DB2TRAN db2tran-name has been deleted.End of change
Start of change
Explanation:

This is an audit log message indicating that DB2TRAN db2tran-name has been deleted from the CICS system using the DISCARD command. Where:

End of change
Start of change
System action:

The system continues normally.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2TMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeterminal, End of changeStart of changeuserid, End of changeStart of changetranid, End of changeStart of changedb2tran-nameEnd of change

Start of changeDFHDB2207End of change
Start of changedate time applid Load error rc abend-code for module modnameEnd of change
Start of change
Explanation:

Error rc with abend-code occurred when the CICS-DB2 attachment facility initialization attempted to use the MVS LOAD macro to load module modname.

End of change
Start of change
System action:

The CICS-DB2 attachment initialization does not complete.

End of change
Start of change
User response:

Resolve the problem indicated by the LOAD return code and abend code.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2STREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changerc, End of changeStart of changeabend-code, End of changeStart of changemodnameEnd of change

Start of changeDFHDB2208End of change
Start of changedate time applid Delete error rc for module modnameEnd of change
Start of change
Explanation:

Error rc occurred when the CICS-DB2 attachment facility attempted to use the MVS DELETE macro to delete module modname during shutdown of the CICS-DB2 interface.

End of change
Start of change
System action:

The CICS-DB2 attachment shutdown continues.

End of change
Start of change
User response:

Resolve the problem indicated by the DELETE return code.

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2STPEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changerc, End of changeStart of changemodnameEnd of change

Start of changeDFHDB2210End of change
Start of changedate time applid DB2 subsystem id db2-id contains invalid characters. The CICS-DB2 Attachment facility is not started.End of change
Start of change
Explanation:

The CICS-DB2 attachment facility startup cannot complete because the db2-id subsystem id specified on the DSNC STRT command contains invalid characters.

End of change
Start of change
System action:

The CICS-DB2 attachment facility does not start.

End of change
Start of change
User response:

Correct the DB2 subsystem id and retry the DSNC STRT command.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeDFHDB2211IEnd of change
Start of changedate time applid Maxopentcbs setting of xxx in the SIT conflicts with the tcblimit setting of yyy in the DB2CONN definition.End of change
Start of change
Explanation:

The CICS-DB2 Attachment Facility detected that CICS is connected to DB2 Version 6 or later and that the setting of MAXOPENTCBS in the SIT is lower than the TCBLIMIT setting in the DB2CONN definition.

When CICS is connected to DB2 Version 6 or later, the CICS-DB2 Attachment Facility uses CICS open TCBs to access DB2 rather than privately managed subtask TCBs. The MAXOPENTCBS SIT parameter defines the maximum number of open TCBs allowed in the CICS system for use by all openapi enabled task related user exits. The TCBLIMIT parameter on the DB2CONN definition defines how many of the open TCBs can be used for DB2, that is, a subset of MAXOPENTCBS for use with DB2.

End of change
Start of change
System action:

Startup of the CICS-DB2 attachment continues.

End of change
Start of change
User response:

Review the setting of MAXOPENTCBS to ensure there are enough TCBs to process your DB2 workload. The MAXOPENTCBS parameter can be changed online via the SET DISPATCHER command.

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

End of change
Start of change
Destination:

Console and Transient Data Queue CDB2

End of change
Modules:

Start of changeDFHD2STREnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changexxx, End of changeStart of changeyyyEnd of change

Start of changeDFHDB2300End of change
Start of changedate time applid tranid DB2 command output truncated (ifcabnm bytes not shown).End of change
Start of change
Explanation:

ifcabnm bytes of a DB2 command response could not be shown.

End of change
Start of change
System action:

The command processing completes, but the output is truncated.

End of change
Start of change
User response:

If you need complete command output, modify the command to reduce the amount of output. For example, specify specific databases rather than an asterisk on a -DISPLAY DATABASE(xxxx).

End of change
Start of change
Destination:

CDB2

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranid, End of changeStart of changeifcabnmEnd of change

Start of changeDFHDB2301End of change
Start of changedate time applid tranid DB2 command complete.End of change
Start of change
Explanation:

The DB2 command processing is complete.

End of change
Start of change
System action:

Control is returned to the user.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CDB2 and Terminal End User

End of change
Modules:

Start of changeDFHD2CM1End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetranidEnd of change

DFHDB8101 I
date time applid Connection to DBCTL xxxx is now complete. Startup Table Suffix used is xx.
Explanation:

DBCTL has notified CICS that the CICS-DBCTL connection is complete.

System action:

CICS resynchronizes any outstanding DBCTL in-doubts.

User response:

None.

Destination:

CDBC

Modules:

DFHDBCT

XMEOUT Parameters: date, time,applid, xxxx, xx

DFHDB8102 I
date time applid Disconnection from DBCTL xxxx is now complete.
Explanation:

CICS has successfully disconnected from DBCTL.

System action:

CICS has successfully disconnected from DBCTL and performed its clean up.

User response:

None.

Destination:

CDBC

Modules:

DFHDBDI

XMEOUT Parameters: date, time,applid, xxxx

DFHDB8103 E
date time applid IDENTIFY request to DBCTL xxxx has failed. MVS SSI return code rc, reason code reason.
Explanation:

CICS has attempted to connect to DBCTL. The attempt has failed. CICS has been notified that DBCTL is not currently executing. The return code from MVS SSI, reported in PAPLRETC, is rc. The reason code from MVS SSI, reported in PAPLRCOD, is reason. The return and reason codes reported in PAPLRETC and PAPLRCOD are explained in the IMS™ Messages and Codes manual.

System action:

CICS attempts to connect to DBCTL at 5 second intervals, issuing this message at each attempt, and message DFHDB8297 at 1 minute intervals, until either:

  1. Disconnection is requested via the CICS supplied DBCTL support menu transaction, CDBC.
  2. 10 minutes have elapsed, after which time CICS stops attempting to connect and IMS message DFS0690 is issued, requesting the operator to type in WAIT (retry the connection attempt) or CANCEL (abandon the connection attempt).

Refer to the explanation of DFHDB8297 for more information. Refer to the IMS Messages and Codes manual for further information on message DFS0690.

User response:

Check why DBCTL is not running. You can cancel the connection attempts by using the CDBC transaction to issue a disconnect request. If message DFH0690 has been issued you should reply to this.

Destination:

CDBC

Modules:

DFHDBCT

XMEOUT Parameters: date, time,applid, xxxx, rc, reason

DFHDB8104 E
date time applid IDENTIFY request to DBCTL xxxx has been rejected by DBCTL. {System abend code | IMS user abend code | DBCTL return code }rc.
Explanation:

CICS has attempted to connect to DBCTL. The attempt has failed. CICS has been notified that DBCTL has rejected the identify request.

System action:

The attempt to connect to DBCTL is abandoned and the storage associated with the CICS-DBCTL interface is cleaned up. Message DFHDB8102 is output.

User response:

For further information about the nonzero response code, if rc is:

Destination:

CDBC

Modules:

DFHDBCT

XMEOUT Parameters: date, time,applid, xxxx, {1=System abend code , 2=IMS user abend code , 3=DBCTL return code }, rc

DFHDB8105 W
date time applid Operator has requested cancellation of the connection to DBCTL.
Explanation:

DBCTL notifies CICS that the operator has replied ‘CANCEL’ to IMS message DFS0690. Refer to the IMS Messages and Codes manual for information on IMS message DFS0690.

System action:

CICS cleans up the storage associated with the CICS-DBCTL interface and issues message DFHDB8102.

User response:

None. This message is for information only.

Destination:

CDBC

Modules:

DFHDBCT

XMEOUT Parameters: date, time,applid

DFHDB8106 E
date time applid The DRA has abnormally terminated. CICS is no longer connected to DBCTL id xxxx.
Explanation:

DBCTL has notified CICS that the database resource adapter (DRA) is abnormally terminating.

System action:

CICS cleans up the storage associated with the CICS-DBCTL interface and disconnects from DBCTL. CICS then issues message DFHDB8102.

User response:

See the CICS IMS Database Control Guide for information about problem determination. If you wish to reconnect CICS to DBCTL, use the menu transaction CDBC.

Destination:

CDBC

Modules:

DFHDBCT

XMEOUT Parameters: date, time,applid, xxxx

DFHDB8107 E
date time applid DBCTL xxxx has abnormally terminated. Will attempt to reconnect.
Explanation:

DBCTL notifies CICS it is about to terminate.

System action:

CICS will attempt to reconnect to DBCTL.

User response:

Notify the system programmer.

Look for messages output by the DBCTL system and determine why DBCTL failed. Restart DBCTL if required.

Destination:

CDBC

Modules:

DFHDBCT

XMEOUT Parameters: date, time,applid, xxxx

DFHDB8108 I
date time applid DBCTL xxxx has received a CHECKPOINT FREEZE command. CICS will disconnect from DBCTL.
Explanation:

DBCTL notifies CICS that it is about terminate because a CHECKPOINT FREEZE command has been issued.

System action:

CICS will clean up the storage associated with the CICS-DBCTL interface and will then output message DFHDB8102.

User response:

None.

Destination:

CDBC

Modules:

DFHDBCT

XMEOUT Parameters: date, time,applid, xxxx

DFHDB8109 E
date time applid Request to DL/I failed for transaction tranid, task taskid, recovery token X'nn'{, system abend code | , IMS user abend code | , DBCTL return code }rc, DBCTL id xxxx.
Explanation:

DBCTL xxxx returns a nonzero response code rc when a DL/I request has been issued from an application program.

System action:

The CICS transaction may be abnormally terminated.

User response:

If the CICS transaction is abnormally terminated, refer to the accompanying CICS transaction abend code.

For further information about the nonzero response code, if rc is:

For further information about the unit of recovery, refer to the CICS IMS Database Control Guide.

Destination:

CDBC

Modules:

DFHDLIDP

XMEOUT Parameters: date, time,applid, tranid, taskid, X'nn', {1=, system abend code , 2=, IMS user abend code , 3=, DBCTL return code },rc, xxxx

DFHDB8110 E
date time applid Non zero return code from DFHDBAT. Return code rc for request request.
Explanation:

The module DFHDBAT, which is a task related user exit forming part of the CICS-DBCTL interface, returns a nonzero return code in reply to a request issued from CICS to DBCTL.

System action:

The request to DBCTL fails.

Three types of request to DBCTL can fail in this way:

  1. A request to connect to DBCTL from module DFHDBCON
  2. A request to disconnect from DBCTL from module DFHDBDSC
  3. A DL/I request from an application program via module DFHDLIDP

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

User response:

The return code is one of the following:

4 -- CALL NOT UNDERSTOOD
This can be returned when attempting to connect, disconnect or issue DL/I requests to DBCTL. The most likely cause is a storage overwrite. If CICS detects a storage overwrite, a dump is taken.
8 -- REDUNDANT INTERFACE CALL
This can be returned when attempting to connect or disconnect from DBCTL. The request is ignored.
16 -- DISCONNECT PRE-EMPTED
This can be returned when attempting to disconnect from DBCTL while a disconnection request is already being processed.
24 -- ADAPTER NOT READY
A request has been made to the adaptor DFHDBAT but CICS is still in the process of connecting to DBCTL.
28 -- ADAPTER IS DISABLED
This indicates that the CICS-DBCTL interface is not available.
Note:
Start of change
The DBCTL interface terminates normally after any inflight tasks accessing DBCTL complete the unit of work. Subsequently any new unit of work or ATI task can receive this return code because of a PCB schedule failure.
End of change

Destination:

CDBC

Modules:

DFHDBCON, DFHDBDSC, DFHDLIDP

XMEOUT Parameters: date, time,applid, rc, request

DFHDB8111 E
date time applid Connection has failed. DBCTL return code rc.
Explanation:

DBCTL returns a nonzero response code when CICS is attempting to connect to it.

System action:

The connection attempt is abandoned.

User response:

Notify the system programmer.

For further information about the DBCTL return code, refer to the IMS Messages and Codes manual.

Destination:

CDBC

Modules:

DFHDBCON

XMEOUT Parameters: date, time,applid, rc

DFHDB8112 E
date time applid Unable to generate Task Token due to purge request.
Explanation:

The module, DFHDBTOX, was invoked:

The GETMAIN failed.

System action:

Processing continues.

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

User response:

This message indicates that there is a storage management problem. You should check for other messages issued from the CICS region to the MVS console.

See the CICS Problem Determination Guide for guidance on dealing with storage problems.

Destination:

CDBC

Modules:

DFHDBTOX

XMEOUT Parameters: date, time,applid

DFHDB8113 E
date time applid Getmain failure for storage to hold the indoubt list. Resync has not taken place.
Explanation:

Connection to DBCTL has been completed, but there are some in-doubts outstanding. The GETMAIN to store the in-doubts has failed.

System action:

CICS remains connected to DBCTL but the in-doubts are not resolved.

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

User response:

This message indicates that there is a storage management problem. You should check for other messages issued from the CICS region to the MVS console.

See the CICS Problem Determination Guide for guidance on dealing with storage problems.

Destination:

CDBC

Modules:

DFHDBCT

XMEOUT Parameters: date, time,applid

DFHDB8114 E
date time applid Connection has failed. DRA startup table with suffix xx cannot be found.
Explanation:

An attempt has been made to connect CICS to DBCTL but the DRA Startup Table with the suffix xx cannot be found.

System action:

The connection attempt is abandoned.

User response:

If you were using the DBCTL Support Menu transaction, CDBC, check to see if you have mistyped the suffix value.

If you have not mistyped the suffix value then notify the system programmer.

Place the DRA Startup Table in a CICS STEPLIB library. For further guidance on how to do this, see the CICS IMS Database Control Guide.

Destination:

CDBC

Modules:

DFHDBCON

XMEOUT Parameters: date, time,applid, xx

DFHDB8115 E
date time applid Connection has failed. Module DFSPRRC0 cannot be found.
Explanation:

An attempt has been made to connect CICS to DBCTL but the DRA Router module, DFSPRRC0, cannot be found.

System action:

The connection attempt is abandoned.

User response:

Place the module DFSPRRC0 in a CICS STEPLIB library. For further guidance on how to do this, refer to the CICS IMS Database Control Guide.

Destination:

CDBC

Modules:

DFHDBCON

XMEOUT Parameters: date, time,applid

DFHDB8116 I
date time applid Connection to DBCTL xxxx is proceeding. Startup Table Suffix used is xx.
Explanation:

The first phase of connecting CICS to DBCTL has been completed.

System action:

CICS connection to DBCTL proceeds.

User response:

None.

Destination:

CDBC

Modules:

DFHDBCON

XMEOUT Parameters: date, time,applid, xxxx, xx

DFHDB8117 W
date time applid No connection to DBCTL made although the connection program is in the PLT.
Explanation:

The connection program, DFHDBCON, has been placed in the program list table (PLT) but CICS was not connected when CICS last shut down.

System action:

CICS will not connect to DBCTL.

User response:

This is a warning message. In this case, if you wish to connect CICS to DBCTL then use the DBCTL Support Menu transaction, CDBC.

Destination:

CDBC

Modules:

DFHDBCON

XMEOUT Parameters: date, time,applid

DFHDB8118 E
date time applid Connection to DBCTL xxxx has been rejected by CICS. Reason code rc.
Explanation:

CICS has rejected the connection attempt to DBCTL for reason rc The value in the reason code field is 4. This indicates an invalid IMS/ESA release for storage protection. That is, CICS storage protection was active, and an attempt was made to connect to a DBCTL system running a release of IMS/ESA that does not support the storage protection function.

System action:

On completion of phase 2 connection processing, CICS indicates to the database resource adapter (DRA), in the control exit, that the DRA should terminate. CICS then completes cleanup of the CICS-DBCTL interface. The status of the interface is that CICS is not connected to DBCTL.

User response:

Connection to this DBCTL system is only possible if CICS is run with storage protection turned off. To run with storage protection on, install a release of IMS/ESA that supports the storage protection function.

Destination:

CDBC

Modules:

DFHDBCT

XMEOUT Parameters: date, time,applid, xxxx, rc

DFHDB8119 I
date time applid CICS is INDOUBT about the LUW with recovery token X'rectok' after issuing a single phase commit request to DBCTL, {SYSTEM ABEND CODE | IMS USER ABEND | DBCTL RETURN CODE} rc.
Explanation:

CICS was attempting to syncpoint updates made to IMS databases via DBCTL for the logical unit of work (LUW) identified by unit of recovery X'rectok'. CICS has detected that updates were made to only one resource manager, DBCTL, in this LUW, and hence has issued a single-phase commit to DBCTL, in place of the normal two-phase commit process. An unexpected response to the single-phase commit has been received from DBCTL, and so CICS is INDOUBT about this LUW. CICS is unable to report whether the updates made via DBCTL have been committed or backed out. No local CICS resources are affected.

System action:

The transaction terminates abnormally with abend code ADCS and a transaction dump. CICS processing continues.

User response:

The unit of recovery X'rectok' output with this message can be used in conjunction with IMS message DFSxxxx output on the IMS console to determine the outcome of the LUW.

If the IMS region has failed, on restart of the IMS region, IMS will output DFSxxxx messages for each LUW that has committed using the single-phase commit protocol. The DFSxxxx message contains the same X'rectok' recovery token as output in this message. While matching up the recovery tokens, if a DFSxxxx message is found with the same recovery token, then the LUW was committed. Failure to find a relevant DFSxxxx message means that the LUW has been backed out.

Rather than the IMS region failing, if the bad response to single-phase commit was caused by an individual thread failure and the LUW has been committed, then IMS outputs a DFSxxxx message for just this LUW.

For further information on IMS message DFSxxxx, refer to the IMS Messages and Codes manual

For further information about the nonzero response code, if rc is:

Destination:

CDBC

Modules:

DFHDBAT

XMEOUT Parameters: date, time,applid, X'rectok', {1=SYSTEM ABEND CODE, 2=IMS USER ABEND, 3=DBCTL RETURN CODE}, rc

DFHDB8120 I
date time applid DBCTL may be INDOUBT about the LUW with recovery token X'nn', which CICS has {committed | backed out}, {SYSTEM ABEND CODE | IMS USER ABEND CODE | DBCTL RETURN CODE} rc.
Explanation:

CICS has received a bad return code from DBCTL for a commit or backout request for the logical unit of work (LUW) identified by unit of recovery X'nn'.

System action:

CICS has either backed out or committed this LUW. CICS continues.

User response:

At the next reconnection, CICS and DBCTL resolve all INDOUBTs.

Alternatively you can request DBCTL to find out if the LUW is INDOUBT, and instruct DBCTL to commit it or back it out. For more information on how to do this, refer to the CICS IMS Database Control Guide.

For further information about the nonzero response code, if rc is:

Destination:

CDBC

Modules:

DFHDBAT

XMEOUT Parameters: date, time,applid, X'nn', {1=committed,2=backed out}, {1=SYSTEM ABEND CODE, 2=IMS USER ABEND CODE, 3=DBCTL RETURN CODE},rc

DFHDB8121 I
date time applid A failure has occurred in DBCTL during syncpoint prepare processing. {System abend code |IMS user abend code | DBCTL return code |IMS fast path status code} rc.
Explanation:

CICS has detected a failure in DBCTL during syncpoint prepare processing.

System action:

The transaction terminates abnormally with abend code ASP7 and a transaction dump. CICS processing continues.

User response:

Refer to the abend code ASP7 for further information about the accompanying CICS transaction.

For further information about the nonzero response code, if rc is:

Destination:

CDBC

Modules:

DFHDBAT

XMEOUT Parameters: date, time,applid, {1=System abend code, 2=IMS user abend code, 3=DBCTL return code, 4=IMS fast path status code}, rc

DFHDB8122I
applid CICS is about to disconnect from DBCTL for CICS shutdown.
Explanation:

CICS was connected to DBCTL when CICS termination commenced. CICS is going to issue a disconnect request.

System action:

CICS disconnection from DBCTL proceeds.

User response:

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

Destination:

Console

Modules:

DFHDBAT

XMEOUT Parameter: applid

DFHDB8123I
applid CICS disconnection from DBCTL for CICS shutdown has completed successfully.
Explanation:

CICS was connected to DBCTL when CICS termination commenced. CICS has successfully disconnected from DBCTL.

System action:

CICS shutdown continues.

User response:

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

Destination:

Console

Modules:

DFHDBAT

XMEOUT Parameter: applid

DFHDB8124 E
date time applid CICS disconnection from DBCTL for CICS shutdown has {failed, | timed out.}{System abend code | IMS user abend code | DBCTL return code | }rc
Explanation:

CICS was connected to DBCTL when CICS termination commenced. CICS disconnection from DBCTL failed for one of the reasons given in the message text.

System action:

CICS shutdown continues.

User response:

If the failure is due to a timed out condition, the message indicates that the time elapsed since CICS requested disconnection has reached the interval specified in the TIMEOUT parameter of the DRA interface without a response from DCBTL. The default interval is 60 seconds.

If failure is due to any other condition, a nonzero return code is given. If rc is:

Destination:

Console

Modules:

DFHDBAT

XMEOUT Parameters: date, time,applid, {1=failed, , 2=timed out.}, {1=System abend code , 2=IMS user abend code , 3=DBCTL return code , 4= }, rc

DFHDB8128 W
date time applid Error linking to the CICS-DBCTL user replaceable program DFHDBUEX from module modname.
Explanation:

An attempt was made to invoke the user replaceable module, DFHDBUEX, but the module was not available.

System action:

CICS disregards the failure and continues execution.

User response:

Ensure that module DFHDBUEX is available.

Destination:

CDBC

Modules:

DFHDBCT, DFHDBDSC.

XMEOUT Parameters: date, time,applid, modname

DFHDB8129 E
date time applid Getmain failure in the Control Exit DFHDBCTX.
Explanation:

The MVS GETMAIN request failed in DFHDBCTX.

System action:

The CICS-DBCTL interface remains unchanged.

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

User response:

This message indicates that there is a storage management problem. Check for other messages issued from the CICS region to the MVS console.

See the CICS Problem Determination Guide for guidance on dealing with storage problems.

Destination:

CDBC

Modules:

DFHDBCTX

XMEOUT Parameters: date, time,applid

DFHDB8130 E
date time applid Disconnection has failed. DBCTL return code rc.
Explanation:

The disconnection attempt failed in DBCTL.

System action:

CICS abandons the attempt to disconnect from DBCTL.

User response:

For further information about the DBCTL return code, refer to the IMS Messages and Codes manual.

Destination:

CDBC

Modules:

DFHDBDSC

XMEOUT Parameters: date, time,applid, rc

DFHDB8131 E
date time applid The CICS-DBCTL control transaction has abnormally terminated with abend abcode.
Explanation:

The CICS-DBCTL control transaction, CDBO, has failed.

System action:

The CICS/DBCTL interface is no longer usable.

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

User response:

See the description of abend abcode for further guidance.

If you wish to use DBCTL from this CICS system again, you have to restart CICS.

Destination:

CDBC

Modules:

DFHDBCT

XMEOUT Parameters: date, time,applid, abcode

Start of changeDFHDB8199 EEnd of change
Start of changeGETMAIN REQUEST FOR CICS-DBCTL CONTROL WORK ELEMENT (CWE) HAS FAILED.End of change
Start of change
Explanation:

While notifying the CICS-DBCTL control transaction of changes to the state of the CICS-DBCTL interface a GETMAIN request for storage to hold a CICS-DBCTL control work element failed.

End of change
Start of change
System action:

CICS uses control exit storage in DBCTL global block (DGB) to notify the control transaction of the error. The control transaction issues message DFHDB8129 to transient data destination CDBC. CICS abandons the attempt to change the state of the CICS-DBCTL interface.

End of change
Start of change
User response:

This message indicates that there is a storage management problem. See any other messages issued from the CICS region to the MVS console for further guidance. You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

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 changeDFHDBCTXEnd of change

DFHDB8201I
The key that you pressed has no meaning on this panel.
Explanation:

The terminal operator has pressed the wrong key when using either

System action:

CICS ignores the key pressed.

User response:

Check the allowable keys display which appears at the bottom of the screen and try a valid key.

Destination:

TERMCDBC

Modules:

DFHDBIQ, DFHDBME

DFHDB8202
Selection must be one of those shown above.
Explanation:

The terminal operator has typed in an invalid option when using CDBC, the DBCTL Support Menu Transaction.

System action:

CICS rejects the invalid option.

User response:

Check the allowable options that appear on the screen and choose the appropriate one.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8204
Invalid DRA startup table suffix supplied.
Explanation:

The terminal operator has typed an invalid startup table suffix when using CDBC, the DBCTL Support Menu Transaction. The suffix must be one or two characters long consisting only of characters valid for a partitioned data set member name.

System action:

CICS rejects the invalid Startup Table Suffix.

User response:

Correct the startup table suffix and try again. You may need to check the suffix with your system programmer.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8207D
Connection to DBCTL requested. Press PF5 to confirm.
Explanation:

The terminal operator has requested that CICS should be connected to DBCTL.

This message is not used when you are running the CDBC transaction at the console. If you are running the CDBC transaction on the console, the terminal PF5 key function (to confirm the request) is not used.

System action:

If the PF5 key is pressed, then CICS will connect to DBCTL. If any other key is pressed in response to this message, CICS will not connect to DBCTL.

User response:

Press the PF5 key if you wish to proceed with connecting CICS to DBCTL. If you do not wish the connection to proceed then press the PF3 key to terminate the transaction, or change the input data and press enter.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8208D
DBCTL immediate disconnection requested. Press PF5 to confirm.
Explanation:

The terminal operator has requested that CICS should be disconnected from DBCTL immediately.

This message is not used when you are running the CDBC transaction at the console. If you are running the CDBC transaction on the console, the terminal PF5 key function (to confirm the request) is not used.

System action:

If the PF5 key is pressed, then all DL/I requests issued from this CICS system and currently being processed in DBCTL will complete and then CICS will disconnect from DBCTL. Tasks which have been using DBCTL but have not yet issued a CICS SYNCPOINT, either explicitly in the application or implicitly as a result of CICS task termination processing, will abnormally terminate with abend code ASP7. If any other key is pressed in response to this message, CICS will not disconnect from DBCTL.

User response:

Press the PF5 key if you wish to proceed with disconnecting CICS from DBCTL immediately. If you do not wish the disconnection to proceed then press the PF3 key to terminate the transaction, or change the input data and press enter.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8209D
DBCTL orderly disconnection requested. Press PF5 to confirm.
Explanation:

The terminal operator has requested that CICS should be disconnected from DBCTL in an orderly manner.

This message is not used when you are running the CDBC transaction at the console. If you are running the CDBC transaction on the console, the terminal PF5 key function (to confirm the request) is not used.

System action:

If the PF5 key is pressed, then all tasks running in this CICS system that have already used DBCTL will complete and then CICS will disconnect from DBCTL. No new tasks running in this CICS system will be permitted to use DBCTL until CICS is connected to DBCTL again. If any other key is pressed in response to this message, CICS will not disconnect from DBCTL.

User response:

Press the PF5 key if you wish to proceed with disconnecting CICS from DBCTL in an orderly way. If you do not wish the disconnection to proceed then press the PF3 key to terminate the transaction, or change the input data and press enter.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8210D
Connection to DBCTL is proceeding. Check CDBC TD queue.
Explanation:

The operator has pressed PF5 in response to message DFHDB8207 or the CDBC transaction was used from the MVS operator console to connect to DBCTL. CICS issues further messages concerning the connection to the CDBC transient data destination.

System action:

CICS proceeds with the connection attempt.

User response:

Press PF3 to terminate the transaction. Press PF2 to refresh the status information on the screen. If you are running the CDBC transaction on the console, the PF key functions are not available. Check the CDBC transient data destination for further messages.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8211D
Orderly disconnection from DBCTL is proceeding. Check CDBC TD queue.
Explanation:

The operator has pressed PF5 in response to message DFHDB8209. CICS issues further messages concerning the disconnection to the CDBC transient data destination. Additionally, DBCTL issues some messages to the MVS console.

System action:

CICS proceeds with the disconnection attempt.

User response:

You are now able to use your terminal to perform other functions. You can check to see how the disconnection attempt is proceeding by using the refresh key to refresh the CICS-DBCTL status information on the screen. In case of problems, for example, CICS does not disconnect from DBCTL, check the CDBC transient data destination.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8212D
Immediate disconnection from DBCTL is proceeding. Check CDBC TD queue.
Explanation:

The operator has pressed PF5 in response to message DFHDB8208. CICS issues further messages concerning the disconnection to the CDBC transient data destination. Additionally, DBCTL issues some messages.

System action:

CICS proceeds with the disconnection attempt.

User response:

You are now able to use your terminal to perform other functions. You can check to see how the disconnection attempt is proceeding by using the refresh key to refresh the CICS-DBCTL status information on the screen. In case of problems, for example, CICS does not disconnect from DBCTL, check the CDBC transient data destination.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8213
Connection to DBCTL is already in progress. Request is ignored.
Explanation:

The terminal operator has requested that CICS should connect to DBCTL and CICS is already trying to connect to DBCTL.

System action:

This connection request is ignored.

User response:

Use the PF2 key to refresh the CICS-DBCTL status information on the screen. If the "DBCTL connected and ready" message is not displayed, check the CDBC transient data destination to ensure that no errors have occurred while CICS was connecting to DBCTL. The operator should also check the MVS console as the message DFS0690 may have been issued, and be waiting for a reply.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8214
Connection to DBCTL has already been done. Request is ignored.
Explanation:

The terminal operator has requested that CICS should connect to DBCTL when CICS is already connected to DBCTL.

System action:

This connection request is ignored.

User response:

If you did not expect DBCTL to be connected to CICS then check the CDBC transient data destination to see when CICS did connect to DBCTL (message DFHDB8101).

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8215
Orderly disconnection from DBCTL in progress. Request is ignored.
Explanation:

The terminal operator has either:

System action:

This disconnection request is ignored.

User response:

Use the refresh key to refresh the CICS-DBCTL status information on the screen. If the ‘DBCTL not connected to CICS’ message is not displayed, check the CDBC transient data destination to ensure that no errors have occurred while CICS was disconnecting from DBCTL.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8216
Immediate disconnection from DBCTL in progress. Request is ignored.
Explanation:

The terminal operator has either:

System action:

This disconnection request is ignored.

User response:

Use the PF2 key to refresh the CICS-DBCTL status information on the screen. If the ‘DBCTL not connected to CICS’ message is not displayed, check the CDBC transient data destination to ensure that no errors have occurred while CICS was disconnecting from DBCTL. If necessary, check the location of the CDBC destination with your system programmer.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8217
DBCTL not currently connected to CICS. Request ignored.
Explanation:

The terminal operator has requested that CICS should disconnect from DBCTL when CICS is not connected to DBCTL.

System action:

This disconnection request will be ignored.

User response:

If you did not expect DBCTL to be disconnected from CICS then check the CDBC transient data destination to see when and why CICS did disconnect from DBCTL (message DFHDB8102). If you do not know where the CDBC destination is, then please check with your system programmer.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8218
CDBC - Please specify CONNECT or DISCONNECT.
Explanation:

The terminal operator has used CDBC, the DBCTL support menu transaction, from the MVS operator console and has not selected an option.

System action:

No action is taken until the operator selects an option.

User response:

Select an option by typing in CDBC with a connect or disconnect option.

See the CICS Supplied Transactions for guidance on using CDBC.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8219
DBCTL connection phase 1 in progress. Request is ignored.
Explanation:

The first phase of connecting CICS to DBCTL has not completed yet, but the terminal operator has requested disconnection from DBCTL.

System action:

This disconnection request is ignored.

User response:

Try requesting disconnection again if you wish to proceed with disconnecting CICS from DBCTL. If you still cannot disconnect then check the CDBC transient data destination to see if any messages have been issued which indicate that there are problems with the connection attempt. Also check if any messages have been issued from DBCTL.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8220
CICS-DBCTL connection is unusable. Request is ignored.
Explanation:

A failure has occurred in the CICS-DBCTL interface.

System action:

Any requests to connect or disconnect from DBCTL is ignored.

User response:

Look for earlier messages identifying the source of the error by checking the CDBC transient data destination for any messages issued from CICS and also by checking for any messages issued from DBCTL.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8221
Non zero return code rc from DFHDBAT. The request is ignored.
Explanation:

The module DFHDBAT returns a nonzero return code in reply to a request issued to DBCTL. DFHDBAT is a task-related user exit and forms part of the CICS-DBCTL interface.

System action:

The request to DBCTL fails.

User response:

See message DFHDB8110 for further guidance.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8222
Connection has failed. DBCTL return code is rc.
Explanation:

DBCTL rejects a request from CICS to connect to it.

System action:

The connection does not proceed.

User response:

See the IMS Messages and Codes manual for an explanation of the DBCTL return code.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8223
DRA startup table with suffix xx cannot be found. Request is ignored.
Explanation:

A connection request has been issued and the startup table with the suffix specified cannot be found.

System action:

The connection does not proceed.

User response:

If you were using the DBCTL Support Menu transaction, CDBC, check if you have mistyped the suffix value.

Place the DRA startup table in a CICS STEPLIB library. For guidance on how to do this, see the CICS IMS Database Control Guide.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8224
Module DFSPRRC0 cannot be found. Connection cannot be done.
Explanation:

The DRA router module, DFSPRRC0, could not be found during an attempt to connect to DBCTL.

System action:

The connection does not proceed.

User response:

Place the module DFSPRRC0 in a CICS STEPLIB library. For guidance on how to do this, see the CICS IMS Database Control Guide.

Destination:

TERMCDBC

Modules:

DFHDBME

DFHDB8225I
applid The DBCTL ID is xxxx. The DRA Startup Table suffix is xx.
Explanation:

This message is issued from module DFHDBME when CDBC, the DBCTL support menu transaction, is used from the MVS operator’s console. This message is issued from module DFHDBIQ when CDBI, the DBCTL support inquiry transaction, is used from the MVS operator’s console.

System action:

Processing continues.

User response:

None.

Destination:

TERMCDBC

Modules:

DFHDBME, DFHDBIQ

DFHDB8226
There was an error starting CDBT. Disconnection from DBCTL failed.
Explanation:

An error has occurred, starting the disconnection transaction CDBT.

System action:

The disconnection attempt fails.

User response:

Look for earlier messages identifying the source of the error on the CDBC or CSMT transient data destinations. Check that the disconnection transaction CDBT is available. Check that the disconnection module DFHDBDSC is available.

Destination:

TERMCDBC

Modules:

DFHDBME

Start of change
DFHDB8227
There was an error linking to DFHDBCON. Connection to DBCTL failed.
Explanation:

An attempt was made to connect to DBCTL but there was an error when linking to the connection module.

System action:

The connection attempt fails.

User response:

Look for earlier messages identifying the source of the error on the CDBC or CSMT transient data destinations. Check that module DFHDBCON is available.

Destination:

TERMCDBC

Modules:

DFHDBME

End of change
Start of change
DFHDB8228
The period (.) and subsequent characters have been removed.
Explanation:

A comment was found at the end of the command. The CDBM transaction has removed the comment before sending the IMS command. Comments start with the period character (.) and continue to the end of the command.

System action:

The IMS command is sent without the comment.

User response:

None.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8229
Spaces immediately after the CRC (/) have been removed.
Explanation:

One or more spaces were found between the command recognition character (CRC) and the IMS verb. The default CRC is the oblique stroke (/). Spaces in this position would normally cause an IMS command to fail.

System action:

The CDBM transaction removes the spaces before sending the IMS command.

User response:

None. The operator should not add spaces between the CRC and the command.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8230
The key that you pressed has no meaning on this panel.
Explanation:

The terminal operator has pressed the wrong key.

System action:

CICS ignores the key pressed.

User response:

Check the display of key functions at the bottom of the screen and try a valid key.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8231
FORCE IMS LOG END OF VOLUME was not set to 1 or 2.
Explanation:

When entering a /DBDUMP or /DBRECOVER IMS command, the value in the FORCE IMS LOG END OF VOLUME field must be set to either 1 or 2. If you select 1, which is the default, the command has the NOFEOV option set; this does not force IMS End OF LOG for this command. To override this, select option 2; the NOFEOV option is not added.

System action:

The command is not sent.

User response:

Choose option 1 or 2 and press Enter.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8232
Initial CRC (/) was not found. Reenter the IMS command.
Explanation:

The command recognition character (CRC) is expected at the start of the command line. The default CRC is the oblique stroke (/).

System action:

The command is not sent.

User response:

Reenter the command with the CRC as the initial character.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8233
A second CRC (/) was found. Reenter the IMS command.
Explanation:

The command field can accept only one command. A command must start with the command recognition character (CRC). The default CRC is the oblique stroke (/). A second CRC within the command field is not allowed and must be removed before the command is sent to IMS.

System action:

The command is not sent.

User response:

Correct the command field by removing the second command or correcting the command syntax.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8234
An invalid wildcard was found. Reenter the IMS command.
Explanation:

More than one database name contains a wildcard. You can use the asterisk (*) to refer to any number of characters, or the plus sign (+) to refer to a single character. However, in a command you can use wildcard characters in one database name only. Wildcards in more than one database name are not permitted and should be removed.

System action:

The command is not sent.

User response:

Remove the invalid wildcard. Either change the first wildcard string to include the database names matched by the second wildcard string, or explicitly name the databases. Alternatively issue the command with the first wildcard string, retrieve the command by pressing F9 (Retrieve) and replace the first wildcard string with the second. If there are other database names within the command, you may need to remove them before sending the command.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8235
Incorrect wildcard position. Reenter the IMS command.
Explanation:

You can use a wildcard character in a command only to refer to database names. In this case a wildcard character, an asterisk (*) or plus sign (+), has been wrongly positioned in the command.

System action:

The command is not sent.

User response:

Correct the command by moving the wildcard to a position where it can refer to a database name or names.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8236
Invalid IMS command verb. Reenter the IMS command.
Explanation:

The command has been rejected by IMS because the verb is not recognized as a valid IMS operator command.

System action:

IMS rejects the command.

User response:

Correct the command and press Enter.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8237
Command not allowed. Enter a valid IMS command.
Explanation:

This command has been rejected by IMS because it cannot be executed using the AIB interface used by CICS.

Certain IMS operator commands such as /MODIFY are not valid with the CDBM transaction and must be issued via the MVS console.

System action:

IMS rejects the command.

User response:

Enter a valid IMS operator command.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8238
Command not authorized. Enter a valid IMS command.
Explanation:

The command has been rejected by IMS because the application or user does not have the necessary authorization to execute the command as entered.

System action:

IMS rejects the command.

User response:

Get the necessary authorization and reissue the command.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8239
aaaa call failed, AIB Return X'bbbb' Reason X'cccc'
Explanation:

The command has been rejected by IMS.

System action:

IMS rejects the command.

User response:

For the IMS function code, examine the AIB return code and reason code to determine the cause of the error. Start of changeSee the IMS/ESA Application Programming: Database Manager manual, SC26-8015 for an explanation of these codes.End of change

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8240
DBCTL not connected. Run CDBC to connect.
Explanation:

CICS was unsuccessful in its attempt to schedule the program specific block (PSB) DFHDBMP before issuing the IMS command.

System action:

The command is not sent.

User response:

Ensure that the DBCTL system is attached using the CICS supplied transaction CDBC.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of change
DFHDB8241
PSB schedule unsuccessful. UIB return codes (X'aaaa')
Explanation:

CICS was unsuccessful in its attempt to schedule the program specification block (PSB) DFHDBMP before issuing the IMS command.

System action:

The command is not sent.

User response:

Ensure that PSB DFHDBMP is available to your system. See the summary of abends and return codes in the CICS IMS Database Control Guide for an explanation of the UIB return codes.

Destination:

Terminal End User

Modules:

DFHDBMP

End of change
Start of changeDFHDB8242End of change
Start of changeCommand in progress. Issue /DISPLAY command for status.End of change
Start of change
Explanation:

The command sent to IMS has not returned a segment but has sent an acknowledgment.

End of change
Start of change
System action:

The IMS command is proceeding or has completed.

End of change
Start of change
User response:

Issue a /DISPLAY command to determine the status. Press F9 (Retrieve) to retrieve the IMS command and change the command to a /DISPLAY command. Alternatively press F12 (Cancel) and enter a new command to display the status.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8243End of change
Start of changeNo match has been found for wildcard (aaaaaaaa).End of change
Start of change
Explanation:

CICS was unsuccessful in its attempt to match any IMS databases with the wildcard supplied.

End of change
Start of change
System action:

The command is not sent.

End of change
Start of change
User response:

Check the names of the databases required and/or the wildcard supplied.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8244End of change
Start of changeThe requested command cannot be found in the command file.End of change
Start of change
Explanation:

The group command entered does not exist in the command file.

End of change
Start of change
System action:

No action

End of change
Start of change
User response:

Check that the group name and command were typed correctly. A list of all available commands can be found using the browse function in the group command maintenance section of CDBM.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8245End of change
Start of changeThe command file, DFHDBFK, cannot be opened.End of change
Start of change
Explanation:

CDBM failed to open the command file, DFHDBFK.

End of change
Start of change
System action:

CDBM will not allow the user to enter the maintenance section.

End of change
Start of change
User response:

Determine the cause of the open failure, and correct the error. Retry selecting the maintenance option from within CDBM.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8246End of change
Start of changeAn error has occurred reading the command file, DFHDBFK.End of change
Start of change
Explanation:

An error occurred whilst CDBM was trying to read a record from the command file, DFHDBFK.

End of change
Start of change
System action:

CDBM cannot read and execute the requested group command.

End of change
Start of change
User response:

Determine the cause of the read failure, and correct the error. Retry issuing the group command again from within CDBM.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8247End of change
Start of changeRecord not found.End of change
Start of change
Explanation:

There was no record in the group command file, DFHDBFK, for the specified group and command.

End of change
Start of change
System action:

None.

End of change
Start of change
User response:

Browse the group command file to locate the correct record. If this message was issued during a browse request, clear the group and name fields and retry the browse.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8248End of change
Start of changeEnd of file reached during browse. Press enter to wrap.End of change
Start of change
Explanation:

The end of the file was reached during a browse request on the group command file, DFHDBFK.

End of change
Start of change
System action:

None.

End of change
Start of change
User response:

Press return to browse the group command file from the beginning.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8249End of change
Start of changeA record already exists for this command in this group.End of change
Start of change
Explanation:

A record with a matching group and command names already exists in the group command file, DFHDBFK.

End of change
Start of change
System action:

A new group command record is not added to the group command file.

End of change
Start of change
User response:

Check the command name is correct. If it is, use a different group name.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8250End of change
Start of changeA record must be read before updating.End of change
Start of change
Explanation:

Before a record in the group command file, DFHDBFK, can be updated, it must first be read.

End of change
Start of change
System action:

The group command record is not updated in the group command file.

End of change
Start of change
User response:

Read the record and apply the changes before issuing an update request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8251End of change
Start of changeA record must be read before deletion.End of change
Start of change
Explanation:

Before a record in the group command file, DFHDBFK, can be deleted, it must first be read.

End of change
Start of change
System action:

The record is not deleted from the group command file.

End of change
Start of change
User response:

Read the record before issuing a delete request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8252End of change
Start of changeGroup and command must not be altered. Record not updated.End of change
Start of change
Explanation:

The group and command fields must not be altered during a group command record update request.

End of change
Start of change
System action:

The record is not updated in the group command file, DFHDBFK.

End of change
Start of change
User response:

Add a new record with the required group and name fields. Delete the unwanted record.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8253End of change
Start of changeGroup and command must not be altered. Record not deleted.End of change
Start of change
Explanation:

The group and command fields must not be altered during a group command record delete request.

End of change
Start of change
System action:

The record is not deleted from the group command file, DFHDBFK.

End of change
Start of change
User response:

Read the correct record before issuing a delete request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8254End of change
Start of changeCannot update during browse. Read record to update.End of change
Start of change
Explanation:

Before a record in the group command file, DFHDBFK, can be updated, it must first be read.

End of change
Start of change
System action:

The group command record is not updated in the group command file.

End of change
Start of change
User response:

Read the record and apply the changes before issuing an update request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8255End of change
Start of changeCannot delete during browse. Read record to delete.End of change
Start of change
Explanation:

Before a record in the group command file, DFHDBFK, can be deleted, it must first be read.

End of change
Start of change
System action:

The record is not deleted from the group command file.

End of change
Start of change
User response:

Read the record before issuing a delete request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8256End of change
Start of changeBoth group and command must be specifed.End of change
Start of change
Explanation:

The group and command fields must both be specified when adding a new group command record to the group command file, DFHDBFK.

End of change
Start of change
System action:

A new group command record is not added to the group command file.

End of change
Start of change
User response:

Enter data in both the group and command fields and issue the add request.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8257End of change
Start of changeFunction invalid. Must be A, B, D, R or U.End of change
Start of change
Explanation:

An action requested was not valid.

End of change
Start of change
System action:

None.

End of change
Start of change
User response:

Enter a valid action letter.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8258End of change
Start of changeFile {write | rewrite | delete | read | browse} failure. EIBRESP=eibresp, EIBRESP2=eibresp2.End of change
Start of change
Explanation:

An unexpected error has occurred during a file operation on the group command file, DFHDBFK.

End of change
Start of change
System action:

The requested update to the group command file is not made.

End of change
Start of change
User response:

Determine the reason for the failure using the EIBRESP and EIBRESP2 values. Fix the cause of the error and retry the operation.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8259End of change
Start of changeGroup command, group command, {added | updated | deleted | read |browsed}.End of change
Start of change
Explanation:

The operation indicated has been performed on the group command file, DFHDBFK.

End of change
Start of change
System action:

The group command file has been successfully modified.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

Start of changeDFHDB8260End of change
Start of changeRecord length exceeds screen size.End of change
Start of change
Explanation:

The record read from the group command file, DFHDBFK, was found to contain more data than could be displayed on the screen.

End of change
Start of change
System action:

None.

End of change
Start of change
User response:

The data set associated with the group command file, DFHDBFK, has been created with a larger record size than allowed. Recreate the data set with the correct record size, and reload the data.

End of change
Start of change
Destination:

Terminal End User

End of change
Modules:

Start of changeDFHDBMPEnd of change

DFHDB8290I
DBCTL not connected to CICS.
Explanation:

This message is issued when CICS is not connected to DBCTL.

If you are using the CDBC transaction, the DBCTL Support Menu transaction, then the message is issued from module DFHDBME.

If you are using the CDBI transaction, the DBCTL Support Inquiry transaction, the message is issued from module DFHDBIQ.

System action:

Processing continues.

User response:

None.

Destination:

TERMCDBC

Modules:

DFHDBME, DFHDBIQ

DFHDB8291I
DBCTL connect phase 1 in progress.
Explanation:

CICS is in phase 1 of connecting to DBCTL and has not yet moved into phase 2 of connection processing.

If you are using the CDBC transaction, the DBCTL Support Menu transaction, this message is issued from module DFHDBME.

If you are using the CDBI transaction, the DBCTL Support Inquiry transaction, this message is issued from module DFHDBIQ.

System action:

Processing continues.

User response:

Press the PF2 key to refresh the status information on the screen. Check the CDBC transient data message destination for any other messages issued from CICS concerning the CICS-DBCTL interface.

Destination:

TERMCDBC

Modules:

DFHDBME, DFHDBIQ

DFHDB8292I
DBCTL connect phase 2 in progress.
Explanation:

CICS is in phase 2 of connecting to DBCTL. (That is, phase 1 of connection has been completed and CICS has not yet heard from DBCTL that phase 2 of connection has been completed.)

If you are using the CDBC transaction, the DBCTL Support Menu transaction, this message is issued from module DFHDBME.

If you are using the CDBI transaction, the DBCTL Support Inquiry transaction, then this message is issued from module DFHDBIQ.

System action:

Processing continues.

User response:

Press the PF2 key to refresh the status information on the screen.

Check the CDBC transient data message destination for any other messages issued from CICS concerning the CICS-DBCTL interface. Check that the DBCTL system you are trying to connect to has been initialized.

Check the MVS operator console for any IMS console messages that need a reply (for example, message DFS0690).

Destination:

TERMCDBC

Modules:

DFHDBME, DFHDBIQ

DFHDB8293I
DBCTL connected and ready.
Explanation:

CICS is connected to DBCTL.

If you are using the CDBC transaction, the DBCTL Support Menu transaction, the message is issued from module DFHDBME.

If you are using the CDBI transaction, the DBCTL Support Inquiry transaction, the message is issued from module DFHDBIQ.

System action:

Processing continues.

User response:

Press the PF3 key to terminate the transaction.

Press the PF2 key to refresh the status information on the screen.

Check the CDBC transient data message destination for any other messages issued from CICS concerning the CICS-DBCTL interface.

Destination:

TERMCDBC

Modules:

DFHDBME, DFHDBIQ

DFHDB8294I
DBCTL orderly disconnect in progress.
Explanation:

CICS is disconnecting from DBCTL in an orderly manner. (That is, all tasks using DBCTL from this CICS system will run to termination before CICS is disconnected from DBCTL.)

If you are using the CDBC transaction, the DBCTL Support Menu transaction, the message is issued from module DFHDBME.

If you are using the CDBI transaction, the DBCTL Support Inquiry transaction, the message is issued from module DFHDBIQ.

System action:

Processing continues.

User response:

Press the PF3 key to terminate the transaction.

Press the PF2 key to refresh the status information on the screen.

Check the CDBC transient data message destination for any other messages issued from CICS concerning the CICS-DBCTL interface.

Destination:

TERMCDBC

Modules:

DFHDBME, DFHDBIQ

DFHDB8295I
DBCTL immediate disconnect in progress.
Explanation:

CICS is disconnecting from DBCTL immediately. (That is, all DL/I requests issued from this CICS system and currently being processed by DBCTL will complete before CICS is disconnected from DBCTL.)

If you are using the CDBC transaction, the DBCTL Support Menu transaction, this message is issued from module DFHDBME.

If you are using the CDBI transaction, the DBCTL Support Inquiry transaction, this message is issued from module DFHDBIQ.

If there is an IMS console message DFS0690 waiting for an operator reply, this message continues to be displayed until the operator replies to the IMS console message.

System action:

Processing continues.

User response:

Press the PF3 key to terminate the transaction.

Press the PF2 key to refresh the status information on the screen.

Check the CDBC transient data message destination for any other messages issued from CICS concerning the CICS-DBCTL interface.

Destination:

TERMCDBC

Modules:

DFHDBME, DFHDBIQ

DFHDB8296I
DBCTL cannot be connected to CICS.
Explanation:

A failure has occurred in the CICS-DBCTL interface.

If you are using the CDBC transaction, the DBCTL Support Menu transaction, the message is issued from module DFHDBME.

If you are using the CDBI transaction, the DBCTL Support Inquiry transaction, the message is issued from module DFHDBIQ.

System action:

Processing continues.

User response:

Look for earlier messages identifying the source of the error by checking the CDBC transient data destination and checking any messages issued from DBCTL.

Destination:

TERMCDBC

Modules:

DFHDBME, DFHDBIQ

Start of changeDFHDB8297End of change
Start of changeapplid CICS/DBCTL CONNECTION BEING ATTEMPTEDEnd of change
Start of change
Explanation:

This message only occurs when there is no recoverable service table (RST). CICS has attempted to connect to DBCTL but has failed on one or more occasions. DBCTL may not be running, or it may be restarting after a DBCTL abend.

End of change
Start of change
System action:

CICS continues to attempt to connect every 5 seconds. This message is reissued every minute for ten minutes or until connection is made.

If the connection is not made in ten minutes, CICS will stop attempting to connect and IMS message DFS0690 is issued. If the user replies WAIT to the IMS DFS0690 message, then the IMS DRA will take over responsibility for retrying the connection attempt. The TIMER parameter in the DRA startup table specifies how often the DRA will retry the connect to DBCTL.

End of change
Start of change
User response:

Check why DBCTL is not running. You can cancel the connection attempts using the CDBC transaction by issuing a disconnect request.

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

Start of changeDFHDB8298End of change
Start of changeapplid An attempt has been made to connect to DBCTL via PLT phase 1. The request has been rejected.End of change
Start of change
Explanation:

The attempt to connect to DBCTL has been unsuccessful.

You are using a startup PLT and the request for DFHDBCON has been issued in PLT phase 1 processing. It can only be issued from PLT phase 2.

End of change
Start of change
System action:

Processing continues.

End of change
Start of change
User response:

Look at the source for your startup PLT. Ensure the DBCTL startup program (DFHDBCON) is after the statement specifying DFHDELIM.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHDBME, DFHDBCONEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

[[ Contents Previous Page | Next Page Index ]]