OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual421944-001
3-65
Responder Application Entity
The steps shown in Figure 3-9 on page 3-64 are as follows:
1. First, use an ALTER SUBSYS command to change any APLMGR subsystem
attributes for which you will not be using the installation defaults. This example
defines the maximum numbers of FTAM initiator and responder processes, the OSI
manager name, and the filename of the primary APLMGR MIB file.
2. Then add the responder process, $AMGR.#FTAMR.FTR1, to the APLMGR MIB.
Its Guardian name is $FTR1. Specify a VFS profile name; for responders, a VFS
profile is required in order to specify a common name. This example also specifies
the primary and backup CPUs, the swap disk volume, and the maximum number of
attaches this responder is to handle.
3. Next add the VFS profile, $AMGR.#VFS.VFS1. Specify the common name,
APPL1A, that will be used to access this responder. This example also specifies the
user ID and password to be used if the remote user does not specify a user ID and
password. Note that this profile can be used by multiple responders.
4. The remaining steps enter information in the OSI manager MIB. First, add the
APPL ENTRY object, $OSM1.#APPL.APPL1A. The filename portion of the
application name, FTMI1A, must match the COMNAME given in step 3. Identify
the PSEL, SSEL, TSEL, and NSAP addresses to go with the application name.
TSELs and NSAPs must represent the actual addresses that will be added later as the
names for the ENTRY objects in the underlying layers.
5. Configure PROCESS, ENTRY, and PROFILE objects for the underlying OSI layers
as in steps 4 through 12 for the initiator. In this example, the only differences are
some of the addresses given in the ENTRY objects.