OSI/FTAM Configuration and Management Manual

Managing the FTAM Configuration
OSI/FTAM Configuration and Management Manual—421944-001
4-5
Using Multiple MIB Files
2. Suspend the APLMGR process:
SUSPEND PROCESS $AMGR
3. Change the MIB attribute using the SCF ALTER SUBSYS command. For this
example
ALTER SUBSYS $AMGR, MIB $DATA1.OSI.ZOSAEVE
changes the filename of the MIB that the APLMGR process accesses to ZOSAEVE.
4. Activate the APLMGR process. Issue the following command to the example
configuration:
ACTIVATE PROCESS $AMGR
When the APLMGR process changes from the SUSPENDED to the STARTED
state, it obtains all of its configuration information from the new MIB file,
ZOSAEVE.
5. Start all processes associated with the configuration:
START PROCESS $AMGR.#FTAMI.FTI1
START PROCESS $AMGR.#FTAMI.FTI2
START PROCESS $AMGR.#FTAMR.FTR1
START PROCESS $AMGR.#FTAMR.FTR2
Changing MIB files can provide a quick and convenient method for checking various
configurations in a test environment. For example, you can keep a number of test
configurations in MIB files separate from the primary MIB file that the APLMGR
process is using. When system utilization is low, you may choose to test one of those
configurations. Do this by following the procedure outlined earlier. When you reach
step 3 (changing the MIB attribute), change the volume, subvolume, and filename of the
original APLMGR MIB to the volume, subvolume, and filename of the test MIB. When
system utilization begins increasing again, check the results of the system test and
switch back to the original APLMGR MIB (again using the outlined procedure).