OSI/AS Configuration and Management Manual

Routine Management Tasks
OSI/AS Configuration and Management Manual—424119-001
5-4
Modifying a Configuration Command File
Nevertheless, these two configuration files are independent of one another and may not
always be consistent with each other. Inconsistencies between these two files can occur
in two ways:
1. You can edit a command file at any time. You can remove SCF commands, add new
ones, or make changes to command parameters. However, unless you invoke a
newly edited command file, your changes have no effect on the current MIB.
2. You can interactively execute SCF commands by entering them directly from a
terminal. You can add new objects, delete existing ones, or change configuration
parameters. The OSI manager process records these changes in the MIB file, but
they do not thereby become part of the configuration command file.
Therefore, while a configuration command file can provide you with a useful record of
an OSI/AS subsystem configuration, it may not describe the actual state of your
subsystem.
Modifying a Configuration Command File
A convenient way to alter the configuration of an OSI/AS subsystem is to edit the
configuration command file and then to invoke the newly edited file to implement the
changes. This procedure can lead to undesirable consequences, however, if you have not
taken care to purge the old configuration data from the MIB file. The OSI manager
process simply writes information into the designated MIB when it receives SCF
configuration commands. Thus, if you do not start with a “clean” MIB file, there is a
danger that old configuration information will remain, leaving the MIB in an
inconsistent state.
The general procedure for using a command file to make configuration changes is as
follows:
1. Edit the old configuration command file.
2. Stop the TSP and TAPS processes.
3. Suspend the OSI manager process.
4. Use the FUP PURGEDATA command to remove old configuration data from the
MIB.
5. Activate the OSI manager process.
6. Use the SCF OBEY command on the new configuration command file.
Using Multiple MIB Files
Under some circumstances, it is desirable to maintain more than one MIB file. You can
cause the OSI manager process to read the MIB file of your choice by altering the
SUBSYS object.
For example, suppose you have two MIB files in the following locations:
$SYSTEM.CONFIG.MIB1
$SYSTEM.CONFIG.MIB2