Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide
- To prevent unintended behavior when switching to extended regular expressions from JP1-specific regular expressions (Windows) or XPG4 basic regular expressions (HP-UX, Solaris, and AIX), you should review the existing settings and redefine them to comply with extended regular expressions.
- Control codes (linefeed codes, tab characters, and so on) may be handled differently depending on the product and operating system. For this reason, you should not include control codes in a regular expression used to specify a condition for a message.
- A period followed by an asterisk (.*) matches any character. If you make frequent use of this regular expression, it may take a long time to find matches. When defining a condition to match a long message, for example, use the period-and-asterisk combination only where required in the search string.
In an environment that supports extended regular expressions, you can use the combination [^ ]* instead of the period-and-asterisk combination to match non-null characters. This reduces the search time.
- The vertical bar (|) represents an OR condition. Note the following when using this OR condition in a regular expression:
Because a vertical bar (|) has low precedence in a regular expression, you must specify the range of the OR condition explicitly; otherwise, it may work erroneously or not at all. You can specify the range of an OR condition by enclosing it in parentheses. An example of specifying the conditions for a source event server name as an OR condition is shown below.
- Example: JP1 events issued by work or host
- ^.* .* .* .* .* (work|host) .*$
- Spaces before or after the vertical bar (|) special character are treated as characters. Do not enter a space unless you want it to be included in the OR condition.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.