Title

IDMS Log Is nn% Full

Name

IDMS DC201

Table

IDMS

Message

IDMS DC050001 DCLOG IS nn% FULL

Message Description

IDMS log is nn% full.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

The rule is triggered when the IDMS log utilization reaches its threshold. If the percentage of Log utilization is higher than a predefined limit, the rule sets a condition to trigger a prescheduled job in Control-M. The job copies the IDMS Log datasets.

The job must be defined as a cyclic job or cyclic started task (STC). It is triggered by adding the prerequisite condition or date CTO-idmsname-LOG-GO STAT. For more details on the job scheduling definition, see the Customization item in this table.

Rule Actions

• Extracts the IDMS log utilization percentage from the message text.
• If utilization is over 80%, the following actions are performed:
  – Issues a command instructing Control-O to write the Global variables.
  – Adds condition or date CTO-idmsname-LOG-GO STAT
  where idmsname is the name of the IDMS 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 IDMS log is already implemented, the mechanism must be removed before testing this rule. By automating IDMS log cleaning 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.

A Control-M job scheduling definition and JCL for the IDMS 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 IDMS log. These samples can be adapted to a site’s conventions and requirements. Separate job scheduling definitions must be created for each IDMS production environment.

If the IDMS log tends to fill up either very quickly or very slowly, the threshold percentage (in the first SET statement) must be either lowered or raised respectively.

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-idmsname-LOG-GO STAT (where idmsname is the name of the IDMS address space). 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.

Title

IDMS Journal Is Full

Name

IDMS DC201

Table

IDMS

Message

IDMS DC205003 TASK: idmsname; DISK JOURNAL IS FULL. SUBMIT IDMSAJNL JOB journalid

Message Description

IDMS journal is full.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

%%IDMS_JRNDUMP_idmsname.

Rule Logic

The rule is triggered as soon as the IDMS journal becomes full. It writes the journal’s ID to a Global variable so that it can be used by the clean and copy job.

The IDMS journal ID is indicated in the message. The Global AutoEdit variable is set to contain this ID and is referenced by the job JCL. The Control-O $GLOBAL member is included in the job JCL by %%LIBSYM and %%MEMSYM AutoEdit control statements.

The rule sets a condition to trigger a prescheduled job in Control-M. The job copies the applicable IDMS journal dataset.

The job must be defined as a cyclic job or cyclic started task (STC). It is triggered by adding the prerequisite condition or date CTO-idmsname-JRN-GO STAT. For more details on the job scheduling definition, see the Customization item in this table.

Rule Actions

• Sets Global variable %%IDMS_JRNDUMP_idmsname to journalid indicated in the message.
• Issues a command instructing Control-O to write the Global variables.
• Adds prerequisite condition or date CTO-idmsname-JRN-GO STAT.

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 IDMS journal is already implemented, the mechanism must be removed before testing this rule. By automating IDMS journal cleaning 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.

A Control-M job scheduling definition and JCL for the IDMS journal copy and clean job must be created. The SOLVSCHD and SOLVJCL libraries contain a sample job scheduling definition and JCL to copy and clean IDMS journal. These samples can be adapted to the site’s conventions and requirements. Separate job scheduling definitions must be created for each 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-idmsname-JRN-GO STAT (where idmsname is the name of the IDMS address space). When an 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.