Pathway/XM System Management Manual

Managing a Pathway/XM Environment
Compaq NonStop™ Pathway/XM System Management Manual—426761-001
7-11
Displaying Current PXMCOM Operational Settings
$DATA.PM.LOGFILE as LOG2 $0, STATUS. The process next sends both error
information and status information to $0 because although the LOG1 command did not
specify the STATUS parameter, the LOG2 command did. Additionally, the process
sends both event messages and text messages to $0 because although the LOG2
command did not specify the EVENTFORMAT parameter, the LOG1 command did.
When you use your PXMCOM command terminal for logging, you can get immediate
information from the Pathway/XM processes. You should restrict the activity on that
terminal, however, to avoid interfering with these messages; in fact, if you use a
terminal for logging, it is best to have that terminal dedicated to logging.
If you use a terminal as the logging file, type “pause” at the TACL prompt to suspend
the TACL process so that logging can occur.
Some of the PATHMON, TCP, and LINKMON link-management messages are
tokenized messages that are always reported to $0, regardless of the LOG1 and LOG2
settings. Message text, cause, effect, and recovery information for those messages is
provided in the Operator Messages Manual for your release of the Compaq NonStop™
Kernel operating system. You can display these messages with an EMS printing
distributor or (on D-series systems) with the ViewPoint application.
Displaying Current PXMCOM Operational Settings
You can use the ENV command to check the current settings of operational parameters
for your PXMCOM session, as follows:
>> ENV
This command displays the following information:
•
Name of the currently open SuperCTL configuration file
•
Names of the LOG1 and LOG2 system log files
•
Name of the current defaults for Guardian volume and subvolume
•
Current depth set for the HISTORY command
•
VERBOSE command setting (ON or OFF)
•
Volume and subvolume of the Pathway/XM program file
For the syntax of the ENV command, refer to ENV
on page 11-23.
Starting a Pathway/XM Environment
After you have used PXMCFG to build the SuperCTL file, you are ready to start your
Pathway/XM environment. To do so, you first run PXMCOM and open the SuperCTL
file, and then issue the necessary START commands.
The first command you issue, which starts the overall Pathway/XM environment, is the
START PATHWAY command. After you issue the START PATHWAY command,
you start other objects explicitly or (in some cases) implicitly.