DFS3177E MSC DETECTED AN ERROR, active_process, RETCODE = rc, RSNCODE = rsn, LOSTSESS = cause, MODULE =m, LINK = nnn, linkname

Explanation

The MSC TCP/IP device dependent module (DDM) detected an error while processing a message or request associated with the MSC logical link identified in the message text.

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 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 SCI instance that is managing communications between the local IMS system and the local IMS Connect instance terminated unexpectedly.
SCISTOP
The SCI instance that is managing communications between the local IMS system and the local IMS Connect instance was shut down.
linkname
The name of the affected MSC logical link.
nnn
The number of the affected MSC logical link.
rc
The return code issued by the MSC DDM. The MSC DDM return and reason codes that are associated with this message are documented in the following table.
rsn
The reason code issued by the MSC DDM. The MSC DDM return and reason codes that are associated with this message are documented in the following table.
Possible cause: The possible cause is indicated by the return and reason codes included in the message text.

IMS MSC DDM return and reason codes for message DFS3177E

The following return and reason codes are also listed in the SCIWORK DSECT in the DFSMSCWA macro in the IMS.SDFSMAC data set.

Return code Reason code Meaning
DFSPOOL RC X'00000004' DFSPOOL GET storage error
DFSPOOL RC X'00000008' DFSPOOL release storage error
CELL POOL RC X'0000000C' Cell pool (CPOOL) get error
CELL POOL RC X'00000010' Cell pool (CPOOL) free error
  X'00000014' Invalid post code or post condition detected
  X'00000018' Invalid AWE detected
  X'0000001C' Invalid MSC directive (DFSMSDIR) detected
  X'00000020' Invalid buffer header control block (BUFMSHDR) detected
  X'00000024' Invalid message control block (BUFMSCB) detected
  X'00000028' Immediate shutdown request received from partner IMS
  X'0000002C' Invalid or unexpected MSC Link (MSLINK) status detected
  X'00000030' Unexpected bracket initiation stop (BIS) message received
  X'00000034' Unexpected error message control block (BUFMSCB) received
  X'00000038' Invalid restart message control block (BUFMSCB) received
  X'0000003C' Invalid shutdown message control block (BUFMSCB) received
  X'00000040' Unexpected return code received from internal routine
  X'00000044' SCIWORK area error
  X'00000048' Queue error detected (CTB5QERR set)
  X'0000004C' Queue buffer chaining error detected
  X'00000050' AWE chaining error detected
  X'00000054' Output edit error
  X'00000058' Input edit error
QMGR RC X'0000005C' Unexpected return code from the message queue manager
  X'00000060' DFSMGPL macro error, message prefix bad
  X'00000064' Invalid response MSCB (BUFMSCB) received
  X'00000068' Invalid internal condition detected
  X'0000006C' Internal control block error
  X'00000070' Lost session error posted by SCI notify exit for SCI/ICON abends or /PSTOP LINK FORCE or UPDATE MSLINK STOP(COMM) OPTION(FORCE) command
  X'00000074' Cannot issue CSLSCMSG request because CSL is not initialized. Check CSLG= parameter on the IMS startup procedure. CSLG=000 is minimum required.
  X'00000078' CSLSCMSG request failed. Nonzero return code was returned by SCI on the request.
  X'000000FC' Undetermined error
  X'0000007C' (RSNOLLB) LXB was posted by the SCI MSG exit, DFSSXIN0, but the LXBTCLBP field was zero.
  X'00000080' (RSN_BUFFER) CSLSCBFR RELEASE request failed to free an SCI buffer. For more information about the RETCODE and RSNCODE codes, see the CSLSRR macro. For MSPLINK-related errors, the RETCODE and RSNCODE codes are stored in the LXBRET and LXBRSN fields of the LXB block. For MSLINK-related errors, the RETCODE and RSNCODE codes are stored in the CLBTEMP4 and CLBTEMP5 fields of the LLB block. These control blocks are logged in the 6701-MSS1 log record.
  X'00000084' (RSN_NOMSC) Message input routine DFSSXIN0 received an MSC TCPIP message, but no MSC was defined.
  X'00000088' (RSN_NOLLBS) Message input routine DFSSXIN0 received an MSC TCPIP message, but no MSC LLBs were defined.
  X'0000008C' (RSN_NOLXBS) Message input routine DFSSXIN0 received an MSC TCPIP message, but the target link had no available LXBs to start a session.
  X'00000090' (RSN_NOTCPIP) Message input routine DFSSXIN0 received an MSC TCPIP message but the target link was not of TCPIP type. For example, this error occurs when the target link is assigned to the MSPLINK type.
  X'00000094' (RSN_NOLCB) LLB was not assigned to an MSPLINK LCB control block.
  X'0000009C' (RSN_NOPRTNR) Message input routine DFSSXIN0 received an MSC TCPIP message, but no target link was found for the specified partner ID.
Return code Reason code Meaning
DFSPOOL RC X'00000004' DFSPOOL GET storage error
DFSPOOL RC X'00000008' DFSPOOL release storage error
CELL POOL RC X'0000000C' Cell pool (CPOOL) get error
CELL POOL RC X'00000010' Cell pool (CPOOL) free error
  X'00000014' Invalid post code or post condition detected
  X'00000018' Invalid AWE detected
  X'0000001C' Invalid MSC directive (DFSMSDIR) detected
  X'00000020' Invalid buffer header control block (BUFMSHDR) detected
  X'00000024' Invalid message control block (BUFMSCB) detected
  X'00000028' Immediate shutdown request received from partner IMS
  X'0000002C' Invalid or unexpected MSC Link (MSLINK) status detected
  X'00000030' Unexpected bracket initiation stop (BIS) message received
  X'00000034' Unexpected error message control block (BUFMSCB) received
  X'00000038' Invalid restart message control block (BUFMSCB) received
  X'0000003C' Invalid shutdown message control block (BUFMSCB) received
  X'00000040' Unexpected return code received from internal routine
  X'00000044' SCIWORK area error
  X'00000048' Queue error detected (CTB5QERR set)
  X'0000004C' Queue buffer chaining error detected
  X'00000050' AWE chaining error detected
  X'00000054' Output edit error
  X'00000058' Input edit error
QMGR RC X'0000005C' Unexpected return code from the message queue manager
  X'00000060' DFSMGPL macro error, message prefix bad
  X'00000064' Invalid response MSCB (BUFMSCB) received
  X'00000068' Invalid internal condition detected
  X'0000006C' Internal control block error
  X'00000070' Lost session error posted by SCI notify exit for SCI/ICON abends or /PSTOP LINK FORCE or UPDATE MSLINK STOP(COMM) OPTION(FORCE) command
  X'00000074' Cannot issue CSLSCMSG request because CSL is not initialized. Check CSLG= parameter on the IMS startup procedure. CSLG=000 is minimum required.
  X'00000078' CSLSCMSG request failed. Nonzero return code was returned by SCI on the request.
  X'000000FC' Undetermined error
  X'0000007C' (RSNOLLB) LXB was posted by the SCI MSG exit, DFSSXIN0, but the LXBTCLBP field was zero.
  X'00000080' (RSN_BUFFER) CSLSCBFR RELEASE request failed to free an SCI buffer. For more information about the RETCODE and RSNCODE codes, see the CSLSRR macro. For MSPLINK-related errors, the RETCODE and RSNCODE codes are stored in the LXBRET and LXBRSN fields of the LXB block. For MSLINK-related errors, the RETCODE and RSNCODE codes are stored in the CLBTEMP4 and CLBTEMP5 fields of the LLB block. These control blocks are logged in the 6701-MSS1 log record.
  X'00000084' (RSN_NOMSC) Message input routine DFSSXIN0 received an MSC TCPIP message but no MSC was defined.
  X'00000088' (RSN_NOLLBS) Message input routine DFSSXIN0 received an MSC TCPIP message but no MSC LLBs were defined.
  X'0000008C' (RSN_NOLXBS) Message input routine DFSSXIN0 received an MSC TCPIP message but the target link had no available LXBs to start a session.
  X'00000090' (RSN_NOTCPIP) Message input routine DFSSXIN0 received an MSC TCPIP message but the target link was not of TCPIP type. For example, this error occurs when the target link is assigned to the MSPLINK type.
  X'00000094' (RSN_NOLCB) LLB was not assigned to an MSPLINK LCB control block.

System action

The MSC link connection is terminated and placed in the PSTOPPED IDLE ERE state. IMS logs type 6701-MSS1, MSS2, and MSS3 records.

IMS attempts 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.

Output destination

The z/OS system console and the IMS 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 x 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 module identified in the message text is where the error occurred. Check for other messages from SCI, IMS Connect, or TCP/IP to 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