Title

CICS Journal Full—Test Environment

Name

DFH*4583

Table

CICS

Message

DFH4583/DFHJC4583
aplid CICS {SYSTEM LOG | JOURNAL nn}
{PRIMARY | SECONDARY | EMERGENCY}
DATASET (DDNAME=DFHJnnx) READY TO
BE COPIED. REPLY ‘Ynnx’ WHEN COPIED.

and the job that issued the message is CICST*.

Message
Description

The CICS journal dataset indicated in the message has filled up and the journal was specified with the PAUSE option.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

The rule is triggered when a CICS journal dataset becomes full and that journal is specified with the PAUSE option. The message waits for a system operator reply indicating that the dataset can be used again by CICS.

A correct reply must be received before CICS attempts to access the dataset for output again. Otherwise, all tasks using the specified journal are delayed until the reply is received.

Assuming that journal datasets of the test CICS environment do not need to be copied, the rule immediately replies to the message so that CICS can use the journal dataset again.

Rule Actions

Determines the reply string according to message text.

Replies to the message with the reply string.

Activating the Rule

Once ordered, 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 3—the rule is provided as an example. If it is decided to implement the rule, some customization is required.

Customization

The rule assumes that test CICS environments are named CICST*. This value must be adapted (in the rule ON statement) to match site conventions.

Title

CICS Journal Full—Production Environment

Name

DFH*4583

Table

CICS

Message

DFH4583/DFHJC4583
aplid CICS {SYSTEM LOG | JOURNAL nn}
{PRIMARY | SECONDARY | EMERGENCY}
DATASET (DDNAME=DFHJnnx) READY TO BE COPIED. REPLY ‘Ynnx’ WHEN COPIED.

and the job that issued the message is CICSP*.

Message Description

The CICS journal dataset indicated in the message has filled up and the journal was specified with the PAUSE option. The message waits for a response indicating that the journal dataset can be opened for output again.

A correct reply must be received before CICS attempts to access the dataset for output again. Otherwise, all tasks using the specified journal are delayed until the reply is received.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

%%REPLY_STRING_cicsname
The reply string indicated in the message. This string is used in the job JCL to identify the dataset to be copied. cicsname is the name of the CICS address space.

%%REPLY_NO_cicsname
Reply number of message DFH4583/DFHJC4583. cicsname is the name of the CICS address space.

Rule Logic

The rule is triggered when a CICS journal dataset becomes full and that journal is specified with the PAUSE option. The message waits for a system operator reply indicating that the dataset can be used again by CICS.

The reply string indicated in the message contains the journal identifier and type. A Global AutoEdit variable is set to contain this string 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 pre-scheduled job in Control-M. The job copies the applicable CICS journal 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-cicsname-JRN-GO STAT. (For more details on the job scheduling definition, see Customization in this table.)

Rule Actions

• Sets Global variable %%REPLY_STRING_cicsname to the reply string indicated in the message.
• Sets Global variable %%REPLY_NO_cicsname to the message reply number.
• Issues a command instructing Control-O to write the Global variables.
• Adds prerequisite condition or date CTO-cicsname-JRN-GO STAT.
• Notifies user U-SYSCICS (the CICS administrator) that a job was sent to copy the CICS journal.

Activating the Rule

Once ordered, 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 this rule.

The SolveWare category for this rule is 2—some customization is required before implementation.

Customization

If a different automatic mechanism to clean CICS journals (for example, AUTOARCH option for CICS version 3.1 and later) is already implemented, the mechanism must be removed before testing this rule. By automating CICS journal 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 production CICS environments are named CICSP*. This value must be adapted (in the rule ON statement) to match the site’s conventions.

Job scheduling definition and JCL for the CICS 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 CICS journal. These samples can be adapted to a 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-cicsname-JRN-GO 0101 (where cicsname is the name of the CICS address space). When an execution of the job is completed, this condition is deleted. This prevents cyclic reinvoking of the job and ensures that the job is only invoked again if the rule is triggered again.

Upon successful completion of the job, the prerequisite condition or date CTO-cicsname-JRN-REPLY STAT (where cicsname is the name of the CICS address space) must be added by Control-M. This triggers an event rule that replies to the original message, notifying CICS that the journal dataset is available.

Title

CICS Journal Copied—Production Environment

Name

CICSP1JC

Table

CICS

Message

CICSP1JC

Message Description

This Event rule replies to CICS message DFH4583/DFHJC4583 after the journal dataset has been successfully copied.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

IN CTO-cicsname-JRN-REPLY STAT

Global Variables

%%REPLY_STRING_cicsname

String to be issued as a reply. cicsname is the name of the CICS address space.

%%REPLY_NO_cicsname

Reply number of message DFH4583/DFHJC4583. cicsname is the name of the CICS address space.

Rule Logic

This event rule is triggered upon successful completion of the CICS journal copy job. The rule replies to CICS message DFH4583, indicating that the journal dataset can be used again by CICS.

Reply %%REPL_STRING_cicsname is issued to reply number %%REPLY_NO_cicsname. These Global variables are set by rule DFH4583 (in this solution).

Rule Actions

• Replies to reply number %%REPLY_NO_cicsname with string %%REPLY_STRING_cicsname
• Deletes prerequisite condition or date
  CTO-cicsname-JRN-REPLY STAT

Activating the Rule

Once scheduled, the rule is triggered when its IN prerequisite condition is added. The rule then deletes that condition and can be invoked again subsequently.

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

Create a similar rule for every production CICS environment. To create a new event rule, change the references to the CICS address space name in the rule actions and IN condition.