Sense code 0888

Name conflict: A name specified in an RU is unknown, or is known and does not have the required capabilities, or is a duplicate resource for the specified resource type. When a name conflict is detected, further name checking ceases; multiple name conflicts are not reported or detected.

Bytes 2 and 3 following the sense code contain sense-code-specific information.

VTAM® hint: Sense code 0888000n might be issued when an attempt to establish a session fails in an intermediate VTAM along the session setup path. This error might occur because the intermediate VTAM that set the sense code is operating with NQNMODE=NAME or is a pre-V4 VTAM. Therefore, the intermediate VTAM cannot define multiple resources with the same name even though the network identifiers are different.

Change the intermediate domain to operate with NQNMODE=NQNAME to allow definition of multiple resources with the same name and different network identifiers, or reroute the session through another path.
0000
No specific code applies.

VTAM Information: When VTAM receives this sense code for a session initiation, it continues searching through the adjacent SSCP table until the destination LU is found or routing is exhausted.

0001
The specified DLU real network name is known, but identifies a resource that is not LU-LU session capable.

VTAM Information: When VTAM receives this sense code for a session initiation, it continues searching through the adjacent SSCP table until the destination LU is found or routing is exhausted.

VTAM hint: A possible cause of this error is a duplicate resource in the same network.

0002
The specified DLU alias network name is known, but identifies a resource that is not LU-LU session capable.

VTAM Information: When VTAM receives this sense code for a session initiation, it continues searching through the adjacent SSCP table until the destination LU is found or routing is exhausted.

0003
The specified OLU real network name is known, but identifies a resource that is not LU-LU session capable.

VTAM Information: When VTAM receives this sense code for a session initiation, it continues searching through the adjacent SSCP table until the destination LU is found or routing is exhausted.

0004
The specified OLU alias network name is known, but identifies a resource that is not LU-LU session capable.

VTAM Information: When VTAM receives this sense code for a session initiation, it continues searching through the adjacent SSCP table until the destination LU is found or routing is exhausted.

0005
Name translation was not valid; that is, a different LU name was returned with the same network ID as the original LU name.
0006
The specified DLU real network name is known, but is a duplicate resource.

VTAM Information: When VTAM receives this sense code for a session initiation, it continues searching through the adjacent SSCP table until the destination LU is found or routing is exhausted.

VTAM hint: Possible causes of this error include, but are not limited to, the following ones:
  • The same resource has been defined in the network in more than one location.
  • If the origin LU is in APPN, this sense code can be issued if the destination resource has moved and the new location is not known throughout the network. This situation will be corrected when the origin LU receives this sense code and discards the incorrect information.
  • If a LEN connection is being used, a possible cause of this error is that the network ID predefined for the cross-domain resource is the same as the network of the LEN connection but is not the same as the network where the resource resides. To fix this, move the CDRSC definition statement for the resource before any NETWORK definition statements so that the resource does not have a predefined network ID.
0007
The specified DLU alias network name is known, but is a duplicate resource.

VTAM Information: When VTAM receives this sense code for a session initiation, it continues searching through the adjacent SSCP table until the destination LU is found or routing is exhausted.

VTAM hint: A possible cause of this error is that VTAM is unable to determine the DLU real name for a TR_REPLY RU. Ensure that the network ID is correct. To determine where the error occurred, look in the alias translation table for the alias name and the real name associated with it. Find the name that was given as the DLU alias name in IST664I and try to determine what the actual resource is in this host.

See z/OS Communications Server: SNA Network Implementation Guide for a description of alternatives to predefining cross-network destination logical units.

0008
The specified OLU real network name is known, but is a duplicate resource.

VTAM Information: When VTAM receives this sense code for a session initiation, it continues searching through the adjacent SSCP table until the destination LU is found or routing is exhausted.

0009
The specified OLU alias network name is known, but is a duplicate resource.

VTAM Information: When VTAM receives this sense code for a session initiation, it continues searching through the adjacent SSCP table until the destination LU is found or routing is exhausted.

000A
A predefined real resource name and a predefined alias resource name were found for the same resource.
000B
A cross-network DLU name is defined as a shadow resource, but shadow resources are not supported for cross-network sessions.

VTAM Information: When VTAM receives this sense code for a session initiation, it continues searching through the adjacent SSCP table until the destination LU is found or routing is exhausted.

000C
A cross-domain or cross-network DLU name matches an alternate application name. However, the alternate application name is not the real name of the resource. This is only allowable in a same-domain session.

VTAM Information: When VTAM receives this sense code for a session initiation, it continues searching through the adjacent SSCP table until the destination LU is found or routing is exhausted.

000D
When processing a session initiation RU, an SSCP has found two different resource definitions for the OLU, one with the real OLU name and one with the alias OLU name.
000E
When processing a session initiation RU, an SSCP has found two different resource definitions for the DLU, one with the real DLU name and one with the alias DLU name.
000F
The specified DLU network name is defined as a generic resource. The session should be reinitiated using the name of an LU.

VTAM hint: This sense code is issued in connection with generic resources and the centralized definition of cross-domain resources function.

For an overview of centralized definition of cross-domain resources and information about how to set up these definitions, see z/OS Communications Server: SNA Network Implementation Guide.

0010
The LU 6.2 partner returned a name in the User Data field of its RSP(BIND) that differs from the name it returned in the User Data field of its RSP(BIND) for a previous BIND. Either the partner changed its name or name changes in the network have caused delivery of the latest BIND to a different partner.
VTAM hint: Possible causes of this error include, but are not limited to, the following ones:
  • The partner LU might have changed names or name changes in the network have caused delivery of the latest BIND to a different partner LU.
  • Name manipulations in the network are inconsistent or the network is finding different targets for the same name on subsequent BINDS.
  • A partner LU incorrectly using the sender's name might have caused a problem.
0011
The LU 6.2 partner receiving a BIND carrying one specific target SLU name returned a name in the User Data field of its RSP(BIND) that is the same as it returned in response to a previous BIND carrying a different target SLU name.

VTAM Information: The partner LU name returned in the user data field of the BIND response was found in a VARIANT_NAME entry, but the SUPPLIED_ NAME entry used when the session was initiated indicates (by the associated name field) that no name associated has taken place. The name returned in the user data field of a BIND response found in a SUPPLIED_NAME LU entry is different from the SUPPLIED_NAME entry used in the setup of the session.

VTAM hint: A possible cause of this error is that the name returned is identical to a name currently in an internal table as a name that has already been supplied by the application.

0012
A session initiation request is received from the partner LU containing a LUNAME found in an internal table, but with a different network qualifier.

VTAM Information: Name changes in the network have caused alteration of the network identifier.

VTAM hint: Possible causes of this error include, but are not limited to, the following ones:
  • The local LU does not support network-qualified names.
  • A non-flat name space was detected where a flat name space is required.
0013
A border node received a topology database update (TDU) from a node within its local subnet containing the CP name of a node that is adjacent to the border node across an intersubnet TG.
0014
An excessive number of topology database updates (TDUs) have been processed for a resource.
0015
A generic name of a resource has been received when only the real name of the resource can be specified.
0016
The DLUR-specified network name is known, but is a duplicate resource.
Parent topic: 08XX (request reject)