The following tables describe the structure of the EREP Problem Alerts solution rules.
Table 58 STS1.LOGREC Access Failed Rule Structure
Item |
Description |
---|---|
Title |
SYS1.LOGREC Access Failed |
Name |
IFB0301 |
Table |
LOGREC |
Message |
Either of the following messages: IFB030I SYS1.LOGREC I/O ACCESS IFB082I LOGREC DATA SET I/O ACCESS |
Message Description |
Dataset SYS1.LOGREC was accessed either to read or write a record and a non-correctable input/output error occurred. |
Basic Scheduling Parameters |
Always schedule this rule. |
Runtime Scheduling Parameters |
No special considerations |
Global Variables |
None. |
Rule Logic |
The rule is triggered when an I/O error occurs while trying to access dataset SYS1.LOGREC. Control-O immediately brings the error to the attention of the system administrator who can then determine the cause of the problem and proceed to solve it. |
Rule Actions |
Sends a message notifying user U-SYSADMIN of the problem. |
Activating the Rule |
Once ordered, the rule remains active until message IFB030I or IFB082I exceeds a predefined threshold. (For more information regarding threshold handling, see LOGREC Rule Thresholds.) |
Recommended Mode or Category |
Activate this rule in PROD mode. The SolveWare category for this rule is 1—little or no customization is required before implementation. |
Table 59 SYS1.LOGREC Format Error Rule Structure
Item |
Description |
---|---|
Title |
SYS1.LOGREC Format Error |
Name |
IFB0501 |
Table |
LOGREC |
Message |
IFB050I/IFB083I FORMAT ERROR,hh.mm.ss |
Message Description |
The header record of dataset SYS1.LOGREC is missing or invalid. |
Basic Scheduling Parameters |
Always schedule this rule. |
Runtime Scheduling Parameters |
No special considerations |
Global Variables |
None. |
Rule Logic |
The rule is triggered when an error occurs while trying to access the SYS1.LOGREC header record. Control-O immediately brings the error to the attention of the system administrator who can then determine the cause of the problem and proceed to solve it. |
Rule Actions |
Sends a message notifying user U-SYSADMIN of the problem. |
Activating the Rule |
Once ordered, the rule remains active until message IFB050I or IFB083I exceeds a predefined threshold. (For more information regarding threshold handling, see LOGREC Rule Thresholds.) |
Recommended Mode or Category |
Activate this rule in PROD mode. The SolveWare category for this rule is 1—little or no customization is required before implementation. |
Table 60 SYS1.LOGREC Cannot Be Accessed Rule Structure
Item |
Description |
---|---|
Title |
SYS1.LOGREC Cannot Be Accessed |
Name |
IFB070I |
Table |
LOGREC |
Message |
Either of the following messages: IFB070I SYSRES CANNOT BE ACCESSED. RECORD IS LOST IFB084I LOGREC DATA SET CANNOT BE ACCESSED, RECORD IS LOST, DSN=dsn |
Message Description |
The SYSRES (System Residence) volume is unavailable; therefore, SYS1.LOGREC cannot be accessed. |
Basic Scheduling Parameters |
Always schedule this rule. |
Runtime Scheduling Parameters |
No special considerations |
Global Variables |
None. |
Rule Logic |
The rule is triggered when the SYSRES volume is unavailable for any reason. Control-O immediately brings the error to the attention of the system administrator who can then determine the cause of the problem and proceed to solve it. |
Rule Actions |
Sends a message notifying user U-SYSADMIN of the problem. |
Activating the Rule |
Once ordered, the rule remains active until message IFB070I or IFB084I exceeds a predefined threshold. (For more information regarding threshold handling, see LOGREC Rule Thresholds.) |
Recommended Mode or Category |
Activate this rule in PROD mode. The SolveWare category for this rule is 1—little or no customization is required before implementation. |
Parent Topic |