SNAX/APC Configuration and Management Manual

Objects for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
7-14
PTNR-LU States
state. If the PTNR-LU object is created dynamically, it will be brought up already
in the STARTED state.
2. If you created it, the PTNR-LU object enters the STARTED state upon receipt of the
START PTNR-LU command if the local LU is in the STARTED state. The PTNR-
LU object enters the STARTING state upon receipt of the START PTNR-LU
command if the local LU is in the STARTING state. If the local LU is in the
STARTING state, the PTNR-LU object remains in the STARTING state until the
local LU has been successfully started, at which time the PTNR-LU object enters
the STARTED state.
3. If a local LU of the PTNR-LU object in the STARTED state receives a file system
error from the underlying access method, the local LU and the PTNR-LU return to
the STARTING state.
4. The PTNR-LU object enters the STOPPED state from either the STARTING state or
the STARTED state when an ABORT PTNR-LU or STOP PTNR-LU command is
received.
5. The PTNR-LU ceases to exist when it receives a DELETE command while in the
STOPPED state.
6. If the object was created dynamically, it will be automatically brought down to the
STOPPED state, and deleted from the local LU after all sessions are terminated.
Figure 7-5
illustrates how the different requests and commands affect the state of the
PTNR-LU object (static definition).
Figure 7-5. The PTNR-LU States
105CDT .CDD
Nonexisting
STARTED
STOPPED
ADD
Command
START Command
(when parent LU
is in STARTED
state)
DELETE
Command
ABORT
or STOP
Command
STARTING
TP-READY triggers
the open to the access
method and the open
is successful.
The parent LU receives a file system error
from the underlying access method.
ABORT or STOP Command
START Command
(when parent LU is
in STARTING state)
START/TP-READY/RETRY
(open failed and parent LU is
in STARTING state)