DFHTC1014 DATE TIME APPLID Communication resource definition for (resname) was not restored from the catalog because the resource definition for (highname) was not installed.
Explanation
During an emergency restart, CICS could not restore the resource resname from the catalog, because the definition for another resource highname that it depends on is not present. Usually resname is a session or modegroup and highname is a connection.
System action
CICS continues restart, and deletes this resource from the CICS catalog. If the definition referred to was being installed when the previous CICS failed, both definitions are restored from the system log later in the restart.
User response
If resource resname is essential to your system and is not restored later in initialization you can reinstall the resource having first installed the resource that it depends on. This message can be caused by:
-
An install which was not complete when CICS failed, in which case it is forward recovered from the system log later, and no action is needed.
-
A failure during warm shutdown in the previous run. In this case messages are produced for connections that were autoinstalled and were not uncataloged by the warm shutdown. In this case some auto-installed connections which would have been removed from the catalog if the warm shutdown had completed are recovered, but those which cause these messages are not.
-
A corrupted CICS catalog. If large numbers of unrelated resources are missing, and the preceding CICS run was not warm keypointing at the time of failure, the catalog may have been corrupted. CICS continues, but you may want to initial start in order to get your definitions to a known state.
-
A CICS logic error. In this case you need assistance from IBM. See IBM problem support for guidance on how to proceed.
Module
XMEOUT parameters/Message inserts
- DATE
- TIME
- APPLID
- resname
- highname
Destination
CSMT