DFS3218 INVALID RESTART MESSAGE OR RESTART RESPONSE MESSAGE RECEIVED RSN=xxyy, LINK link#

Explanation

The MSC link was restarted. During the exchange of the restart messages, an invalid or unexpected message was detected, or the values in the restart message indicated incompatible MSC link definitions between the partner IMS systems.

In the messages:
xx
Identifies the module.
01
DFSCM7D0, a VTAM® restart routine
02
DFSCMSW0, the CTC or MTM restart routine
03
DFSCM7A0, a VTAM restart routine
04
DFSCM7B0, a VTAM restart routine
05
DFSTC7B0, a TCP/IP restart routine
yy
Reason code.
01
The partner IMS release is zero or invalid. MSC generally supports two lower or higher versions; for example, Version 10 supports Versions 8 and 9 and two higher versions. Ensure that the partner is a supported release. If the releases are supported, this problem is an IMS internal error.
02
The partner IMS does not support extended prefixes. Extended prefix support was introduced in IMS Version 5 and is required if you are connecting to an IMS Version 8 or above. Ensure that the partner is a supported release. If the release is supported, this problem is an IMS internal error.
03
The partner IMS ID is invalid. Both sides of the link must have the same two-character partner ID.
04
An invalid restart message was detected; likely the restart message ID is invalid. This problem is an IMS internal error.
05
Bandwidth is incompatible. The partner IMS systems must both be either BANDWIDTH (OFF) or BANDWIDTH (ON).
06
Invalid FMH5. For MSC VTAM, the restart message must be proceeded by an FMH5 block. This problem is an IMS internal error.
07
FMH5 contained an invalid DPN field. For MSC VTAM, the FMH5 block must have DFSCMS00. This problem is an IMS internal error
08
The buffer sizes were not equal. Both sides of the link must have the same MSLINK buffer size.
09
An error occurred getting storage during bandwidth restart for a QMBA or QLST block used by QMGR. This problem most likely is an insufficient storage error. If not, then it is an IMS internal error.
10
V10 VTAM link encountered an error rebuilding the buffers and VTAM control blocks were compatible with the Version 8 or Version 9 partner. This problem might be an IMS internal error.
11
An attempt was made to start a logical link on an MSC TCP/IP physical link that specifies the generic IMS ID of a TCP/IP generic resource group, but parallel logical links are already active or in ERE status on another physical link that specifies the IMS ID of the IMS system. All physical links to the same IMS system must specify either the same generic IMS ID of a TCP/IP generic resource group or the IMS ID of the IMS system.
12
An attempt was made to start a logical link on an MSC TCP/IP physical link that specifies the IMS ID of the IMS system, but parallel logical links are already active or in ERE status on another physical link that specifies the generic IMS ID of a TCP/IP generic resource group. All physical links to the same IMS system must specify either the same generic IMS ID of a TCP/IP generic resource group or the IMS ID of the IMS system.
13
An attempt was made to start a logical link on an MSC TCP/IP physical link that specifies a generic IMS ID of a TCP/IP generic resource group, but the IMS system has active physical links that specify conflicting IMS ID values. All physical links to the same IMS system must specify either the same generic IMS ID of a TCP/IP generic resource group or the IMS ID of the IMS system. This problem is an internal logic error.
14
An attempt was made to start a logical link on an MSC TCP/IP physical link that specifies the IMS ID of the IMS system, but the IMS system has active physical links that specify conflicting IMS ID values. All physical links to the same IMS system must specify either the same generic IMS ID of a TCP/IP generic resource group or the IMS ID of the IMS system. This problem is an internal logic error.
15
An attempt was made to start a logical link on an MSC TCP/IP physical link that specifies a generic IMS ID of a TCP/IP generic resource group, but the STOGENLGN status is set for the physical link in either the local IMS system or the remote IMS system.
16
An attempt was made to start a logical link on an MSC TCP/IP physical link, but the STOLGN status is set for the physical link in either the local IMS system or the remote IMS system.
17
The value of the GENIMSID= parameter in IMS DFSDCxxx PROCLIB member and the value of the GENIMSID= parameter in the IMS Connect PROCLIB member are not the same. Applies to MSC TCP/IP links.
18
The GENIMSID= parameter in the IMS DFSDCxxx PROCLIB member is not specified, but the value of the GENIMSID= parameter in IMS Connect HWSCFGxx PROCLIB member is not blanks.
19
A remote partner IMS system attempted to logon to an IMS system in a TCP/IP generic resource group by using an IMS ID. To logon to an IMS system in a TCP/IP generic resource group, remote IMS systems must use the generic IMS ID of the TCP/IP generic resource group, as specified on the GENIMSID parameter of the DFSDCxxx PROCLIB members of the participating IMS systems.
20
The GENIMSID in parmlib member DFSDCxxx was the same value as either the real subsystem ID (IMSID) or the XRF resource name (RSENAME). These must be different.
21
A restart message was received from a remote IMS to a XRF alternate IMS. The restart was rejected with a DFS3218 RSN=0521. This event is a normal condition in a XRF environment using a GENIMSID. The error condition was issued internally to notify IMS Connect to reject this restart. The restart message to the active IMS will be accepted. This message is not issued to the MTO.
link#
Identifies the link.

System action

IMS prevents the link from starting.

Operator response

Refer to the reason code for possible causes and actions. The DFS3218 reason codes are also documented in the DFSKEYRC macro.

Use the QUERY MSLINK, /DISPLAY LINK, or /DISPLAY LINK OPTION BUFSIZE command on each side of the link to determine whether the links are compatible. If error is due to incompatible link parameters, use the UPDATE MSLINK or /UPDATE MSLINK command to set the parameters compatible. Notify the system programmer if the error persists.

System programmer response

If the error is not due to incompatible link options between this side of the link and its partner, or the incompatibility cannot be determined or corrected with the UPDATE MSLINK command, analyze the 6701 MSSx log records produced when the error occurred.

To print the type 6701-MSSx (x = 1, 2, 3, and 4) log records, use the DFSERA10 log print utility with the following control cards:
CONTROL CNTL
OPTION PRINT O=5,V=6701,L=2,C=M,E=DFSERA30
OPTION PRINT O=9,V=MSS,L=3,T=C,C=E,E=DFSERA30

If the error is related to the use of TCP/IP generic resources, make sure that all MSC TCP/IP physical links to the IMS systems specify either the generic IMS ID of the TCP/IP generic resource group, or the IMS ID of the IMS system. If the link you are starting uses TCP/IP generic resources, you might try directing the link to another IMS system in the TCP/IP generic resource group.

If the error is related to any of the following link statuses, issue the /RSTART LINK command or the UPDATE MSPLINK command with either the START(LOGON) or the START(GENLOGON) keyword:
  • PSTOPPED
  • PSTOPGEN
  • STOLGN
  • STOGENLGN

The type-1 /PSTOP MSPLINK command sets the appropriate stop status, either PSTOPPED or PSTOPGEN, depending on the specification of the GENIMSID parameter in the DFSDCxxx PROCLIB member. If status is ACTIVE, PSTOPGEN is set, if DISABLED, PSTOPPED is set. This status can be displayed by either the /DISPLAY ASMT MSPLINK or QUERY MSPLINK NAME(msplink_name) SHOW(STATUS) commands.

Problem determination

1, 5, 6, 7, 17b

Module

DFSCMSW0, DFSCM7D0, DFSCM7A0, DFSCM7B0, DFSTC7B0