|
|
|
|
|
The following tables describe the structures of the SMF Alerts solution rules.
Table 64 SMF Dataset Resides on a Non-Direct Access VolumesRule Structure
Item |
Description |
|---|---|
Title |
SMF Dataset Resides on a Non-Direct Access Volumes |
Name |
IEE3631 |
Table |
SMF |
Message |
IEE363I SMF ser NOT DIRECT ACCESS |
Message Description |
SMF dataset SYS1.MANx resides on a non-direct access device and therefore cannot be used by SMF. |
Basic Scheduling Parameters |
Always schedule this rule. |
Runtime Scheduling |
IN !CTO-IEE363I-THRESH STAT |
Global Variables |
None. |
Rule Logic |
The rule is triggered when the SYS1.MANx dataset resides on a non-direct access device. 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 IEE363I exceeds a predefined threshold. (For more information regarding threshold handling, see SMF Rule Thresholds.) |
Recommended |
This rule must be activated in PROD mode. The SolveWare category for this rule is 1—little or no customization is required before implementation. |
Table 65 SI/O Error While Writing on SMF Dataset Rule Structure
Item |
Description |
|---|---|
Title |
SI/O Error While Writing on SMF Dataset |
Name |
IEE3641 |
Table |
SMF |
Message |
IEE364I SMF {LOGICAL | PHYSICAL} I/O ERROR ON SYS1.MANx {FEEDBACK CODE = fc | error text} |
Message Description |
An I/O error occurred while writing on the SYS1.MANx dataset indicated in the message. |
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 writing on SYS1.MANx. 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 IEE364I exceeds a predefined threshold. (For more information regarding threshold handling, see SMF Rule Thresholds.) |
Recommended Mode or Category |
This rule must be activated in PROD mode. The SolveWare category for this rule is 1—little or no customization is required before implementation. |
Table 66 SMF Dataset or SYS1.PARMLIB Cannot Be Opened Rule Structure
Item |
Description |
|---|---|
Title |
SMF Dataset or SYS1.PARMLIB Cannot Be Opened |
Name |
IEE3651 |
Table |
SMF |
Message |
IEE365I SMF SYS1.{MANx | PARMLIB} NOT OPENED |
Message Description |
SMF failed to open SMF dataset SYS1.MANx or SYS1.PARMLIB. No records are written to the SMF dataset. |
Basic Scheduling Parameters |
Always schedule this rule. |
Runtime Scheduling Parameters |
No special considerations |
Global Variables |
None. |
Rule Logic |
The rule is triggered when SYS1.MANx or SYS1.PARMLIB cannot be opened. 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 IEE365I exceeds a predefined threshold. (For more information regarding threshold handling, see SMF Rule Thresholds.) |
Recommended Mode or Category |
This rule must be activated in PROD mode. The SolveWare category for this rule is 1—little or no customization is required before implementation. |
Parent Topic |