DFS3176E IMS CONNECT ERROR MESSAGE RECEIVED, active_process, RETCODE = rc, RSNCODE = rsn, LOSTSESS = cause, MODULE =m, LINK = nnn, linkname
Explanation
IMS Connect detected an error while processing a request or message from MSC and returned a non-zero return or reason code to IMS. The error might have been detected by either the local IMS Connect instance or the remote IMS Connect instance. The error message is returned to the local IMS system that issued the request or message.
In the
message text:
- active_process
- The MSC process that was active when the error occurred. Possible values include:
- RESTART
- When IMS Connect encountered the error, MSC was attempting to notify IMS Connect and the remote IMS system of the restart of the logical link identified in the message text.
- SENDMSG
- When IMS Connect encountered the error, MSC was attempting to send an MSC message to a remote IMS system by way of the logical link identified in the message text.
- SHUTDOWN
- When IMS Connect encountered the error, MSC was attempting to notify IMS Connect and the remote IMS system that the logical link is shutting down.
- UNKNOWN
- Displayed when the error occurred during an unidentifiable MSC 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:
- FORCESTO
- A /PSTOP LINK FORCE or UPDATE MSLINK STOP(COMM) OPTION(FORCE) command was issued by the operator.
- 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.
- STOPCLNT
- The receive socket between a local IMS Connect instance and a remote IMS Connect instance was
terminated.The following list includes some of the possible causes:
- An IMS Connect STOPCLNT command or its equivalent type-2 UPDATE command was issued.
- An IMSplex, MSC, or RMTIMSCON entity in a remote IMS Connect was stopped.
- A remote IMS Connect was terminated.
- A remote IMS was terminated.
- STOPIP
- The communication between a local IMS Connect instance and an IMSplex was stopped. This is caused by an IMS Connect STOPIP command or its equivalent type-2 UPDATE command.
- STOPLINK
- The MSC logical link in a local IMS Connect instance was stopped. This is caused by an IMS Connect STOPLINK command or its equivalent type-2 UPDATE command.
- STOPMSC
- The MSC physical link in a local IMS Connect instance was stopped. This is caused by an IMS Connect STOPMSC command or its equivalent type-2 UPDATE command.
- STOPRMT
- The communication between a local IMS Connect instance and a remote IMS Connect instance was stopped. This is caused by an IMS Connect STOPRMT command or its equivalent type-2 UPDATE command.
- linkname
- The name of the affected MSC logical link.
- nnn
- The number of the affected MSC logical link.
- rc
- The return code issued by IMS Connect. The IMS Connect return and reason codes that are associated with this message are documented in the following table. These and other IMS Connect return and reason codes are also documented in the HWSHRR macro.
- rsn
- The reason code issued by IMS Connect. The IMS Connect return and reason codes that are associated with this message are documented in the following table.
| Return code | Reason code | Meaning |
|---|---|---|
| X'0C000018' | X'00006000' | Receive from IMS failed. |
| X'00006004' | Link not found. | |
| X'00006008' | Link being restarted is already restarted. | |
| X'0000600C' | Failed to get a send socket. | |
| X'00006010' | Invalid directive received on the CSLSCMSG request. | |
| X'00006014' | IMS Connect failed to get a link block. | |
| X'00006018' | The local IMS Connect instance detected an invalid restart link request. | |
| X'0000601C' | The local IMS Connect could not restart a link because IMS Connect is disconnected from MSC. | |
| X'00006020' | The local IMS Connect could not restart a link because MSC is not active. | |
| X'00006024' | The local IMS Connect could not restart a link because the restart request contains an invalid IMS ID for the local IMS system. | |
| X'00006028' | The local IMS Connect detected an invalid link shutdown request. | |
| X'0000602C' | The local IMS Connect could not shutdown a link because IMS Connect is disconnected from MSC. | |
| X'00006030' | The local IMS Connect could not shutdown a link because MSC is not active. | |
| X'00006034' | The local IMS Connect could not restart a link because the shutdown request contains an invalid IMS ID for the local IMS system. | |
| X'00006038' | The local IMS Connect instance received an invalid message from MSC. | |
| X'0000603C' | IMS Connect cannot process a message from the remote MSC because the local MSC is disconnected. | |
| X'00006040' | IMS Connect cannot process a message from the remote MSC because the local MSC is not active. | |
| X'00006044' | IMS Connect cannot process a message from the remote MSC because the message contains an invalid IMS ID. | |
| X'00006048' | An attempt was made to start a logical link, but the value of the GENIMSID parameter in the DFSDCxxx PROCLIB member of the IMS system does not match the value of the GENIMSID parameter in the corresponding MSC configuration statement in the IMS Connect configuration PROCLIB member. The start request is rejected. To resolve the problem, make the two GENIMSID values match. | |
| X'0000604C' | An attempt was made to start a logical link from an IMS system that
does not specify the GENIMSID parameter to enable TCP/IP generic resources, but the MSC
definitions for the link in IMS Connect do specify the GENIMSID parameter for TCP/IP
generic resources. IMS Connect rejected the restart link request. You can resolve the
problem in one of the following ways:
|
|
| X'00006050' | An attempt was made to start a logical link from an IMS system in a
TCP/IP generic resource group, but one or more logical links that use the same physical
link already have affinity with another IMS system in the TCP/IP generic resource group.
IMS Connect rejected the start request. To resolve the problem, either restart the logical link from the IMS system in the TCP/IP generic resource group that has affinity, or terminate the logical links on the other IMS system and, after IMS Connect has cleared the existing affinities, restart the link on this IMS system. |
|
| X'00006054' | The IMS system notified IMS Connect that it would accept a restart link request from a remote IMS system, but another IMS system in the TCP/IP generic resource group already accepted the link request. IMS Connect rejected the notification of acceptance from this IMS system. This is not an error. | |
| X'00006058' | The local IMS Connect could not shutdown a link because the specified link is not found. Check for any IMS Connect HWSF3355E message. | |
| X'0000605C' | An attempt was made to start a logical link from an IMS system that
specifies the GENIMSID parameter to enable TCP/IP generic resources, but the MSC
definitions for the link in IMS Connect do not specify the GENIMSID parameter for TCP/IP
generic resources. IMS Connect rejected the restart link request. You can resolve the
problem in one of the following ways:
|
|
| X'00006100' | Send to the remote IMS Connect failed. | |
| X'00006200' | The receive failed on the TCP/IP read from a remote IMS Connect instance. | |
| X'00006204' | Send to data store failed. This is most likely an internal error. | |
| X'00006300' | Send to IMS failed. The remote IMS system is probably not available. | |
| X'00006400' | An MSC link was stopped in the local IMS Connect instance by a STOPLINK command. | |
| X'00006404' | MSC communications stopped in the local IMS Connect instance by a STOPMSC command. | |
| X'00006408' | Communications on a connection to a remote IMS Connect instance was stopped in the local IMS Connect by a STOPRMT command. | |
| X'0000640C' | Communications with the local IMSplex was stopped in the local IMS Connect by a STOPIP command. | |
| X'00006410' | IMS Connect shutdown. |
System action
The MSC link connection is terminated and placed in the PSTOPPED IDLE ERE state. IMS writes type 6701-MSS1, MSS2, and MSS3 records.
Depending on the status of the connection to the remote IMS system, IMS might attempt to notify the remote IMS system. If notification is successful, the remote IMS system terminates the logical link, places the link in the PSTOPPED IDLE ERE state, and issues message DFS2169I DISCONNECTION COMPLETED ON LINK xxx at the remote site.
If the notification is not successful and the link remains in an IDLE ACTIVE state at the remote site, a /PSTOP LINK xxx FORCE or UPDATE MSLINK NAME(linkname) STOP(COMM) OPTION(FORCE) might need to be issued to terminate the link.
Even if the notification to the remote system is not successful, the notification to the local IMS Connect might succeed, in which case the local IMS Connect cleans up the associated sockets.
Output destination
The z/OS system console and the master terminals.
System programmer response
If the remote IMS system could not be notified of the termination of the logical link, someone might need to issue a /PSTOP LINK xxx FORCE or UPDATE MSLINK NAME(linkname) STOP(COMM) OPTION(FORCE) at the remote site.
Determine the cause of the error from the RETCODE, RSNCODE, and LOSTSESS values. The problem could be in either the local or remote 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.
After the cause of the error is corrected, restart the link.
Module
| Module | Description |
|---|---|
| DFSTCER0 | DFSxxxx message interface |
| DFSTCPE0 | Execute CSLSCMSG request |
| DFSTCP20 | Receive Post handler |
| DFSTCRC0 | Validate post codes |
| DFSTC1A0 | Send output controller |
| DFSTC1B0 | Send output buffer setup |
| DFSTC2A0 | Process send completion |
| DFSTC3A0 | Receive input controller |
| DFSTC4A0 | Process receive completion |
| DFSTC7A0 | Restart and shutdown router |
| DFSTC7B0 | Restart processor |
| DFSTC7C0 | Shutdown processor |
| DFSTC7D0 | Shutdown cleanup |
| DFSCMSG0 | Bandwidth output edit |
| DFSCMSP0 | Bandwidth input error message processor |
| DFSCMSR0 | Bandwidth response message builder |
| DFSCMSU0 | Bandwidth output buffer header builder |
| DFSCMSX0 | Bandwidth response message builder |
| DFSCMSZ0 | Bandwidth input message processor |
| DFSCMS00 | MSC analyzer |