Start-Up
Determine Your System Start-Up Program Name
In order to ensure that QSystem Robot starts each time the system IPLs, you need to add a number of steps to your system start-up program.
To determine the name of your system’s start-up program, type the command DSPSYSVAL SYSVAL(QSTRUPPGM). The display shows you the name and library of the program. For this example, we'll assume it's QSTRUP in library QGPL.
Determine the Source for Your System Start-Up Program
Having determined the program’s name, you now need to locate its source. To determine where the source resides, enter the command DSPPGM PGM(QGPL/QSTRUP). The display shows you the ‘Source file’ and ‘Library’ for the object.
Adding the Steps to the System Start-Up Program
All you now have to do is add the relevant lines (see the following sections) to the source and then recompile the program. This applies to both the central system and any configured remotes.
Purge
The product’s detailed data, which is collected throughout the day, is summarized by the MON.SUMARY job (usually overnight).
The detailed data files can get very large over a period of time, and the summary files can also grow quite large if you intend to keep a few years worth of history. It is therefore important to establish your historical data requirements, monitor the file growth, and then schedule the MONPURGE command to run as or when required.
The following simple example purges old data (greater that sixty days old) from all of the data files for all of the configured systems.
A more complicated example follows:
MONPURGE DATE(*DAYS) DAYS(120)
PRGDTA(*YES) PRGDSK(*YES) PRGACT(*YES) PRGPRT(*YES) PRGSUM(*YES) PRGADT(*YES) PRGDSM(*YES)
PRGHIC((60 0)) PRGRSP((60 0)) PRGDCP((60 0)) PRGDIO((60 0))
This selectively purges data from the monitor history files based on a number of days to keep (120), and then selectively purges data from the detailed files for a more aggressive factor (60).
We recommended that if a date is supplied, it should always be the beginning of a month. If MONRESUM is run, monthly averages are rebuilt using the partial data available, which may be misleading. By using the beginning of a month, performance is also improved.
Reorganization
The MONRGZPF (Reorganization) command is used to reorganize files with more than a certain number of deleted records, and is often used after a user runs the MONPURGE. It can run interactively or be submitted as a batch job. Do the following to run it interactively:
- Sign on to the host system using your user profile and password.
- On the command line, execute the following command to add the library MSM to your library list:
ADDLIBLE MSM
Note: If you used a different library name during installation, use that name instead of MSM.
- Type MONRGZPF on the command line and press F4 to display the Reorganize Selected Files
panel.
- Fill out the fields on the panel. Press F1 for field information and descriptions.
- When you're finished, press Enter to reorganize your selected files.
Product Start-Up
Assumption
If you add the following to your start-up routines, it's assumed that your shut-down routines will also be amended to stop the product (see below).
Central System
If you do not have MSM in the library list for the job and the MSM subsystem is not active, you'll probably need the following three lines of code, depending on the rest of your start-up routine:
ADDLIBLE MSM
MONSTRTCP STRSBS(*YES)
RMVLIBLE MSM
The first and third lines obviously only change the library list and could be removed if the job had MSM as part of its library list.
The second line performs three functions. The first is to start the QSM TCP server job on the central system, which controls communications with the remote systems defined within Robot Monitor. The second is to start the MSM subsystem in which the product's jobs will run. The third is to start the system monitoring process itself.
Remote Systems
If you don't have MSM in the library list for the job and the MSM subsystem is not active, you'll probably need the following three lines of code, depending on the rest of your start-up routine:
ADDLIBLE MSM
MONSTRTCP STRSBS(*SBSONLY)
RMVLIBLE MSM
The first and third lines obviously only change the library list and could be removed if the job had MSM as part of its library list.
The second line performs two functions. The first is to start the MSM TCP server job on the remote system, which controls communications with the central system defined within Robot Monitor. The second is to start the MSM subsystem in which the product's jobs will run.
The monitoring jobs required by Robot Monitor will be started in the subsystem, after the remote system establishes communications with the central system.
Product Shut-Down
Assumption
If you add the following to your shut-down routines, it's assumed that your start-up routines will also be amended to restart the product (see above).
Central System
If you do not have MSM in the library list for the job, you'll probably need the following five lines of code, depending on the rest of your shut-down routine:
ADDLIBLE MSM
MONENDTCP
MONEND
ENDSBS MSM
RMVLIBLE MSM
Remote systems
If you don't have MSM in the library list for the job, you'll probably need the following four lines of code, depending on the rest of your shut-down routine:
ADDLIBLE MSM
MONENDTCP
ENDSBS MSM
RMVLIBLE MSM
