DFS3213I REMOTE INITIATED LINK START FAILED, REASON CODE=nn. PARTNER ID xx. INITIATOR IS NODE nodename.
Explanation
A remote IMS system, identified by node (nodename)
and partner ID (xx), attempted to start a link
and failed for the following reason code (nn):
- Code
- Reason
- 04
- The Partner ID specified does not exist on this system, or the logical link for NODENAME = nodename could not be found.
- 08
- The Partner ID specified is under a different physical link on this system, or it exists, but is unassigned to a physical link.
- 12
- The maximum number of sessions has been reached for the associated local physical link.
- 16
- The associated local physical link has been PSTOPPED.
- 20
- The buffer size specified for the requested link is incompatible with partner's.
- 24
- Bind parameters received are invalid.
- 28
- There is a Primary to Secondary LU polarity mismatch. The side that came up cold was secondary at time of last session failure. Alternatively, if both sides came up warm, at least one of them restarted after the wrong checkpoint.
- 32
- The partner ID specified is already in session.
- 36
- Polarity mismatch. Both sides are requesting secondary LU status.
System action
IMS prevents the link from starting. Processing continues normally.
Operator response
Use a QUERY MSLINK or /DISPLAY
LINK command to determine the status of the link or links.
Depending on the reason code, continue as follows:
- Code
- Response
- 04
- Notify the system programmer.
- 08
- Use /DISPLAY ASMT to display logical-to-physical link assignments, and correct them with /MSASSIGN LINK or UPDATE MSLINK if in error. Notify the system programmer.
- 12
- Notify the system programmer.
- 16
- Restart the link from this system if a session is warranted.
- 20
- Notify the system programmer.
- 24
- Notify the system programmer. Try again from either system.
- 28
- Restart the partner with a warm restart (/ERE), cold restart both sides, or restart the link from this side, or restart following the correct checkpoint.
- 32
- Terminate the prior session using /PSTOP to stop the link or VARY NET INACT APPLID. Establishing a new session.
- 36
- Verify that both sides were restarted from the proper checkpoint. This problem can happen only if both sides are warm started. To get around the problem, one side must be either set to warm primary, or set to cold status.
System programmer response
Depends upon reason code, as follows:
- Code
- Response
- 04
- An IMS system definition is required.
- 08
- An IMS system definition might be required.
- 12
- An IMS system definition or temporary JCL change might be required if more sessions are warranted.
- 16
- Not applicable
- 20
- An IMS system definition is required.
- 24
- Take a VTAM® trace of the bind.
- 28
- None.
- 32
- If the link, in session status, is unwarranted, then create a memory dump. You might also have to run an IMS link trace and a VTAM trace to determine why the link is being left in the session.
- 36
- If the link, in session status, is unwarranted, then create a memory dump. You might also have to run an IMS link trace and a VTAM trace to determine why both links are requesting secondary status.