SNAX/APC Configuration and Management Manual

Objects for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
7-11
LU States
2. The CONV object enters the STARTED state if the ALLOCATE verb is successfully
completed or if the remote ATTACH request is attached to the parent TPI object.
3. The CONV object enters the STOPPING state and is in the process of being
deallocated when one of the following conditions is detected:
•
A DEALLOCATE request is received from either the local or remote side
•
A session outage is detected
•
A protocol error is detected
•
A CLOSE request is received
4. The CONV object ceases to exist when the DEALLOCATE request is completed.
Figure 7-2
illustrates how the different requests and commands affect the state of the
CONV object.
LU States
The following describes the states of the LU object.
1. The LU object is created by the ADD LU command, which puts the LU object in the
STOPPED state.
2. The LU object enters the STARTING state with the START LU command.
3. When the LU object receives a TP-READY request that triggers a successful open to
the access method, the object enters the STARTED state. During normal, error-free
operation, the STARTING state is a temporary transition state.
4. If the open fails, the object remains in the STARTING state until the open is
successfully retried at which time the object enters the STARTED state. If an LU
object in the STARTED state receives a file-system error from the underlying SNAX
Figure 7-2. The CONV States
104CDT .CDD
ALLOCATE
Completed OK
or
Remote ATTACH
DEALLOCATE
(From Either Side),
Session Outage,
Protocol Error
or
CLOSE
STARTED
ABORT TPI or
STOP TPI Command
ALLOCATE
or
Remote ATTACH
STARTING
STOPPING
DEALLOCATE
Completed
Nonexisting