TCP/IP Management Programming Manual

SPI Programming Considerations
HP NonStop TCP/IP Management Programming Manual529636-001
4-3
Error Handling
Error Handling
General programming considerations for handling errors that occur when using the
management-programming interfaces are discussed in the SPI Common Extensions
Manual.
In the programmatic control-and-inquiry interface to the TCP/IP subsystem, there are
two values for the return token (ZSPI-TKN-RETCODE) that indicate that the response
record does not contain an error list. One value, ZCOM-ERR-OK, means that no error
or warning occurred. The other is a ZCOM error number that signifies the “empty”
response record. This value, ZCOM-ERR-EMPT-RSP, indicates there are no more
responses to be returned.
Error-handling considerations for specific commands are described in Section 6,
Commands and Responses.
Security
Security for the subsystem is handled by SCP, as described in the SPI Common
Extensions Manual.
Some of the commands are sensitive commands, meaning that they can be issued
only by certain users. When a user is not allowed to issue sensitive commands,
attempts to issue one, SCP returns an error. For more information on sensitive
commands, see Sensitive and Nonsensitive Commands on page 6-2.
Dynamic Route Switching
The TCP/IP subsystem provides dynamic route switching. This redetermines the
subnet with which the route is associated. This can occur when a subnet is deleted or
system resources need to be allocated differently. Monitoring subnet routing might be
one of the tasks performed by an application responsible for managing the TCP/IP
subsystem.
Relationship to SLSA
For Ethernet subnets, the SUBNET object of the TCP/IP subsystem is associated with
a SLSA LIF. The TYPE attribute specifies Ethernet, SNAP, or X.25.
Relationship to X25AM LINE Object
For X.25 subnets, the SUBNET object of the TCP/IP subsystem is associated with the
LINE object, namely the #TCPIP1 through #TCPIP32 subdevices, on an X25AM
process. These X25AM subdevices must be added prior to adding the X.25-type
subnet. For more information on the X25AM LINE object, see the X25AM Management
Programming Manual.