LOGREC

LOGREC solutions are designed to automate management of the Environmental Record Editing and Printing (EREP) facility. EREP is a diagnostic facility that reads and edits environmental records generated by both software and hardware.

Information stored in EREP records can be crucial when trying to locate problems. Therefore, handle EREP errors as soon as they occur to prevent the loss of environmental information.

All messages (DO SHOUT actions) in the LOGREC rules are sent to an INCONTROL user named U-SYSADMIN. Define a user with this name in the IOA Dynamic Destination table (CTMDEST). For more information, see the Dynamic Destination Table chapter of the INCONTROL for z/OS Administrator Guide.

In many cases, rule definitions make use of the inverse IN condition feature. This feature activates rules only if the specified IN conditions are not set. For more information about using inverse IN conditions, see Inverse IN Conditions.

Solutions Provided

SolveWare subject LOGREC contains the following solutions:

Copy and Clean SYS1.LOGREC
Handles situations where the EREP dataset SYS1.LOGREC fills up. A copy or clean job is automatically sent to prevent loss of environmental information.
EREP Problem Alerts
Intercepts error messages issued by EREP and notifies the system administrator of the problems.
LOGREC Rule Thresholds
Handles exceeded thresholds of all other LOGREC rules.

Copy and Clean SYS1.LOGREC

EREP stores environmental records in dataset SYS1.LOGREC. When this dataset is nearly full, a message appears on the system console. If SYS1.LOGREC is not cleaned, another message is issued when SYS1.LOGREC becomes full.

To prevent loss of environmental records, the following solution is triggered by both the SYS1.LOGREC NEAR FULL and SYS1.LOGREC IS FULL messages. The ‘FULL’ message is defined for any situations in which the ‘NEAR FULL’ message was disregarded.

Utility program IFCEREP1 is initiated to copy and clean SYS1.LOGREC when it becomes nearly full. EREP records can be copied to a generation dataset, to a single cumulative dataset (with DISP=MOD), and so on.

Rules

The Copy and Clean SYS1.LOGREC solution includes the following rules:

SYS1.LOGREC IS NEAR FULL
SYS1.LOGREC IS FULL

Rules Structure

The following tables describe the structure of the Copy and Clean SYS1.LOGREC solution rules.

Table 57 SYS1.LOGREC Is Near Full, SYS1.LOGREC Is Full Rule Structure

Item	Description
Title	SYS1.LOGREC is Near Full, SYS1.LOGREC is Full
Name	IFB060E
Table	LOGREC
Message	One of the following messages: IFB060E SYS1.LOGREC NEAR FULL IFB040I SYS1.LOGREC AREA IS FULL, hh:mm:ss IFB080E LOGREC DATA SET NEAR FULL, DSN=dsn IFB081I LOGREC DATA SET IS FULL,hh.mm.ss, DSN=dsn
Message Description	Dataset SYS1.LOGREC has reached 90% of its capacity, or the SYS1.LOGREC area is full and cannot hold more information.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations
Global Variables	None.
Rule Logic	The rule is triggered when dataset SYS1.LOGREC is either full or nearly full. Either situation normally requires a user response to initiate a job or started task that executes program IFCEREP1 to dump and clean SYS1.LOGREC. The rule adds condition or date CTO-LOGRECCP-GO STAT, which triggers a pre-scheduled cyclic job in Control-M to dump and clean SYS1.LOGREC. (For more details on the job scheduling definition, see Customization in this table.) Once the rule has been triggered, it is temporarily deactivated by adding its inverse IN condition or date CTO-IFB060E-HANDLED 0101. This prevents multiple triggering of the rule caused by the additional appearances of FULL or NEAR FULL messages before the job has finished cleaning SYS1.LOGREC. Once the job has successfully executed, condition CTO-IFB060E-HANDLED is deleted to reactivate the rule. Condition CTO-LOGRECCP-GO, which triggered the pre-scheduled job, is deleted upon completion of the job.
Rule Actions	Determines the text of the message to be sent to the system administrator according to the type of message. Sends a message notifying user U-SYSADMIN of both the occurrence of the problem and the corrective steps that were performed. Sets condition CTO-IFB060E-HANDLED to trigger a pre-scheduled job in Control-M that copies and cleans SYS1.LOGREC. Sets condition CTO-LOGRECCP-GO to deactivate the rule temporarily (see Rule Logic in this table).
Activating the Rule	Once ordered, the rule remains active until one of the messages IFB060E or IFB040I or IFB080E or IFB081I exceeds a predefined threshold. (For more information regarding threshold handling, see LOGREC Rule Thresholds.) The rule is also temporarily deactivated when it is triggered and reactivated after the copy or clean job finishes OK (see Rule Logic in this table).
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 the rule. The SolveWare category for this rule is 2—some customization is required before implementation.
Customization	A job scheduling definition and JCL for the SYS1.LOGREC copy or clean job must be created. The SOLVSCHD and SOLVJCL libraries contain a sample scheduling definition and JCL to copy or clean SYS1.LOGREC. These samples can be adapted to site conventions and requirements. Define the job (in the Control-M job scheduling definition) as a cyclic job or cyclic started task with a MAXWAIT value of 99. Order the job once, but do not manually remove it from the Control-M Active Jobs file. The MAXWAIT value of 99 ensures that the job is never removed from the Active Jobs file by the Control-M New Day procedure. The cyclic job is always ready for submission. It is triggered by adding the prerequisite condition or date CTO-LOGRECCP-GO STAT. When an execution of the job is completed, this condition is deleted. This prevents cyclic re-invoking of the job and ensures that the job is only invoked again if the rule is triggered again.

EREP Problem Alerts

This solution handles various EREP error situations that are not resolved automatically. This solution ensures that the system administrator is notified immediately by Control-O when EREP problems occur, so that the system administrator can locate the source of the error and solve the problem.

Rules

The EREP Problem Alerts solution includes the following rules:

SYS1.LOGREC Access Failed
SYS1.LOGREC Format Error
SYS1.LOGREC Cannot Be Accessed

Rules Structure

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 ERROR,sens,stat,hh.mm.ss IFB082I LOGREC DATA SET I/O ACCESS ERROR,sens,stat,hh.mm.ss, DSN=dsn
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.

LOGREC Rule Thresholds

This solution handles message overload – situations in which a message appears on the console more times than is acceptable. If an EREP message appears too often on the system console, threshold rules deactivate the relevant LOGREC rule until the source of the problem is found and the problem corrected.

For more information regarding threshold handling, see SolveWare Implementation Considerations.

Rules

The LOGREC Rule Thresholds solution includes the following rules:

Handling Exceeded LOGREC Thresholds
Resetting LOGREC Rule Threshold Conditions..

Rules Structure

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 ERROR,sens,stat,hh.mm.ss 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 ERROR,sens,stat,hh.mm.ss, DSN=dsn IFB083I LOGREC DATA SET FORMAT ERROR,hh.mm.ss, DSN=dsn IFB084I LOGREC DATA SET CANNOT BE ACCESSED, RECORD IS
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	Notifies user U-SYSADMIN that the message that exceeded its threshold is no longer handled by Control-O. Sets the appropriate IN condition to deactivate the rule. The format of this condition is: CTO-msgid-THRESH where msgid is the message ID of the specific message.
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	Deletes condition or date CTO-IFB030I-THRESH STAT Deletes condition or date CTO-IFB040I-THRESH STAT Deletes condition or date CTO-IFB050I-THRESH STAT Deletes condition or date CTO-IFB060E-THRESH STAT Deletes condition or date CTO-IFB070I-THRESH STAT
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. Threshold conditions are also deleted at time of IPL. Threshold conditions are specified in the IGNORE list of the Control-M CONTDAY procedure. For details, see SolveWare Initialization .