Pathway/XM System Management Manual

Managing a Pathway/XM Environment
Compaq NonStop™ Pathway/XM System Management Manual426761-001
7-4
Starting PXMCOM
all the online mananagement functions needed in the Pathway/XM environment.
(PATHCOM commands are not needed and should not be used.)
Starting PXMCOM
After you have configured your Pathway/XM environment by writing a PXMCFG
source file and running PXMCFG to create the SuperCTL file, you can start a
PXMCOM process by issuing an implicit RUN command to TACL. For example, the
following command starts a PXMCOM process in the current default volume and
subvolume:
> PXMCOM
The operating system responds to your command by creating your PXMCOM process.
You can enter this command from your terminal, as shown in the example.
Alternatively, you can create a command file that contains this command (as well as
others) and then request execution of the commands in that file. The following
examples show the interactive use of PXMCOM.
When PXMCOM starts, it displays the PXMCOM banner message on your screen and
presents two greater-than signs as a prompt for your first PXMCOM command, as
shown in the following example:
8> PXMCOM
PXMCOM - T0223D48 - (31MAR2000)
COPYRIGHT 2000 COMPAQ COMPUTER CORPORATION
For detailed syntax of the command you use to start PXMCOM, refer to Starting
PXMCOM on page 11-3.
After starting PXMCOM, you must establish communication with the SuperCTL file for
your Pathway/XM environment by using an OPEN command. For example, the
following command establishes communication with the SuperCTL file named SCTL1:
>> OPEN SCTL1
Alternatively, you can issue the OPEN command in the same TACL command line you
use to start PXMCOM. For example, the following command line both starts
PXMCOM and establishes communication with the SuperCTL file named SCTL1:
> PXMCOM OPEN SCTL1
Figure 7-1 shows the communication path established by running PXMCOM and
opening the SuperCTL file SCTL1.
Caution. Using PATHCOM commands to change the configuration or to change the state of
objects can interfere with Pathway/XM operations and produce unpredictable results; it can
cause the Pathway/XM environment to be unbalanced and uncontrollable from PXMCOM.
Moreover, the output of informational PATHCOM commands such as INFO, STATUS, and
STATISTICS can be confusing or misleading in the Pathway/XM environment.