SNAX/APC Configuration and Management Manual

Objects for SNAX/APC
SNAX/APC Configuration and Management Manual138787
7-5
Naming Conventions
Naming Conventions
The object name for the PROCESS object is $apc-process, and it has the following
format:
\node
is the name of the Tandem node on which the SNAX/APC process resides. This
node name is optional unless the SNAX/APC process resides on a different node
from the SCF process.
$apc-process
is the name of the PROCESS object. It is the SNAX/APC process name. The name
must begin with a dollar sign ($) followed by from 1 through 5 characters. The first
character must be alphabetic while the second through fifth characters can be either
alphabetic or numeric. If the node name associated with the process name is
included, the length of the process name is limited to a dollar sign ($) followed by
four characters.
The PROCESS object name must be unique within a Tandem system.
Examples
The following are valid object names for the PROCESS object:
$APC1
$APC01
PTNR-LU Object
The PTNR-LU object type describes a partner LU. You must pre-define the partner LU
before a local LU can initiate a session ( known as an “acquire”, as in acquiring a
session), but you do not need to make this static definition in the case of a session
request from a partner LU ( known as an “accept”, as in accepting a session). In the case
of an accept, you may add a PTNR-LU before a session starts (static definition) or just
allow SNAX/APC to add the PTNR-LU object dynamically when SNAX/APC receives
the unsolicited BIND request from a partner LU.
Naming Conventions
The object name for the PTNR-LU object is partner-lu, and it has the following
format:
[ \node. ]$apc-process
$apc-process.local-lu.partner-lu