The following tables describe the structure of the LOGREC Rule Thresholds solution rules.
Table 61 Handling Exceeded LOGREC Thresholds Rule Structure
Item |
Description |
---|---|
Title |
Handling Exceeded LOGREC Thresholds |
Name |
IFB0301 |
Table |
LOGREC |
Message |
Any of the following messages: IFB030I SYS1.LOGREC I/O ACCESS IFB040I SYS1.LOGREC AREA IS FULL,hh.mm.ss IFB050I FORMAT ERROR,hh.mm.ss IFB060E SYS1.LOGREC NEAR FULL IFB070I SYSRES CANNOT BE ACCESSED. RECORD IS LOST IFB080E LOGREC DATA SET NEAR FULL, DSN=dsn IFB081I LOGREC DATA SET IS FULL,hh.mm.ss, DSN=dsn IFB082I LOGREC DATA SET I/O ACCESS IFB083I LOGREC DATA SET FORMAT IFB084I LOGREC DATA SET CANNOT BE |
Message Description |
All messages handled by rules comprising the LOGREC solutions. |
Basic Scheduling Parameters |
Always schedule this rule. |
Runtime Scheduling Parameters |
No special considerations |
Global Variables |
None. |
Rule Logic |
To avoid message overload situations, this rule deactivates LOGREC rules whose messages have exceeded a predetermined number of appearances in a period of time. These threshold values are defined for every message included in this rule in the threshold parameters APPEARED ### TIMES IN #### MINUTES. To synchronize threshold handling correctly, this rule is assigned a higher PRIORITY value than the message rules that it monitors, and has a CONTINUE SEARCH value of Y (Yes). Deactivation of a LOGREC rule is achieved by adding the appropriate (inverse) IN prerequisite condition that is defined for the rule. To reactivate a deactivated rule, the threshold conditions must be deleted. This can be done either manually or automatically by Control-O (see the following section). Threshold conditions are specified in the IGNORE list of the Control-M CONTDAY procedure (see SolveWare Implementation Considerations). |
Rule Actions |
|
Activating the Rule |
Once scheduled, the rule is triggered whenever one of the above messages exceeds its threshold. |
Recommended Mode or Category |
During the testing period, activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for this rule. The SolveWare category for this rule is 2—some customization is required before implementation. |
Customization |
Review each LOGREC message monitored by this rule and determine appropriate threshold values. For each message included in this rule, adapt to site requirements APPEARED ### TIMES IN #### MINUTES values, which specify a number of appearances in a time period. |
Table 62 Resetting LOGREC Rule Threshold Conditions Rule Structure
Item |
Description |
---|---|
Title |
Resetting LOGREC Rule Threshold Conditions |
Name |
RESLOGRC |
Table |
LOGREC |
Event |
RESLOGRC |
Event Description |
This Event rule deletes all threshold conditions for all LOGREC rules. |
Basic Scheduling Parameters |
Always schedule this rule. |
Runtime Scheduling Parameters |
No special considerations |
Global Variables |
None. |
Rule Logic |
Using the INTERVAL parameter, this rule periodically deletes the threshold conditions of all LOGREC rules, to reactivate LOGREC rules that exceeded their thresholds. For more information about the resetting of threshold conditions, see Customization in this table. |
Rule Actions |
|
Activating the Rule |
Once scheduled, the rule is triggered periodically according to the INTERVAL parameter specification. |
Recommended Mode or Category |
During the testing period, activate the rule in LOG mode. Once you are satisfied with the results of the rule, change the mode to PROD to avoid log messages for this rule. The SolveWare category for this rule is 2—some customization is required before implementation. |
Customization
|
Adapt the INTERVAL parameter to site requirements: If you use the INTERVAL parameter without the TIME FROM parameter, the threshold conditions are deleted when the rule is ordered. |
Note: Threshold conditions are also deleted at time of IPL. For more information, see the section on initializing SolveWare in Chapter 2, "STARTSYS." Threshold conditions are specified in the IGNORE list of the Control-M CONTDAY procedure. For details, see SolveWare Initialization. |
Parent Topic |