RNAA request error: The RNAA must be rejected because there is
a mismatch between sending and receiving system definitions, or capabilities.
Bytes 2 and 3 following the sense code contain sense code specific
information.
- 0000
- No specific code applies.
- 0001
- No available pre-ENA addresses: Reject an RNAA that requests
an address that is pre-ENA compatible, and there are no pre-ENA addresses
available.
- 0002
- RNAA takeover error: In a takeover situation, a system definition
mismatch was detected between the "old" SSCP and the SSCP taking
over. For example, if the LU name field in the RNAA is not the same
as the LU name field in the logical unit block (LUB), the RNAA is
rejected. If an existing LU with the same local address is found,
but the LU is generated (instead of DR-added), the RNAA is rejected.
Also, if the adjacent link station (ALS) name given in the RNAA does
not agree with the ALS name given in the common physical unit block
(CUB), the RNAA is rejected.
- 0003
- NETID not valid: If the NETID field in the RNAA is not the
same as the native network ID, the RNAA is rejected. There is likely
a mismatch between the PU Type 4 and SSCP system definitions.
- 0004
- PU or LU type not valid: If the PU to which the LUs are to
be added is not Type 1 or Type 2, the RNAA is rejected. The SSCP
attempts to add an LU to a PU, but NCP has defined that PU as a PU
Type 4. The second situation is if the SSCP sent an RNAA Type X'00' or X'05' with
a PU or LU specified. This is an RU-NAU mismatch caused by an SSCP-NCP
definition mismatch.
- 0005
- MAXSUBA required for pre-ENA address assignment: If MAXSUBA
is not specified and an RNAA requesting a pre-ENA address is received,
the RNAA is rejected.