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.