SNAX/APC Configuration and Management Manual

Configuring Network Resources for SNAX/APC

SNAX/APC Configuration and Management Manual—138787

4-5

Object Hierarchies

As you can see from the example names just shown, the SNAX/APC subsystem, like

many others, is structured hierarchically, with a group of objects of one type logically

subordinate to an object of another type.

All object types are subordinate to the SNAX/APC process. Figure 4-1

represents the

hierarchical relationships that exist among the object types valid for SNAX/APC.

TPI This represents an instance of the transaction program. In the

Tandem (local) LU, the TPI can be a Tandem process, or a thread

within a Tandem process. On the Tandem side, a TPI object is

created by a TP issuing a TP-READY service verb, and is deleted by

a TP issuing a TP-END service verb, an ABORT/STOP command,

or a file system CLOSE request. This object is not created at

configuration time.

An example object name would be $APC1.LU01.ACCT.003A.

CONV The CONV object type represents an LU 6.2 conversation. A

conversation is created by a TP issuing an ALLOCATE verb and

deleted by a TP issuing a DEALLOCATE verb. This object is not

created at configuration.

An example object name would be $APC1.LU01.ACCT.003A.0012.

Figure 4-1. Object Type Hierarchical Relationships

009CDT .CDD

PROCESS

PTNR-LU

PTNR-MODE

SESSION

TPN

TPI

CONV