OSI/FTAM Configuration and Management Manual

OSI/FTAM Configuration and Management Manual—421944-001
4-1
4
Managing the FTAM Configuration
Once you have configured Tandem FTAM, you must perform several important tasks to
manage your installation. These tasks are described in the following subsections:
•
Managing APLMGR Configuration Files on this page
•
Retrieving Configuration Information on page 4-6
•
Controlling Open Requests on page 4-15
•
Controlling Object States on page 4-18
•
Checking Association Status on page 4-22
Managing APLMGR Configuration Files
APLMGR is associated with two types of configuration files: configuration command
files and the management information base (MIB) file. These files both affect
configuration, but in different ways. In addition, making a change in one file does not
always result in a corresponding change in the other.
Configuration command files are files you prepare that contain sequences of commands
to perform configuration tasks. Although you can enter configuration commands
manually, it is more efficient and accurate to issue the command sequence through a
command file. You can also use command files to perform such routine tasks as starting
up or shutting down the installation.
These files can be text files consisting of SCF and non-SCF commands, which you
invoke by using the TACL OBEY command, or files consisting of only SCF commands,
which you invoke by using the SCF OBEY command or by specifying the file as an IN
file in the SCF command line.
The MIB is a key-sequenced Enscribe file in which the APLMGR process stores the
configuration information for the Tandem FTAM initiator and responder processes and
VFS profiles. Whenever the APLMGR process changes from the STOPPED or
SUSPENDED state to the STARTED state, it reads this file to refresh configuration
information.