13.12.2012 Views

HP OpenView Operations Administrator's Reference - filibeto.org

HP OpenView Operations Administrator's Reference - filibeto.org

HP OpenView Operations Administrator's Reference - filibeto.org

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring OVO<br />

Configuring Flexible Management Templates<br />

158<br />

If you include the day of the week (for example, Monday April 1,<br />

1997), OVO cross-checks the day and date you have entered to make<br />

sure that they match the calendar. If they do not match, however, the<br />

action will not be correctly completed. OVO does not issue an error<br />

message.<br />

❏ Wildcards (*)<br />

You can set dates or periods using a wildcard character (*):<br />

Specific Dates<br />

To set a condition for December 1st every year, use the syntax:<br />

DATE ON 12/01/*<br />

Time Periods<br />

To set a condition from August 6th to September 10th every year,<br />

use the syntax:<br />

DATE FROM 08/06/* TO 09/10/*<br />

NOTE Although syntactically correct, OVO cannot handle mixed conditions<br />

like DATE FROM 05/07/01 TO 10/10/*.<br />

NOTE <strong>HP</strong>-UX Only:<br />

For further examples of time templates, see the following:<br />

❏ “Syntax for Time Templates” on page 135<br />

❏ man page opcmom(4)<br />

❏ /etc/opt/OV/share/conf/OpC/mgmt_sv/tmpl_respmgrs<br />

To correct time differences between the different time resources used by<br />

the OVO C-routines and the MPE/iX intrinsics and commands, the<br />

TIMEZONE variable must be set on MPE/iX managed nodes. If not,<br />

messages can be sent to the wrong management server as they are<br />

processed using the incorrect time. For information about setting the<br />

TIMEZONE variable for MPE/iX nodes, see the OVO DCE Agent<br />

Concepts and Configuration Guide.<br />

Chapter 2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!