OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
3-56
Configuring and Starting Initiator and Responder
Processes
Configuring and Starting Initiator and Responder Processes
You can configure two types of FTAM processes using the SCF ADD command: the
initiator and the responder. Initiator processes are responsible for receiving user
requests, interpreting those requests, and communicating with a remote FTAM system
through the OSI/AS subsystem. Responder processes are responsible for receiving
requests from a remote FTAM system through OSI/AS, performing the requested FTAM
services, and returning necessary information to the remote system.
Adding and Configuring Processes
Add and configure FTAM initiator and responder processes using the SCF ADD
command with the PROCESS object. Section 5, Monitoring FTAM Performance,
discusses how to detect a need for additional FTAM initiator and responder processes.
PROCESS attributes that you specify using the ADD command allow you to configure
the process for your installation. Table 2-8
on page 2-18 lists and describes these
attributes, and Using Tandem FTAM Configuration Attributes on page 3-27 discusses
aspects of operations that these attributes control. The APLMGR process must be in the
STARTED state before you add any FTAM processes to the configuration.
The following example adds and configures the initiator process $FTI1 in the Example
FTAM Configuration on page 3-38:
ADD PROCESS $AMGR.#FTAMI.FTI1, NAME $FTI1 &
, COMNAME "FTMI1A" &
, MAXASSOC 4 &
, CPU 1 &
, BACKUPCPU 2 &
, SWAP $DATA
In addition to the two PROCESS object attributes required when you add an initiator
process—NAME and COMNAME (or the OSI address)—this command also specifies
the optional primary processor, backup processor, and swap disk attributes. Association
requests by the process fail if the address associated with common name FTMI1A has
not been added to the LDIB of the OSI manager MIB. The APLMGR process does not
verify that this common name is registered with OSI/AS, and a problem is not detected
until the process is used.
Adding a responder process is identical to adding an initiator process, except that instead
of making a direct reference to a common name or OSI address, you specify a profile
associated with the responder. In addition, you have the option of specifying the
MAXATTACH attribute, which determines the maximum number of attaches available
at the responder. (This value must be less than or equal to the value of MAXASSOC.)
Note the following example:
ADD PROCESS $AMGR.#FTAMR.FTR1, NAME $FTR1 &
, PROFILE $AMGR.#VFS.VFS1 &
, MAXASSOC 4 &
, MAXATTACH 4 &
, CPU 2 &
, BACKUPCPU 0 &
, SWAP $DATA