OSI/MHS Configuration and Management Manual

Managing Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
7-2
Using SCF Commands Interactively
online, that change is not automatically made to the configuration file. You must edit
the configuration file to reflect the configuration changes you make online.
Likewise, when you change the configuration file, that change does not reflect the
current system until you invoke that configuration file. This subsection describes these
two methods of reconfiguring the system.
Using SCF Commands Interactively
To reconfigure the subsystem interactively, you use the SCF commands ADD,
DELETE, and ALTER. These commands add new objects, delete existing ones, or
change configuration parameters. When you use these commands on an object,
follow the guidelines described in Section 2, Management Environment for OSI/MHS.
Some objects, for example, must be in the STOPPED state before you can alter them.
Using Command Files
A command file (also called an OBEY file) is an EDIT file that contains sequences of
commands. This could be a TACL command file containing SCF and other
commands, or an SCF command file containing only SCF commands. You invoke a
TACL command file by using the TACL OBEY command; you invoke an SCF
command file by using the SCF OBEY command. A command file can also include
comments. Appendix A, Examples of Configuration Files, contains the command files
for the configuration examples used in this manual.
You can edit a configuration command file at any time. You can remove SCF
commands, add new ones, or make changes to command parameters. When you
modify a command file, you must invoke the newly edited file to implement the
changes; otherwise, your changes have no effect on the current OSI/MHS subsystem.
Managing the Databases
The OSI/MHS subsystem has two types of databases you must manage: the
OSI/MHS database and the group databases. All the databases are protected by the
Transaction Management Facility (TMF). For guidelines on using TMF, see the TMF
Planning and Configuration Guide and the TMF Operations and Recovery Guide.
OSI/MHS Database
The OSI/MHS database consists of the configuration database, the registration
database, the distribution list database, and the CUG database. (For a brief
description of the database files, see Table 2-1 on page 2-3.) To manage these
databases, you should first make sure that your subsystem has the right configuration
for TMF. Then follow normal TMF procedures and perform regular backups using the
BACKUP utility or TMF online dumps.