SNAX/APC Management Programming Manual

START Command
Commands and Responses
111813 Tandem Computers Incorporated 5–83
Operational Notes
The target object is placed in the STARTED state.
SNAX/APC accepts a START command while the parent object of the target object
is still in the STARTING state. In this case, the target object is first placed in the
STARTING state and then placed in the STARTED state after its parent object is
started.
When a START LU command is executed, the ZAPC-TKN-SNAX-RETRY-COUNT
token counter is reset. This counter keeps track of the retries of the local LU. If an
error occurs once the counter is reset, the local LU will perform as many retries as
specified by ZAPC-TKN-SNAX-MAX-RETRY-COUNT.
Upon completion of the START LU command, SNAX/APC opens the configured
ZAPC-TKN-SNAX-FILE-NAME token file.
Upon completion of the START PTNR-LU command, the reserved PTNR-MODE
object named SNASVCMG is started automatically, and an
INITIALIZE_SESSION_LIMIT CNOS verb is issued.
The START PTNR-MODE command places the target PTNR-MODE object in the
STARTING state and issues an INITIALIZE_SESSION_LIMIT CNOS verb. If the
CNOS verb is completed successfully, the specified PTNR-MODE object is placed
in the STARTED state; otherwise, the PTNR-MODE object is returned to the
STOPPED state.
When a PTNR-MODE object is placed in the STARTED state, both the values
represented by ZAPC-TKN-CUR-MAXINRUSIZE and ZAPC-TKN-CUR-
MAXOUTRUSIZE tokens are set to the values specified in the ZAPC-TKN-D-
MAXINRUSIZE and ZAPC-TKN-D-MAXOUTRUSIZE tokens respectively if these
values do not exceed the upper bound of the transfer capacity of the underlying
SNAX file (SNAX access method such as SNAX/APN or SNAX/XF). Otherwise,
these counters are set to the upper limit of the underlying SNAX file’s transfer
capacity.
If the reserved PTNR-MODE object named SNASVCMG is stopped manually, an
explicit START command is required to bring it up before any CNOS commands
can be exchanged.