Recovering from remote logical unit failure
When a series of conversation or change number of sessions (CNOS) failures occur from a remote logical unit (LU), you need to recover from this situation.
Symptoms
Message DSNL501I is issued when a CNOS request to a remote LU fails. The CNOS request is the first attempt to connect to the remote site and must be negotiated before any conversations can be allocated. Consequently, if the remote LU is not active, message DSNL501I is displayed to indicate that the CNOS request cannot be negotiated. Message DSNL500I is issued only once for all the SQL conversations that fail as a result of a remote LU failure.
Message DSNL502I is issued for system conversations that are active to the remote LU at the time of the failure. This message contains the VTAM® diagnostic information about the cause of the failure.
Environment
Any application communications with a failed LU receives a message to indicate a resource-unavailable condition. Any attempt to establish communication with such an LU fails.Resolving the problem
System programmer response: Communicate with the other involved sites regarding the unavailable-resource condition, and request that appropriate corrective action be taken. If a DSNL502 message is received, activate the remote LU, or ask another operator to do so.