OSI/MHS Configuration and Management Manual

Starting, Stopping, and Updating Your OSI/MHS
Subsystem
OSI/MHS Configuration and Management Manual—424827-003
6-3
Specifying MHS Manager Startup Commands
Options for the RUN Command
NAME Specifies the name of the MHS manager process. The name that you
specify here must be the same as the value you supply to the
MHSMGR_PNAME keyword in the installation file. You must run all
MHS manager processes with this option.
NOWAIT Causes TACL to return control to the user after starting the MHS
manager process.
OUT Defines the out file to be used as the log file. You must specify the file
as either a spooler file or a disk file before you issue the RUN
command. If you specify a disk file, the file must already exist.
Typically, the disk file is an entry-sequenced file with a record size of at
least 132 bytes. You can create the disk log file by using the following
command:
FUP CREATE filename, TYPE E, REC 132, EXT (10, 20)
You set the log file initially with the OUT option of the RUN command,
but you can modify it later. You do this by using SCF and entering an
ALTER command for the MON object of the same process name as the
MHS manager.
PRI Specifies the priority at which the MHS manager process is to run. This
priority must be higher than all other processes within an OSI/MHS
subsystem. (In other words, it must be higher than the priority set for
the GI, LO, MS, RTS, SC, RS, and MR processes.)
SWAP Defines the disk volume on which the data area is swapped. If you omit
the SWAP parameter, the disk on which the program file resides is
used.
If you omit the SWAPVOL parameter, the disk used as the data
swapping volume also defines the disk for extended memory swapping.
(This is also true if you omit the SWAPVOL parameter in the PARAM
command.)
TERM Defines the home terminal. When abnormal conditions are detected
that warrant termination of the MHS manager process, the MHS
manager attempts to write a message to the log file. If the log file is
inaccessible, the message is written to the home terminal. In addition,
certain errors detected during startup (before the logging device is
known) are written to the home terminal. The home terminal should
correspond to a device that is used to display urgent error messages.