RU data error: Data in the request RU is not acceptable
to the receiving component; for example, a character code is not in
the set supported, a formatted data field is not acceptable to presentation
services, or a value specified in the length field (LL) of a structured
field is not valid.
VTAM® hint: This
code can also be issued if a required name in the request is omitted.
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.
- 0001
- The request contains a subarea address of zero or a subarea address
greater than the maximum subarea value within the specified or implied
network.
VTAM hint: A
possible cause of this error is that a network address cannot be assigned
to a dynamic application program when VTAM is
trying to build that dynamic application program from a model application
program definition.
- 0002
- The network ID specified in the ACTPU is unknown, or is not valid
on the link over which the ACTPU was received.
- 0003
- Isolated pacing message format error: An incorrectly formatted
isolated pacing message was received.
- 0005
- An RNAA Type 4 was received in which the local address field length
is greater than one. The implementation does not support a length
other than one.
- 0006
- An RNAA Type 4 was received in which the link station address
field length is greater than one. The implementation does not support
a length other than one.
- 0007
- On BFCINIT the network name portion of the network-qualified name
field has a format error.
- 0008
- A character code that is not valid was found.
- 0009
- The formatted data field is unacceptable to presentation services.
- 000A
- A length field for a structured field that is not valid was found.
- 000B
- The value in the name length field is not valid.
- 000C
- The value in the cryptography length field is too great.
- 000D
- The URC length field is not valid.
- 000E
- The control vector length field is inconsistent with the control
vector data.
- 000F
- A PLU or SLU role specification encoding is not valid.
- 0010
- The value in the user data length field is not valid.
- 0020
- Too many session keys are present.
- 0021
- A control vector or session key data is not valid.
- 0022
- A BIND image in a session services RU is not valid.
- 0023
- A device characteristics field is not valid.
- 0024
- A BIND or +RSP(BIND) that was not for LU Type 6.2 and not in extended
format was received at an intermediate APPN network node. The session
is terminated.
- 0026
- The length of GDS variable within the request RU is not valid.
- 0027
- A GDS variable within a locate is not valid.
- 0030
- Control vector ambiguity: The request contains two or more conflicting
control vectors. Generally the two control vectors have the same
key. However, there are cases where a new control vector key supersedes
an old one. In this case, two control vectors with different keys
but no other distinguishing data (such as network ID) could be ambiguous.
An example is a SETCV to a gateway node with both a VR ID list control
vector (control vector X'1B') and a route parameters control
vector (control vector X'4E') for the same network.
- 0033
- The name of the deciphering CP in a cryptography (X'63') control
vector does not match the name of the receiving CP(PLU).
- 0034
- A topology data update was received across an APPN subnetwork
link carrying topology information about an adjacent subnet.
VTAM hint: Information that
was not valid was received in a topology database update (TDU) over
an APPN subnetwork link. This sense code is set only by a border node
during the initial topology exchange after CP-CP sessions are established
over an APPN subnetwork link. If the non-native node sends a TDU containing
more topology information that its own X'44'/X'45' control
vector pair, then the sense code is set. A dump from both nodes should
be taken for problem determination.
- 0035
- A logon command was entered using a format different from that
specified at system-definition time for the USS table.
- 0036
- The message authentication code received in the RU did not match
the one generated by the receiver for that RU.
- 0037
- The data manipulation header contained data that was not valid.
- 0038
- The data manipulation header contained a length that was not valid.
- hnnn
- Where h≥8; that is, the high-order
bit in Byte 2 is set to one. The 15 low-order bits of Bytes 2 and
3 contain a binary count that indexes (zero-origin) the first byte
of the field found to be in error.