TS/MP 2.5 System Management Manual

6> PURGE NEWCONF
To rename the file named NEWCONF to OLDCONF, enter:
7> RENAME NEWCONF, OLDCONF
3. Produce the OBEYFORM file. To do this, enter a PATHCOM OBEY command, specifying as
input the EDIT file described in Step 1. For example, if you had named the EDIT file INFOCOM,
you would enter:
= OBEY INFOCOM
This OBEY command runs the INFO commands contained in the EDIT file. With the OBEYFORM
option, an INFO command generates configuration information in the form of RESET, SET,
and ADD commands that can be run by PATHCOM.
4. Shut down your PATHMON environment, using the SHUTDOWN2 command as explained in
“Shutting Down a PATHMON Environment” (page 43).
5. Alter any object attribute in the OBEYFORM file to conform to your requirements.
6. Add the START PATHWAY command to the command file, just after the last SET PATHWAY
command. OBEYFORM does not automatically write the START PATHWAY command to its
destination file, so you must include it before using this file to start a PATHMON environment.
For example, in this command file, you would insert START PATHWAY COLD! in the location
indicated:
.
.
SET PATHWAY MAXTMFRESTARTS 5
SET PATHWAY OWNER \QATST.8,21
SET PATHWAY SECURITY "N"
START PATHWAY COLD! <----(Required for COLDSTART)
.
.
7. Run the commands in the command file by entering the OBEY command, specifying the
command file as input. As PATHCOM runs these commands, it configures and cold starts the
PATHMON environment. As an example, to use the command file named NEWCONF to
configure and start your system, enter:
= OBEY NEWCONF
This step completes your configuration and start operations.
If you frequently alter your global configuration, using the OBEYFORM option to create a command
file can be helpful.
NOTE: OBEYFORM presents certain limitations. First, it produces a highly restrictive record of
your system configuration, one in which the default values recorded are those assigned by the
current version of the PATHMON environment. The file names recorded are fully expanded on the
basis of current file assignments at your node. In addition, OBEYFORM produces files that contain
values for all object attributes, whether assigned by a PATHCOM command or by default.
Logging Status and Error Information
PATHMON reports error and status information to a log file.
You can request the PATHMON process to report errors only, or errors and changes in object
status as well. You can request the PATHMON process to log information to only one file, or to
copy the information to two files. Also, you can request that error and status information be formatted
either as text or as tokenized event messages (managed by the Event Management Service (EMS)
portion of the Distributed Systems Management (DSM) software).
You can log information to a command terminal or to a disk file; it is recommended, however, that
you not specify a terminal. On a terminal, log messages are lost when they scroll off the terminal
screen; also, performance is generally better to a process on a disk file than to a terminal.
98 Maintaining a PATHMON Environment