Title

ADABAS Protection Log Is Full

Name

ADAN21

Table

ADABAS

Message

ADAN21 adabasname PROTECTION LOG DDPLOGRn started

when the message is issued from job MPM*.

Message Description

ADABAS is switching to the alternate protection log indicated by DDPLOGRn. The full protection log must be cleaned.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

As soon as the ADABAS protection log becomes full, a job is triggered to clean and copy it.

Rule Actions

Adds condition or date CTO-adabasname-LOG-GO STAT, where adabasname is the name of the ADABAS job or started task.

Activating the Rule

Once scheduled, the rule remains active until deleted from Control-O.

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

If a different automatic mechanism to clean the ADABAS log is already implemented, that mechanism must be removed before testing this rule. By automating ADABAS log dumping with Control-O, the benefits of integrated operation are achieved. Control-M tracks and controls the copy and clean job, and manages Quantitative resources used by the job.

The rule assumes that the name of the production ADABAS environments starts with MPM. This prefix may need to be changed (in the rule’s ON statement) in order to match site conventions.

A Control-M job scheduling definition and JCL for the ADABAS log copy and clean job must be created. The SOLVSCHD and SOLVJCL libraries contain a sample job scheduling definition and JCL to copy and clean ADABAS log. These samples can be adapted to the site’s conventions and requirements. Separate job scheduling definitions must be created for each ADABAS production environment.

The job must be defined as a cyclic job or cyclic started task (STC) with a MAXWAIT value of 99. It then only needs to be ordered once, but must not be removed manually 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 prerequisite condition or date
CTO-adabasname-LOG-GO STAT (where adabasname is the name of the ADABAS job or started task). When execution of the job is completed, this condition is automatically deleted. This prevents cyclic re-invoking of the job and ensures that the job is only invoked again if the rule is triggered again.