TS/MP 2.5 System Management Manual

You cannot change the OWNER and SECURITY attributes while a PATHMON environment is
running; you must first shut down the environment, as shown in this example. Recall that when you
configure global limits after a shutdown, you must specify all limits, not just the ones you are
changing. Once you have specified old and new limits, and changed the OWNER and SECURITY
attributes, you must use the COLD! start option to restart the PATHMON environment:
= SHUTDOWN2, MODE ORDERLY
= OPEN $PM
.
. (specify old limits)
.
= SET PATHWAY OWNER 8,60
= SET PATHWAY SECURITY "O"
= START PATHWAY COLD!
For more information about the OWNER and SECURITY attributes, see “Configuring Objects in a
PATHMON Environment” (page 51).
Capturing a Configuration
You can use the INFO command with the OBEYFORM option to capture a configuration for use in
future start operations.
When you specify the OBEYFORM option, the PATHMON process reads information from the
PATHMON configuration file and writes it to a specified file in the format required for a PATHMON
environment startup file. Each attribute is written as a syntactically correct PATHCOM command
with the proper SET prefix. Example 15 (page 97) contrasts output of the INFO command with
and without the OBEYFORM option specified:
Example 15 Using the OBEYFORM Option
= INFO PATHMON
PATHMON
BACKUPCPU 4
DUMP ON (FILE \SYS.$VOL1.TESTING.MONDUMP)
= INFO PATHMON, OBEYFORM
SET PATHMON BACKUPCPU 4
SET PATHMON DUMP ON (FILE \SYS.$VOL1.TESTING.MONDUMP)
You can use the OBEYFORM option to create a comprehensive record of your complete PATHMON
environment or, optionally, a selected portion of it. The OBEYFORM file represents a "snapshot"
of the system as it exists at the time the file is produced.
These steps illustrate how to use OBEYFORM to capture a complete system configuration:
1. Create an EDIT file that contains a set of INFO commands specifying the OBEYFORM option.
Each individual INFO command captures a distinct portion of the overall configuration (the
PATHMON process, PATHWAY object, SERVERS, TCPs, and so forth) in the destination
command file.
For example, the second INFO command in this group captures the configuration information
for the PATHWAY object and writes that information to the startup file named NEWCONF.
Notice that an asterisk (*) is used in the last four commands to indicate all SERVER objects in
the set.
INFO /OUT NEWCONF/ PATHMON , OBEYFORM
INFO /OUT NEWCONF/ PATHWAY , OBEYFORM
INFO /OUT NEWCONF/ SERVER *, OBEYFORM
2. Purge any existing file of the same name as your destination command file, or rename that
file, by entering the PURGE or RENAME TACL commands.
This step prevents OBEYFORM from appending new information to a file that already contains
obsolete information. For example, to purge the file named NEWCONF, enter:
Capturing a Configuration 97