SNAX/APC Management Programming Manual

15: ZAPC-ERR-INV-DEV-TYPE
Error Numbers and Error Lists
111813 Tandem Computers Incorporated A–19
15: ZAPC-ERR-INV-DEV-TYPE
Either an unknown device type was specified, or the LU is a parallel-session LU but
the access method is not SNAX/APN.
ZSPI–TKN–ERRLIST token–type ZSPI–TYP–LIST.
ZSPI–TKN–ERROR token–type ZSPI–TYP–ERROR.
ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING
ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-STRING
ZSPI–TKN–ENDLIST token–type ZSPI–TYP–SSCTL.
ZSPI–TKN–ERROR
is the standard SPI error token, as described in the SPI Programming Manual. Its
value consists of the subsystem ID and the error number ZAPC–ERR–INV–DEV–
TYPE. This token is always present in the error list.
ZCOM-TKN-OBJNAME
is the first object name provided with the command on which the error occurred.
This token is always present in the error list, and is described in Section 4,
“Common Definitions.”
ZCOM-TKN-OBJTYPE
is the object type provided with the command on which the error occurred. This
token is always present in the error list, and is described in Section 4, “Common
Definitions.”
Cause
The device type returned by the file specified in the SNAXFILENAME attribute by the
underlying access method is unknown to SNAX/APC subsystem, or the LU is a
parallel session LU but the access method is not SNAX/APN. This error is usually
caused by a START LU command.
Effect
The command fails.
Recovery
Verify what the underlying access method for the LU is. Use the ALTER LU command
to specify the appropriate SNAXFILENAME for the local LU. The access method
addressed by SNAXFILENAME must be SNAX/XF or SNAX/CDF; if the local LU is
a parallel-session LU, the access method must be SNAX/APN.