OSI/MHS Configuration and Management Manual

Starting, Stopping, and Updating Your OSI/MHS
Subsystem
OSI/MHS Configuration and Management Manual—424827-003
6-5
Specifying MHS Manager Startup Commands
the traffic on the primary collector ($0) will likely be higher than is desirable if all the
accounting events are going to it.
PROCESSES
Sets the maximum number of processes the MHSMGR can run. The value must
be less than 400. If you specify a value of 400 or greater, the MHS manager fails
at startup time. If you specify a value too small for your configuration, processes
fail to start.
SWAPVOL
Specifies the name of the disk used for swapping extended memory. If you omit
this parameter, the SWAP volume is assumed to be the same volume as that used
to swap the data area. If you start the program from the TACL command, then the
data swap volume is controlled by the SWAP keyword in the run options. If you
omit the SWAPVOL parameter from the run options, the disk from which the MHS
manager program was loaded is used.
CONFIG-DB-SVOL
Specifies the volume and subvolume of the configuration database. The default is
the subvolume from which the MHS manager program was run, the same
subvolume as defined by the installation file keyword,
OSIMHS_CONFIG_DATABASE.
LOG or LOGFILE
Defines the log file. You should specify the file as either a spooler file or a disk file.
For 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 file-name, TYPE E, REC 132, EXT (10, 20)
If you do not specify a file name, no logging output is produced.
Argument: maximum number of child processes supported
Default: 100
Argument: name of local disk
Default: data swap disk
Argument: volume and subvolume name
Default: MHS manager volume and subvolume
Argument: file-name
Default: (blank)