Function not supported: The function requested is not
supported. The function might have been specified by a formatted request
code, a field in an RU, or a control character.
Note: Numbers 0001 and 0002 are also assigned for implementation.
See the implementation documentation for details of use.
Bytes 2 and 3 following the sense code contain sense code
specific information.
- 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.
VTAM hint: If resources are
not activating correctly when a new NCP is activated, either rename
the new NCP or use another method to make sure that the old resource
resolution table (RRT) is replaced with the new RRT.
- 0001
- The half-session receiving the request did not perform the function
because it is not capable of doing so. The requesting half-session
requested a function that the receiver does not support, and the receiver
did not specify that it was capable of supporting the function at
session activation; consequently, there is an apparent mismatch of
half-session capabilities.
Note: This is to cover a system error.
For example, if the PU receiving a SETCV (vector key=X'15')
is not a gateway PU; that is, if the PU did not indicate in the ACTPU
response that it is a gateway PU, the PU reports to the SSCP that
sent the SETCV that there is an apparent mismatch of half-session
capabilities.
- 0002
- The half-session receiving the request did not perform the function,
though it is capable of doing so. The requesting half-session did
not specify at session activation that it was capable of supporting
the function; consequently, there is an apparent mismatch of half-session
capabilities.
Note: This is to cover a system error. For example,
if the SSCP sending a SETCV (vector key=X'15') is not known
to the receiving PU as a gateway SSCP; that is, the SSCP did not indicate
in ACTPU that it is a gateway SSCP, the PU reports a mismatch of capabilities.
- 0003
- The component received an unsupported normal-flow DFC command.
- 0004
- The component received an unsupported expedited-flow DFC command.
For example, the LU 6.2 half-session might have received a SIGNAL
RU when its local conversation style is full-duplex. (However, the
half-session rejects the SIGNAL only if it is for the current bracket.
Early SIGNALs are held for the correct bracket by saving the SIGNAL
value until the correct BB arrives.)
- 0005
- The component received a network control command during an LU-SSCP
session.
- 0006
- The component received an unsupported session control command
during an LU-SSCP session.
- 0007
- The component received an unsupported data flow control command
with LU-SSCP session specified.
- 0008
- Broadcast search with reservation: An NNCP received a broadcast
search request with reservation.
- 0009
- Initiate type: The initiate type requested in the CDINIT GDS
variable or INIT_OTHER_CD GDS variable is not supported at the receiver.
- 000A
- Session polarity: The session polarity requested in the CDINIT GDS
variable is not supported at the receiver.
- 000B
- A BIND specifying delayed request mode was received from a non-6.2
Type LU, but delayed request mode is not supported in the receiver.
- 000C
- A stand-alone BIND is received from a node that is served by an
SSCP that does not support stand-alone BINDs.
- 000D
- The function identified in the request is not supported by the
processing application transaction program.
- 0010
- The RU is not known to session services.
- 0011
- A session key is not supported.
- 0012
- A control vector is not supported.
- 0014
- Cryptography is not supported but a nonzero length was specified
for the cryptography key.
- 0015
- Queuing not supported for a controller session.
- 0016
- Service parameter not supported. When this SNA report code is
used in an SNA condition report, it is accompanied by a supplemental
report identifying the service parameter triplet (or triplets) that
was not supported.
- 0017
- Service parameter level not supported. When this SNA report code
is used in an SNA condition report, it is accompanied by a supplemental
report identifying the service parameter triplet (or triplets) that
was not supported.
- 0018
- Destination-role function not supported. When this SNA report
code is used in an SNA condition report, it is accompanied by a structure
report identifying the structure and containing the contents that
specified the unsupported function. Whenever the structure report
is not sufficient to identify the unsupported functions, the supplemental
report might also be present.
- 0019
- All-role function not supported. When this SNA report code is
used in an SNA condition report, it is accompanied by a structure
report identifying the structure and containing the contents that
specified the unsupported function. Whenever the structure report
is not sufficient to identify the unsupported functions, the supplemental
report might also be present.
- 001B
- Unable to initiate agent.
- 001C
- Function conflicts with Format Set 1 encodings. When this SNA
report code is used in an SNA condition report, it is accompanied
by a structure report identifying the structure and containing the
contents that specified the conflicting function.
- 001F
- Multiple-destination traffic not supported. The reporting location
is a specialized, end-only role implementation that supports single-destination
traffic only.
- 0020
- A session initiation request specified an OLU and DLU that are
the same LU. An LU that does not use VTAM LU
6.2 API cannot establish a session with itself.
- 0021
- There is a mismatch between session initiation request type and
LU type (independent or dependent). For example, a session initiation
request other than BFINIT identifies an independent LU as a session
partner.
VTAM hint: Ensure
that the PU name and CPNAME operand have unique names in the PU definition
statement of the switched major node definition.
- 0023
- A session initiation request requiring Extended Session Services
NNS Support was received at an EN that does not have this service
available to it.
- 0025
- The component received a NOTIFY request whose type is not supported.
- 0027
- LU type is not supported.
VTAM hint: This
sense code can be displayed in a VTAM message,
but is set by another product. See the appropriate product-specific
manual for further information.
- 0036
- The network node server received a NOTIFY request whose type is
not supported by the DLU.
- 0037
- Request received is inappropriate for the receiving type of network
addressable unit.
- 0039
- A third-party-initiated session request specified an ILU (initiating
LU) and a DLU (destination LU) that are the same LU. An application
cannot initiate a third-party-initiated session to itself.
- 6002
- The resource identified by the destination program name (DPN)
is not supported.
- 6003
- The resource identified by the primary resource name (PRN) is
not supported.
Note: This sense code can also be used instead of
sense code X'0826'.