OSI/FTAM Configuration and Management Manual

Managing the FTAM Configuration
OSI/FTAM Configuration and Management Manual421944-001
4-2
Creating a New Configuration Command File
Configuration command files and the MIB file are related in that you can use a
command file to create the MIB. There are, however, two important differences you
should be aware of when working with these two files:
You can edit a configuration command file anytime. You can add or remove
commands, edit existing command lines, or change command parameters. Unless
you invoke the newly edited command file, however, the changes have no effect on
the current MIB.
You can interactively execute SCF commands by entering them directly from a
terminal. You can change object attributes, add new processes, or delete existing
processes. The APLMGR process records this information in the MIB, but the
information does not automatically become part of the configuration command file.
If you want these changes to be reflected the next time you use this command file,
you must edit the file and invoke it to change the configuration.
The three primary tasks involved in managing APLMGR configuration files are
described in the following subsections:
Creating a New Configuration Command File on this page
Invoking a New Configuration Command File on page 4-3
Using Multiple MIB Files on page 4-4
Creating a New Configuration Command File
You can develop a configuration command EDIT file by making a log file of your
interactive commands while they are executing. After executing the necessary
configuration commands, edit the log file, deleting any messages or command output
that was returned. Use the resulting file as your configuration command file.
By changing command files that already exist, you can create new configuration
command files to perform tasks for your installation. If the command sequence of an
existing command file follows fairly closely the sequence of tasks you need to perform,
you can save time by using that file’s basic structure. Unless you invoke the new file,
however, the system will not implement the changes.
When using command files, you can use the SCF DELAY command to suspend activity
for a short time to allow a command to complete, for example, when a START
command to an APLMGR or OSI manager process is followed by commands that
depend on the completion of the START command. Because SCF’s request to the
operating system to run the APLMGR or OSI manager process is in nowait mode,
control is returned to the command file before the creation and initialization of the
process has finished.