The DFHDBxxxx messages are issued by the CICS-DB2 and CICS-DBCTL
interfaces. Messages for the CICS-DB2 interface are in the
range 2000-2999.
CICS-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.
This manual documents the default destination.
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. A 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.
The CICS is connected to DB2 but UOW uowid will remain indoubt in DB2.
The UOW uowid will have to be resolved manually using DB2 -DISPLAY THREAD and -RECOVER INDOUBT operator commands.
Console and Transient Data Queue CDB2
DFHD2EX1
XMEOUT Parameters: date, time,applid, db2id, X'uowid'
The CICS-DB2 attachment is already active and enabled to CICS.
The CICS-DB2 attachment facility initialization does not complete.
Only one CICS-DB2 attachment facility may be active in a CICS region.
CDB2 and Terminal End User
DFHD2STR
XMEOUT Parameters:
date,
time,
applid
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.
The CICS-DB2 attachment facility command is not processed.
Reenter the command with the correct plan name.
Terminal End User
DFHD2CC
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.
The CICS-DB2 attachment facility command is not processed.
Reenter the command with the correct transaction name.
Terminal End User
DFHD2CM1
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.
The CICS-DB2 attachment facility command is not processed.
Reenter the command with the correct destination ID.
Terminal End User
DFHD2CM1
The CICS-DB2 attachment facility does not recognize the verb entered on the DSNC command.
The command is not processed.
Reenter the command with the correct syntax.
Terminal End User
DFHD2CM1
The CICS-DB2 attachment facility DSNC command contains an unknown positional keyword or a keyword is missing.
The command is not processed.
Reenter the command with the correct syntax.
Terminal End User
DFHD2CM1
The numeric value in the DSNC modify command is invalid. The error is caused by one of the following:
The CICS-DB2 attachment facility command is not processed.
Reenter the command with a correct value.
Terminal End User
DFHD2CM1
The transaction was abnormally terminated because a DB2 thread TCB was not available on which to create a thread for the transaction.
The transaction is abnormally terminated.
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.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
tranid
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:
The transaction is abnormally terminated.
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.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
tranid,
resname
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.
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.
If the quiesce is not completed within an acceptable time period, a DSNC STOP FORCE command should be issued from another terminal.
Terminal End User
DFHD2CM1
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:
For active threads only:
Processing continues normally.
None.
CDB2 and Terminal End User
DFHD2CC
XMEOUT Parameters:
date,
time,
applid,
db2-id
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:
The name of the DB2ENTRY or '*COMMAND' for the command section and '*POOL' for the pool section.
DB2 Plan name
Total number of SQL calls made
Total number of sign-on invocations for transactions associated with this entry. A sign-on does not indicate whether a new thread is created or an existing thread reused. If a thread is reused a sign-on may occur dependent on the ACCOUNTREC setting of the DB2ENTRY.
Number of times all available threads for this entry were busy and the transaction had to wait or the thread request was diverted to the POOL.
Maximum number of concurrent threads required by transactions associated with this DB2ENTRY at any time since the last reset.
Total number of units of work that were rolled back.
One of the following two fields is incremented each time a DB2 transaction associated with this DB2ENTRY takes an explicit or implicit (end of task) syncpoint.
The total number of single-phase commits for transactions associated with this DB2ENTRY.
The total number of two-phase commits for transactions associated with this DB2ENTRY.
Processing continues normally.
None.
CDB2 and Terminal End User
DFHD2CC
XMEOUT Parameters:
date,
time,
applid,
db2conn-name,
db2-id
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.
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.
Notify the system programmer.
Console and Transient Data Queue CDB2
DFHD2TM
XMEOUT Parameters:
date,
time,
applid,
db2-id
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.
The CICS-DB2 attachment facility initialization does not complete.
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:
CDB2
DFHD2STR, DFHD2CM1
XMEOUT Parameters:
date,
time,
applid,
{1=subsystem,
2=group},
db2-id,
X'
reason-code
'
The CICS-DB2 attachment facility startup cannot complete because the db2-id group or subsystem is not active.
The CICS-DB2 attachment facility stops.
Restart the CICS-DB2 attachment facility after starting DB2.
CDB2
DFHD2STR, DFHD2CM1
XMEOUT Parameters:
date,
time,
applid,
db2-id,
{1=subsystem is not active.,
2=group
has no active members.}
The DSNC MODIFY command completed successfully.
Processing continues.
None.
Terminal End User
DFHD2CM1
The DSNC DISPLAY command completed successfully.
Processing continues normally.
None.
CDB2 and Terminal End User
DFHD2CC
XMEOUT Parameters:
date,
time,
applid
The DSNC DISCONNECT command completed successfully.
Processing continues normally.
None.
Terminal End User
DFHD2CC
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.
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.
None.
Terminal End User
DFHD2CM1
The CICS-DB2 attachment facility startup has successfully connected to DB2 subsystem db2-id group db2-group
The CICS-DB2 attachment facility is active.
If a group name does not appear then group attach is not active. You can suppress this message with the SIT parameter, MSGLVL = 0.
Console and Transient Data Queue CDB2 and Terminal End User
DFHD2STR, DFHD2CM1
XMEOUT Parameters:
date,
time,
applid,
db2-id,
{1= ,
2= group },
db2-group
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.
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.
If a group name does not appear, group attach is not active. You can suppress this message with the SIT parameter, MSGLVL = 0.
Console and Transient Data Queue CDB2 and Terminal End User
DFHD2STR, DFHD2CM1
XMEOUT Parameters:
date,
time,
applid,
db2-id,
{1= ,
2= group },
db2-group
The CICS-DB2 attachment facility has successfully disconnected from DB2 db2-id subsystem group db2-group
The CICS-DB2 attachment facility is inactive.
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.
Console and Transient Data Queue CDB2 and Terminal End User
DFHD2STP, DFHD2CM1
XMEOUT Parameters:
date,
time,
applid,
db2-id,
{1= ,
2= group },
db2-group
The CICS-DB2 attachment facility cannot accept commands directed to DB2 during or after the termination of the CICS-DB2 attachment facility.
The command is rejected.
Issue the command via the DB2 console instead.
Terminal End User
DFHD2CM1
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.
The command is rejected.
Notify the system programmer.
Terminal End User
DFHD2CM1
The DB2 command submitted by transaction received IFI return code rc and reason code reason-code
The command processing stops.
Refer to the DB2 Messages and Codes for a description of the rc and reason-code.
CDB2
DFHD2CM1
XMEOUT Parameters:
date,
time,
applid,
tranid,
rc,
X'reason-code
'
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.
The command is rejected.
Install the necessary DB2CONN. The command can then be re-issued.
CDB2 and Terminal End User
DFHD2CM1, DFHD2STR
XMEOUT Parameters:
date,
time,
applid
The DSNC DISPLAY command to an alternate destination is complete. The output should be available at the requested destination.
Processing continues normally.
None.
CDB2 and Terminal End User
DFHD2CC
XMEOUT Parameters:
date,
time,
applid
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.
Output from the command may be suppressed.
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.
Console and Terminal End User
DFHD2CC
XMEOUT Parameters:
applid,
termid
CICS indicates that recovery should not be required for uowid but DB2 subsystem db2id is indoubt.
The CICS is connected to DB2 but the UOW remains indoubt in DB2.
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.
Console and Transient Data Queue CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
X'
uowid',
db2id
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
or
has been started.
Notify the system programmer that a DB2 subsystem requires to be started according to the information supplied.
Console and Transient Data Queue CDB2 and Terminal End User
DFHD2STR,DFHD2CM1
XMEOUT Parameters:
date,
time,
applid,
{1=subsystem,
2=group},
db2-id,
{1= is not active. ,
2= has no active members.}
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.
The command is rejected.
Re-issue the command when DB2 has been started and the attachment facility has connected to DB2.
Terminal End User
DFHD2CM1
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.
Processing continues.
None.
Terminal End User
DFHD2CM1
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.
CICS-DB2 attachment facility initialization does not complete.
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.
CDB2 and Terminal End User
DFHD2STR
XMEOUT Parameters:
date,
time,
applid,
tranid,
modname
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.
Processing continues normally.
None.
Terminal End User
DFHD2CC
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.
The CICS-DB2 attachment does not connect to DB2.
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.
CDB2
DFHD2STR
XMEOUT Parameters:
date,
time,
applid,
db2-id
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.
The transaction is abnormally terminated.
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.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
resname
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.
The transaction is abnormally terminated with abend code AD21. A CICS system dump is taken.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
rmi-name
The CICS-DB2 attachment facility failed to connect because the DB2ID or DB2GROUPID id cannot be found.
The CICS-DB2 attachment facility is inactive.
None.
Console and Transient Data Queue CDB2 and Terminal End User
DFHD2STR
XMEOUT Parameters:
date,
time,
applid,
{1=subsystem,
2=group},
id
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.
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.
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.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
transid,
taskid
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.
The UOW remains indoubt in DB2 and CICS keeps hold of the UOW disposition. A CICS system dump is taken with dumpcode 00C30003.
Use the reason code to determine why the resolve indoubt request failed.
Console and Transient Data Queue CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
db2-id,
X'
uowid',
X'reason-code
'
Dynamic plan exit program progname has abnormally terminated with abend code abcode.
Normal transaction abend processing continues.
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.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
tranid,
termid,
abcode,
progname
The CICS-DB2 attachment facility has failed to link to dynamic plan exit program progname because it is not link edited AMODE 31.
Normal transaction abend processing continues.
Relinkedit the dynamic plan exit program AMODE 31.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
tranid,
termid,
abcode,
progname
The CICS-DB2 attachment facility has failed to link to dynamic plan exit program progname because it is disabled.
Normal transaction abend processing continues.
Enable the dynamic plan exit program.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
tranid,
termid,
abcode,
progname
An unexpected return code was returned from the link to the dynamic plan exit program progname by the CICS-DB2 attachment facility.
Normal transaction abend processing continues.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
tranid,
termid,
abcode,
progname
CICS requested a single-phase commit from DB2, but DB2 was unable to comply. The request failed with DB2 reason code reason-code.
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.
You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
X'
reason-code',
transid,
taskid
CICS was unable to find a PPT entry for the dynamic plan exit program progname.
Normal transaction abend processing continues.
Ensure that the dynamic plan exit program progname has been correctly defined to CICS.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
tranid,
termid,
abcode,
progname
CICS was unable to load the dynamic plan exit program progname.
Normal transaction abend processing continues.
Ensure that the dynamic plan exit program progname has been correctly defined and is in a load library accessible to CICS.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
tranid,
termid,
abcode,
progname
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.
The CICS-DB2 attachment facility initialization does not complete.
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.
CDB2
DFHD2STR, DFHD2CM1
XMEOUT Parameters:
date,
time,
applid
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.
The CICS-DB2 attachment initialization does not complete.
Ensure that the DSNC transaction definition in group DFHDB2 is the installed definition.
CDB2
DFHD2CM1
XMEOUT Parameters:
date,
time,
applid,
xxxx,
yyyy
CICS indicates that resynchronization is outstanding for subsystem db2id after DB2 Group Attach has connected to subsystem db2id2.
The CICS is connected to DB2 subsystem db2id but UOWs remain outstanding for DB2 subsystem db2id2.
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.
Console and Transient Data Queue CDB2
DFHD2STR
XMEOUT Parameters:
date,
time,
applid,
db2id,
db2id2
The module running under the CICS Execution Diagnostic Facility (EDF) attempted to display an input or output variable that had an incorrect length indicator.
EDF processing continues, but the value of the variable is not displayed.
Examine the SQL statement in the application program.
Terminal End User
DFHD2EDF
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.
Normal transaction abend processing continues.
Correct the PPT entry to define the program as local.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
tranid,
termid,
abcode,
progname
A DSNC STOP command or an EXEC CICS SET DB2CONN NOTCONNECTED command was issued when the CICS-DB2 interface was already inactive.
The CICS-DB2 attachment facility stop processing is ended.
If this was unexpected, examine earlier messages to determine why the CICS-DB2 attachment facility is inactive.
CDB2 and Terminal End User
DFHD2STP
XMEOUT Parameters:
date,
time,
applid
While processing a DSNC command, an EXEC CICS SEND TEXT command to terminal termid failed with EIBRESP eibresp.
Processing of the command terminates.
Examine the eibresp value eibresp to determine why the SEND TEXT command failed.
Console and Terminal End User
DFHD2CC
XMEOUT Parameters:
applid,
termid,
X'
eibresp
'
While processing a DSNC command, an EXEC CICS SEND PAGE command to terminal termid failed with EIBRESP eibresp.
Processing of the command terminates.
Examine the eibresp value to determine why the SEND PAGE command failed.
Console and Terminal End User
DFHD2CC
XMEOUT Parameters:
applid,
termid,
X'
eibresp
'
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.
The transaction is abnormally terminated with abend code AD2Z.
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.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
transid,
X'
eibresp2
'
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.
The CICS-DB2 attachment facility command is not processed.
Re-enter the command with a correct destination ID.
Terminal End User
DFHD2CM1
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.
The transaction will use a DB2 thread from the pool.
This message is output for each task that attempts to use the disabled DB2ENTRY.
Determine why the DB2ENTRY has been disabled. If appropriate re-enable the DB2ENTRY.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
transid,
tasknum,
db2ename
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.
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.
Determine why the DB2ENTRY is not installed. If appropriate re-install the DB2ENTRY.
CDB2
DFHD2EX1
XMEOUT Parameters:
date,
time,
applid,
transid,
db2tname,
db2ename
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.
Startup of the CICS-DB2 interface does not complete.
If 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.
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.
CDB2 and Terminal End User
DFHD2STR
XMEOUT Parameters: date, time,applid
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.
CICS initialization terminates with message DFHSI1521 and a dump is taken.
To correct this error, place DFHD2RP in a partitioned data set in the DFHRPL DD statement.
Console
DFHD2IN2
XMEOUT Parameter:
applid
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.
The system continues normally.
None.
CDB2
DFHD2TM
XMEOUT Parameters:
date,
time,
applid,
terminal,
userid,
tranid,
db2conn-name
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:
The system continues normally.
None.
CDB2
DFHD2TM
XMEOUT Parameters:
date,
time,
applid,
terminal,
userid,
tranid,
db2conn-name
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.
The system continues normally.
None.
CDB2
DFHD2TM
XMEOUT Parameters:
date,
time,
applid,
terminal,
userid,
tranid,
db2conn-name
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:
The system continues normally.
None.
CDB2
DFHD2TM
XMEOUT Parameters:
date,
time,
applid,
terminal,
userid,
tranid,
db2entry-name
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:
The system continues normally.
None.
CDB2
DFHD2TM
XMEOUT Parameters:
date,
time,
applid,
terminal,
userid,
tranid,
db2entry-name
This is an audit log message indicating that DB2ENTRY db2entry-name has been deleted from the CICS system using the DISCARD command. Where:
The system continues normally.
None.
CDB2
DFHD2TM
XMEOUT Parameters:
date,
time,
applid,
terminal,
userid,
tranid,
db2entry-name
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:
The system continues normally.
None.
CDB2
DFHD2TM
XMEOUT Parameters:
date,
time,
applid,
terminal,
userid,
tranid,
db2tran-name
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:
The system continues normally.
None.
CDB2
DFHD2TM
XMEOUT Parameters:
date,
time,
applid,
terminal,
userid,
tranid,
db2tran-name
This is an audit log message indicating that DB2TRAN db2tran-name has been deleted from the CICS system using the DISCARD command. Where:
The system continues normally.
None.
CDB2
DFHD2TM
XMEOUT Parameters:
date,
time,
applid,
terminal,
userid,
tranid,
db2tran-name
Error rc with abend-code occurred when the CICS-DB2 attachment facility initialization attempted to use the MVS LOAD macro to load module modname.
The CICS-DB2 attachment initialization does not complete.
Resolve the problem indicated by the LOAD return code and abend code.
CDB2
DFHD2STR
XMEOUT Parameters:
date,
time,
applid,
rc,
abend-code,
modname
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.
The CICS-DB2 attachment shutdown continues.
Resolve the problem indicated by the DELETE return code.
CDB2
DFHD2STP
XMEOUT Parameters:
date,
time,
applid,
rc,
modname
The CICS-DB2 attachment facility startup cannot complete because the db2-id subsystem id specified on the DSNC STRT command contains invalid characters.
The CICS-DB2 attachment facility does not start.
Correct the DB2 subsystem id and retry the DSNC STRT command.
Terminal End User
DFHD2CM1
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.
Startup of the CICS-DB2 attachment continues.
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.
Console and Transient Data Queue CDB2
DFHD2STR
XMEOUT Parameters:
date,
time,
applid,
xxx,
yyy
ifcabnm bytes of a DB2 command response could not be shown.
The command processing completes, but the output is truncated.
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).
CDB2
DFHD2CM1
XMEOUT Parameters:
date,
time,
applid,
tranid,
ifcabnm
The DB2 command processing is complete.
Control is returned to the user.
None.
CDB2 and Terminal End User
DFHD2CM1
XMEOUT Parameters:
date,
time,
applid,
tranid
DBCTL has notified CICS that the CICS-DBCTL connection is complete.
CICS resynchronizes any outstanding DBCTL in-doubts.
None.
CDBC
DFHDBCT
XMEOUT Parameters: date, time,applid, xxxx, xx
CICS has successfully disconnected from DBCTL.
CICS has successfully disconnected from DBCTL and performed its clean up.
None.
CDBC
DFHDBDI
XMEOUT Parameters: date, time,applid, xxxx
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.
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:
Refer to the explanation of DFHDB8297 for more information. Refer to the IMS Messages and Codes manual for further information on message DFS0690.
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.
CDBC
DFHDBCT
XMEOUT Parameters: date, time,applid, xxxx, rc, reason
CICS has attempted to connect to DBCTL. The attempt has failed. CICS has been notified that DBCTL has rejected the identify request.
The attempt to connect to DBCTL is abandoned and the storage associated with the CICS-DBCTL interface is cleaned up. Message DFHDB8102 is output.
For further information about the nonzero response code, if rc is:
CDBC
DFHDBCT
XMEOUT Parameters: date, time,applid, xxxx, {1=System abend code , 2=IMS user abend code , 3=DBCTL return code }, rc
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.
CICS cleans up the storage associated with the CICS-DBCTL interface and issues message DFHDB8102.
None. This message is for information only.
CDBC
DFHDBCT
XMEOUT Parameters: date, time,applid
DBCTL has notified CICS that the database resource adapter (DRA) is abnormally terminating.
CICS cleans up the storage associated with the CICS-DBCTL interface and disconnects from DBCTL. CICS then issues message DFHDB8102.
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.
CDBC
DFHDBCT
XMEOUT Parameters: date, time,applid, xxxx
DBCTL notifies CICS it is about to terminate.
CICS will attempt to reconnect to DBCTL.
Notify the system programmer.
Look for messages output by the DBCTL system and determine why DBCTL failed. Restart DBCTL if required.
CDBC
DFHDBCT
XMEOUT Parameters: date, time,applid, xxxx
DBCTL notifies CICS that it is about terminate because a CHECKPOINT FREEZE command has been issued.
CICS will clean up the storage associated with the CICS-DBCTL interface and will then output message DFHDB8102.
None.
CDBC
DFHDBCT
XMEOUT Parameters: date, time,applid, xxxx
DBCTL xxxx returns a nonzero response code rc when a DL/I request has been issued from an application program.
The CICS transaction may be abnormally terminated.
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.
CDBC
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
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.
The request to DBCTL fails.
Three types of request to DBCTL can fail in this way:
Message DFHME0116 is normally produced containing the symptom string for this problem.
The return code is one of the following:
CDBC
DFHDBCON, DFHDBDSC, DFHDLIDP
XMEOUT Parameters: date, time,applid, rc, request
DBCTL returns a nonzero response code when CICS is attempting to connect to it.
The connection attempt is abandoned.
Notify the system programmer.
For further information about the DBCTL return code, refer to the IMS Messages and Codes manual.
CDBC
DFHDBCON
XMEOUT Parameters: date, time,applid, rc
The module, DFHDBTOX, was invoked:
The GETMAIN failed.
Processing continues.
Message DFHME0116 is normally produced containing the symptom string for this problem.
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.
CDBC
DFHDBTOX
XMEOUT Parameters: date, time,applid
Connection to DBCTL has been completed, but there are some in-doubts outstanding. The GETMAIN to store the in-doubts has failed.
CICS remains connected to DBCTL but the in-doubts are not resolved.
Message DFHME0116 is normally produced containing the symptom string for this problem.
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.
CDBC
DFHDBCT
XMEOUT Parameters: date, time,applid
An attempt has been made to connect CICS to DBCTL but the DRA Startup Table with the suffix xx cannot be found.
The connection attempt is abandoned.
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.
CDBC
DFHDBCON
XMEOUT Parameters: date, time,applid, xx
An attempt has been made to connect CICS to DBCTL but the DRA Router module, DFSPRRC0, cannot be found.
The connection attempt is abandoned.
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.
CDBC
DFHDBCON
XMEOUT Parameters: date, time,applid
The first phase of connecting CICS to DBCTL has been completed.
CICS connection to DBCTL proceeds.
None.
CDBC
DFHDBCON
XMEOUT Parameters: date, time,applid, xxxx, xx
The connection program, DFHDBCON, has been placed in the program list table (PLT) but CICS was not connected when CICS last shut down.
CICS will not connect to DBCTL.
This is a warning message. In this case, if you wish to connect CICS to DBCTL then use the DBCTL Support Menu transaction, CDBC.
CDBC
DFHDBCON
XMEOUT Parameters: date, time,applid
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.
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.
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.
CDBC
DFHDBCT
XMEOUT Parameters: date, time,applid, xxxx, rc
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.
The transaction terminates abnormally with abend code ADCS and a transaction dump. CICS processing continues.
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:
CDBC
DFHDBAT
XMEOUT Parameters: date, time,applid, X'rectok', {1=SYSTEM ABEND CODE, 2=IMS USER ABEND, 3=DBCTL RETURN CODE}, rc
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'.
CICS has either backed out or committed this LUW. CICS continues.
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:
CDBC
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
CICS has detected a failure in DBCTL during syncpoint prepare processing.
The transaction terminates abnormally with abend code ASP7 and a transaction dump. CICS processing continues.
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:
CDBC
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
CICS was connected to DBCTL when CICS termination commenced. CICS is going to issue a disconnect request.
CICS disconnection from DBCTL proceeds.
None. You can suppress this message with the SIT parameter, MSGLVL = 0.
Console
DFHDBAT
XMEOUT Parameter: applid
CICS was connected to DBCTL when CICS termination commenced. CICS has successfully disconnected from DBCTL.
CICS shutdown continues.
None. You can suppress this message with the SIT parameter, MSGLVL = 0.
Console
DFHDBAT
XMEOUT Parameter: applid
CICS was connected to DBCTL when CICS termination commenced. CICS disconnection from DBCTL failed for one of the reasons given in the message text.
CICS shutdown continues.
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:
Console
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
An attempt was made to invoke the user replaceable module, DFHDBUEX, but the module was not available.
CICS disregards the failure and continues execution.
Ensure that module DFHDBUEX is available.
CDBC
DFHDBCT, DFHDBDSC.
XMEOUT Parameters: date, time,applid, modname
The MVS GETMAIN request failed in DFHDBCTX.
The CICS-DBCTL interface remains unchanged.
Message DFHME0116 is normally produced containing the symptom string for this problem.
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.
CDBC
DFHDBCTX
XMEOUT Parameters: date, time,applid
The disconnection attempt failed in DBCTL.
CICS abandons the attempt to disconnect from DBCTL.
For further information about the DBCTL return code, refer to the IMS Messages and Codes manual.
CDBC
DFHDBDSC
XMEOUT Parameters: date, time,applid, rc
The CICS-DBCTL control transaction, CDBO, has failed.
The CICS/DBCTL interface is no longer usable.
Message DFHME0116 is normally produced containing the symptom string for this problem.
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.
CDBC
DFHDBCT
XMEOUT Parameters: date, time,applid, abcode
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.
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.
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.
Console
DFHDBCTX
The terminal operator has pressed the wrong key when using either
CICS ignores the key pressed.
Check the allowable keys display which appears at the bottom of the screen and try a valid key.
TERMCDBC
DFHDBIQ, DFHDBME
The terminal operator has typed in an invalid option when using CDBC, the DBCTL Support Menu Transaction.
CICS rejects the invalid option.
Check the allowable options that appear on the screen and choose the appropriate one.
TERMCDBC
DFHDBME
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.
CICS rejects the invalid Startup Table Suffix.
Correct the startup table suffix and try again. You may need to check the suffix with your system programmer.
TERMCDBC
DFHDBME
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.
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.
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.
TERMCDBC
DFHDBME
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.
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.
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.
TERMCDBC
DFHDBME
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.
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.
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.
TERMCDBC
DFHDBME
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.
CICS proceeds with the connection attempt.
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.
TERMCDBC
DFHDBME
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.
CICS proceeds with the disconnection attempt.
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.
TERMCDBC
DFHDBME
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.
CICS proceeds with the disconnection attempt.
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.
TERMCDBC
DFHDBME
The terminal operator has requested that CICS should connect to DBCTL and CICS is already trying to connect to DBCTL.
This connection request is ignored.
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.
TERMCDBC
DFHDBME
The terminal operator has requested that CICS should connect to DBCTL when CICS is already connected to DBCTL.
This connection request is ignored.
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).
TERMCDBC
DFHDBME
The terminal operator has either:
This disconnection request is ignored.
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.
TERMCDBC
DFHDBME
The terminal operator has either:
This disconnection request is ignored.
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.
TERMCDBC
DFHDBME
The terminal operator has requested that CICS should disconnect from DBCTL when CICS is not connected to DBCTL.
This disconnection request will be ignored.
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.
TERMCDBC
DFHDBME
The terminal operator has used CDBC, the DBCTL support menu transaction, from the MVS operator console and has not selected an option.
No action is taken until the operator selects an option.
Select an option by typing in CDBC with a connect or disconnect option.
See the CICS Supplied Transactions for guidance on using CDBC.
TERMCDBC
DFHDBME
The first phase of connecting CICS to DBCTL has not completed yet, but the terminal operator has requested disconnection from DBCTL.
This disconnection request is ignored.
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.
TERMCDBC
DFHDBME
A failure has occurred in the CICS-DBCTL interface.
Any requests to connect or disconnect from DBCTL is ignored.
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.
TERMCDBC
DFHDBME
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.
The request to DBCTL fails.
See message DFHDB8110 for further guidance.
TERMCDBC
DFHDBME
DBCTL rejects a request from CICS to connect to it.
The connection does not proceed.
See the IMS Messages and Codes manual for an explanation of the DBCTL return code.
TERMCDBC
DFHDBME
A connection request has been issued and the startup table with the suffix specified cannot be found.
The connection does not proceed.
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.
TERMCDBC
DFHDBME
The DRA router module, DFSPRRC0, could not be found during an attempt to connect to DBCTL.
The connection does not proceed.
Place the module DFSPRRC0 in a CICS STEPLIB library. For guidance on how to do this, see the CICS IMS Database Control Guide.
TERMCDBC
DFHDBME
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.
Processing continues.
None.
TERMCDBC
DFHDBME, DFHDBIQ
An error has occurred, starting the disconnection transaction CDBT.
The disconnection attempt fails.
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.
TERMCDBC
DFHDBME
An attempt was made to connect to DBCTL but there was an error when linking to the connection module.
The connection attempt fails.
Look for earlier messages identifying the source of the error on the CDBC or CSMT transient data destinations. Check that module DFHDBCON is available.
TERMCDBC
DFHDBME
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.
The IMS command is sent without the comment.
None.
Terminal End User
DFHDBMP
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.
The CDBM transaction removes the spaces before sending the IMS command.
None. The operator should not add spaces between the CRC and the command.
Terminal End User
DFHDBMP
The terminal operator has pressed the wrong key.
CICS ignores the key pressed.
Check the display of key functions at the bottom of the screen and try a valid key.
Terminal End User
DFHDBMP
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.
The command is not sent.
Choose option 1 or 2 and press Enter.
Terminal End User
DFHDBMP
The command recognition character (CRC) is expected at the start of the command line. The default CRC is the oblique stroke (/).
The command is not sent.
Reenter the command with the CRC as the initial character.
Terminal End User
DFHDBMP
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.
The command is not sent.
Correct the command field by removing the second command or correcting the command syntax.
Terminal End User
DFHDBMP
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.
The command is not sent.
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.
Terminal End User
DFHDBMP
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.
The command is not sent.
Correct the command by moving the wildcard to a position where it can refer to a database name or names.
Terminal End User
DFHDBMP
The command has been rejected by IMS because the verb is not recognized as a valid IMS operator command.
IMS rejects the command.
Correct the command and press Enter.
Terminal End User
DFHDBMP
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.
IMS rejects the command.
Enter a valid IMS operator command.
Terminal End User
DFHDBMP
The command has been rejected by IMS because the application or user does not have the necessary authorization to execute the command as entered.
IMS rejects the command.
Get the necessary authorization and reissue the command.
Terminal End User
DFHDBMP
The command has been rejected by IMS.
IMS rejects the command.
For the IMS function code, examine the AIB return code and reason code
to determine the cause of the error. See the IMS/ESA Application Programming: Database Manager manual, SC26-8015 for an
explanation of these codes.
Terminal End User
DFHDBMP
CICS was unsuccessful in its attempt to schedule the program specific block (PSB) DFHDBMP before issuing the IMS command.
The command is not sent.
Ensure that the DBCTL system is attached using the CICS supplied transaction CDBC.
Terminal End User
DFHDBMP
CICS was unsuccessful in its attempt to schedule the program specification block (PSB) DFHDBMP before issuing the IMS command.
The command is not sent.
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.
Terminal End User
DFHDBMP
The command sent to IMS has not returned a segment but has sent an acknowledgment.
The IMS command is proceeding or has completed.
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.
Terminal End User
DFHDBMP
CICS was unsuccessful in its attempt to match any IMS databases with the wildcard supplied.
The command is not sent.
Check the names of the databases required and/or the wildcard supplied.
Terminal End User
DFHDBMP
The group command entered does not exist in the command file.
No action
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.
Terminal End User
DFHDBMP
CDBM failed to open the command file, DFHDBFK.
CDBM will not allow the user to enter the maintenance section.
Determine the cause of the open failure, and correct the error. Retry selecting the maintenance option from within CDBM.
Terminal End User
DFHDBMP
An error occurred whilst CDBM was trying to read a record from the command file, DFHDBFK.
CDBM cannot read and execute the requested group command.
Determine the cause of the read failure, and correct the error. Retry issuing the group command again from within CDBM.
Terminal End User
DFHDBMP
There was no record in the group command file, DFHDBFK, for the specified group and command.
None.
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.
Terminal End User
DFHDBMP
The end of the file was reached during a browse request on the group command file, DFHDBFK.
None.
Press return to browse the group command file from the beginning.
Terminal End User
DFHDBMP
A record with a matching group and command names already exists in the group command file, DFHDBFK.
A new group command record is not added to the group command file.
Check the command name is correct. If it is, use a different group name.
Terminal End User
DFHDBMP
Before a record in the group command file, DFHDBFK, can be updated, it must first be read.
The group command record is not updated in the group command file.
Read the record and apply the changes before issuing an update request.
Terminal End User
DFHDBMP
Before a record in the group command file, DFHDBFK, can be deleted, it must first be read.
The record is not deleted from the group command file.
Read the record before issuing a delete request.
Terminal End User
DFHDBMP
The group and command fields must not be altered during a group command record update request.
The record is not updated in the group command file, DFHDBFK.
Add a new record with the required group and name fields. Delete the unwanted record.
Terminal End User
DFHDBMP
The group and command fields must not be altered during a group command record delete request.
The record is not deleted from the group command file, DFHDBFK.
Read the correct record before issuing a delete request.
Terminal End User
DFHDBMP
Before a record in the group command file, DFHDBFK, can be updated, it must first be read.
The group command record is not updated in the group command file.
Read the record and apply the changes before issuing an update request.
Terminal End User
DFHDBMP
Before a record in the group command file, DFHDBFK, can be deleted, it must first be read.
The record is not deleted from the group command file.
Read the record before issuing a delete request.
Terminal End User
DFHDBMP
The group and command fields must both be specified when adding a new group command record to the group command file, DFHDBFK.
A new group command record is not added to the group command file.
Enter data in both the group and command fields and issue the add request.
Terminal End User
DFHDBMP
An action requested was not valid.
None.
Enter a valid action letter.
Terminal End User
DFHDBMP
An unexpected error has occurred during a file operation on the group command file, DFHDBFK.
The requested update to the group command file is not made.
Determine the reason for the failure using the EIBRESP and EIBRESP2 values. Fix the cause of the error and retry the operation.
Terminal End User
DFHDBMP
The operation indicated has been performed on the group command file, DFHDBFK.
The group command file has been successfully modified.
None.
Terminal End User
DFHDBMP
The record read from the group command file, DFHDBFK, was found to contain more data than could be displayed on the screen.
None.
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.
Terminal End User
DFHDBMP
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.
Processing continues.
None.
TERMCDBC
DFHDBME, DFHDBIQ
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.
Processing continues.
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.
TERMCDBC
DFHDBME, DFHDBIQ
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.
Processing continues.
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).
TERMCDBC
DFHDBME, DFHDBIQ
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.
Processing continues.
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.
TERMCDBC
DFHDBME, DFHDBIQ
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.
Processing continues.
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.
TERMCDBC
DFHDBME, DFHDBIQ
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.
Processing continues.
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.
TERMCDBC
DFHDBME, DFHDBIQ
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.
Processing continues.
Look for earlier messages identifying the source of the error by checking the CDBC transient data destination and checking any messages issued from DBCTL.
TERMCDBC
DFHDBME, DFHDBIQ
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.
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.
Check why DBCTL is not running. You can cancel the connection attempts using the CDBC transaction by issuing a disconnect request.
Console
DFHDXAX
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.
Processing continues.
Look at the source for your startup PLT. Ensure the DBCTL startup program (DFHDBCON) is after the statement specifying DFHDELIM.
Console
DFHDBME, DFHDBCON
XMEOUT Parameter:
applid