Control Processes [ HP DeskMon: Administrator's Guide ] MPE/iX 5.0 Documentation
HP DeskMon: Administrator's Guide
Control Processes
DeskOn
DeskOn (DMDSKON.DESKMON.SYS) requests the Report process to enable HP
DeskManager checking and reporting.
Report
Report (DMREPORT.DESKMON.SYS) is the father process for DeskMon reporting
and is the program that is run by the DeskMon job.
When Report is started, it checks that the DeskMon reporting process is
not already active by attempting to gain exclusive access to the file
DMLOCK.DESKMON.HPOFFICE. If this file is already being accessed, the
Report process assumes that another Report process is already active,
displays a suitable error message and terminates.
If the Report process successfully gains access to the DMLOCK file, it
proceeds to start other processes used for DeskMon reporting. Which
processes are started will depend on the local system and local DeskMon
configuration:
* DSSend will not be started on an MPE/XL system as DeskMon can only
report using NS on these systems.
* The LogScan process will only be started if STATSFIL checking is
specified in the DeskMon configuration.
* The LocalPrinter process will only be started if a printer is
specified in the DeskMon configuration.
Other initialization tasks of the Report process include:
* Clearing the main IPC file (DMIPC) of any existing packets. It is
very unlikely that there will be any packets in the IPC file
because of the controlled shut down sequence.
* If the system is not MPE/XL, DS reporting is available. To notify
the other processes of this, the Report process exclusively
accesses the file DMDSLOCK.DESKMON.HPOFFICE.
Once all the required processes are active, the Report process starts
performing its main function--processing packets that are put in its main
input IPC file (DMIPC). Depending on the type of packet received, one of
the following actions will be performed:
* Translate the Report Category supplied to the appropriate
recipients and write packets to the necessary IPC files. This
type of packet comes from either the Check process, the LogScan
process or the DMJCL process.
* Pass a packet straight through to the required output processes by
writing packets into the appropriate IPC files. These packet
types come from one of the network receiving processes (NSReceive
or DSReceive) and are messages from remote systems to be displayed
on the local system.
* Handle a circular error message. This involves creating three
message packets from the circular error packet and sending them to
the local operator by writing them into the DMLOCIPC file.
* Handle a request to stop HP DeskManager checking and release
access to the HP DeskManager database. The Report process will
then:
* Request the Check process to not perform any further checks
that need access to the HP DeskManager database.
* Request the DeskSend process to terminate.
* Kill the LogScan process.
* Handle a request to completely shut down the Report process. The
shut down is split into two stages. In the first stage, all input
processes are shut down:
* Request the Check process to terminate after it has
finished processing any current checks.
* Kill the NSReceive process.
* Prevent further DSReceive processes from starting and
refuse existing ones access to the Report process.
* Kill the LogScan process.
Once the first stage of the shut down has been successfully
completed, the second stage in which all output processes are shut
down can begin:
* Request the DeskSend process to terminate.
* Request the LocalReport process to terminate.
* Request the LocalPrinter process to terminate.
* Request the NSSend process to terminate. This process will
in turn request the DSSend process to terminate.
After all the shut down requests have been issued, the Report
process checks that all the processes have terminated. If after
five minutes some processes are still active, DeskMon assumes they
are blocked in some way and kills them.
The Report process now terminates and the job will log off.
* Handle a request to enable HP DeskManager checking and reporting.
The Report process will then:
* Request the Check process to enable HP DeskManager checks.
* Start the DeskSend process.
* Start the LogScan process.
The Report process also monitors the state of the other active processes
in the DeskMon reporting process. If any of these processes abort, then
the Report process attempts to restart them.
DeskOff
DeskOff (DMDSKOFF.DESKMON.SYS) requests the Report process to stop HP
DeskManager checking and release access to the HP DeskManager database.
DMStop
DMStop (DMSTOP.DESKMON.SYS) requests the Report process to completely
shut itself down.
MPE/iX 5.0 Documentation