SNAX/APC Configuration and Management Manual

Objects for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
7-3
The Null Object Type
Unless you fully understand the possible effects or you have a strong reason for doing
so, do not use all six characters when naming processes. Refer to the Introduction to
D-Series Systems for more information.
The Null Object Type
In SNAX/APC, the null object type is supported only for the NAMES and VERSION
command; it has no hierarchical relationship to any of the other supported object types.
The null object type does not have a name and is assumed to be the default for either
the VERSION or NAMES commands if no object type is specified..
The null object type is not a true object type, but indicates that the command can be
issued without specifying an object type. For more information about the null object
type, refer to the Subsystem Control Facility (SCF) Reference Manual.
CONV Object
The CONV object type represents an LU 6.2 conversation. A conversation can be
created by a transaction program issuing an MC_ALLOCATE or ALLOCATE
conversation verb, and can be deleted by a transaction program issuing an
MC_DEALLOCATE or DEALLOCATE conversation verb. In certain situations, such
as the occurrence of a protocol error or session outage, a CONV object could be deleted
automatically.
Naming Conventions
The object name for the CONV object is conv-id, and it has the following format:
$apc-process
is the name of the SNAX/APC process.
local-lu
is the name of the local LU.
tpn
is the name of the local transaction program.
tpi-id
is the name of the instance of the local transaction program.
conv-id
is the name of the CONV object. It is assigned by the SNAX/APC process and is
the name that uniquely identifies a conversation. It is an unsigned integer, and is
$apc-process.local-lu.tpn.tpi-id.conv-id