|
OMACHECK |
  
|
|
OMACHECK |
|
Check Operations Monitor Alert Files
OMACHECK [omaname ...]
This program allows you to select and monitor one or more OMA files that are written by each COPIAFACTS server engine program every fifteen seconds. If an OMA file is found to be older than a specified interval, OMACHECK launches a program you supply. OMA files written by other than the COPIAFACTS server engine (e.g. FFEXTERN.OMA, JOBMON.OMA) must be explicitly specified on the command line and should be added to the shortcut used to run OMACHECK. No path need be specified because these files are always written in the base CopiaFacts folder. Missing OMA files appear in red in the display and 'old' files in blue.
You could specify as the launched program a utility to send you e-mail or send an SMS message to your pager, or take any other action you require. The delay interval that you can specify allows for differences in time settings between the nodes on your network, or allows time for another auto-restart procedure to attempt to restart COPIAFACTS or the network node.
Iconizing the program (using the start button) causes it to start monitoring the specified OMA files.
The reboot option allows you to force reboot of a machine when the OMA check is triggered. To do this you must provide the machine name to match each node that you are monitoring and wish to reboot. It is also necessary to be logged in to the machine in question with sufficient privileges to allow you to reboot it. After launching the specified command, OMACHECK waits one minute before performing the reboot. After performing any reboot, OMACHECK suppresses all actions for ten minutes.
The "Command-line to execute" box must contain a valid Windows command line. If the pathname of the program contains blank spaces, double-quotes must be used to enclose the pathname. If you wish to perform different actions depending on which OMA file has 'failed', you can use the values @node and @machine in the command line to be run. No other CopiaFacts system variables are expanded. The @node is expanded to the nodename (e.g. M1) and the @machine to the machine name to be rebooted (e.g. \\FAXFACTS). If no reboot is specified, the @machine variable expands to blank.
No action will be taken for a missing or old OMA file until a corresponding 'good' (i.e. recent) OMA file has been seen. This feature works both on starting OMACHECK and after an OMA failure has been detected for which no machine reboot has been specified. This allows you to restart a node manually and avoids repeated triggering of OMACHECK after the node has failed once. On the other hand, if you set OMACHECK to reboot a failed node, OMACHECK will trigger again (after ten minutes) if the reboot has failed to make the OMA file current.
Topic url: http://www.copia.com/support/refmanual/index.html?omacheck.htm