DFS3595E IMS CONNECT ERROR MESSAGE RECEIVED, active_process, RETCODE = rc, RSNCODE = rsn, LOSTSESS = cause, MODULE =mod_name, NODE = nodename, USER = username
Explanation
IMS Connect detected an error while processing a request or message from ISC and returned a non-zero return or reason code to IMS. The error message is returned to the local IMS system that issued the request or message.
In the message text:
- active_process
- The ISC process that was active when the error occurred. Possible
values include:
- SENDMSG
- When IMS Connect encountered the error, ISC was attempting to send an ISC message to a remote CICS system by way of the parallel session identified in the message text.
- SESSTERM
- When IMS Connect encountered the error, ISC was attempting to notify IMS Connect and the remote CICS system that the terminal session was terminated.
- SESSINIT
- When IMS Connect encountered the error, ISC was attempting to notify IMS Connect and the remote CICS system of the session initiation of the parallel session terminal identified in the message text.
- UNKNOWN
- Displayed when the error occurred during an unidentifiable ISC process. The troubleshooting and recovery procedure is the same as for the regular active process types.
- cause
- The cause of a lost session, as reported either by SCI through
the CSL SCI Notify Client exit routine or by IMS. The possible values include:
- ICONABE
- The local IMS Connect instance terminated unexpectedly.
- ICONSTOP
- The local IMS Connect instance was shut down.
- NONE
- Neither IMS nor the CSL SCI Notify Client exit routine recorded a cause for the lost session.
- SCIABE
- The local SCI instance that is managing communications between the local IMS system and the local IMS Connect instance terminated unexpectedly.
- SCISTOP
- The local SCI instance that is managing communications between the local IMS system and the local IMS Connect instance was shut down.
- mod_name
- The name of the module that detected the error.
- nodename
- The name of the affected parallel session terminal.
- rc
- The return code issued by IMS Connect. Some of the return codes that are more likely to be returned by IMS Connect are documented in the following table. All of the IMS Connect return and reason codes are documented in the HWSHRR macro.
- rsn
- The reason code issued by IMS Connect. Some of the reason codes that are more likely to be returned by IMS Connect are documented in the following table. All of the IMS Connect return and reason codes are documented in the HWSHRR macro.
The following table lists some of the more
likely return and reason codes that IMS Connect might return to IMS.
The explanations of any IMS Connect return and reason codes that are
not in the following table can be found in the IMS Connect HWSHRR
macro.
| Return code | Reason code | Meaning |
|---|---|---|
| X'0C00001C' | X'0000700C' | A message could not be sent to CICS. Usually message HWSG4040W or HWSG4080W is also issued. |
| X'0C00001C' | X'00007020' | The ISC datastore in IMS Connect has been stopped. Use UPDATE IMSCON TYPE(ISC) START(COMM) to start it. |
| X'0C00001C' | X'00007030' | The ISC datastore in IMS Connect has been stopped. Use UPDATE IMSCON TYPE(ISC) START(COMM) to start it. |
| X'0C00001C' | X'00007040' | The ISC datastore in IMS Connect has been stopped. Use UPDATE IMSCON TYPE(ISC) START(COMM) to start it. |
| X'0C00001C' | X'00007060' | The ISC datastore in IMS Connect cannot be found. Check the ISC statement in the IMS Connect configuration. |
| X'0C00001C' | X'00007084' | The ISC datastore in IMS Connect has been stopped. Use UPDATE IMSCON TYPE(ISC) START(COMM) to start it. |
System action
The parallel session is terminated. IMS processing continues.System programmer response
Determine the cause of the error from the RETCODE, RSNCODE, and LOSTSESS values. The problem could be in the IMSplex network. Check for other messages from SCI, the IMS Connect instances, or TCP/IP that might help with the diagnosis. Collect the X'6701' error records from the IMS log.