IDMS

IDMS solutions are designed to keep track of the status of IDMS, to enable integration with Control-M and to automate basic actions of cleaning the IDMS log and journal. Integration is done through IOA prerequisite conditions and is useful for scheduling jobs that use IDMS only when IDMS is active.

Some messages (DO SHOUT actions) in the IDMS rules are sent to INCONTROL users (U-SYSDBA or U-SHFTOPER). Users with these names must be defined in the IOA Dynamic Destination table (CTMDEST). For details, see the considerations chapter of the INCONTROL for z/OS Administrator Guide.

Some 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 SolveWare Implementation Considerations.

Solutions Provided

SolveWare subject IDMS contains the following solutions:

IDMS Startup and Termination
Monitors the IDMS startup and termination procedures, intercepts relevant messages and updates the appropriate IOA prerequisite conditions.
Copy and Clean the IDMS Journal and Log
Handles situations where the IDMS journal or log datasets become full. A copy and clean job is submitted automatically to prevent loss of information.

IDMS Startup and Termination

This solution handles IDMS startup and termination.

At sites operating both Control-M and IDMS, the status of IDMS (up or down) impacts the start of jobs that run under Control-M. Therefore, for the production IDMS in the system, the site must maintain two prerequisite conditions indicating IDMS status – CTO-IDMS-UP STAT and CTO-IDMS-DOWN STAT.

These two conditions are updated by Control-O according to IDMS initialization and termination messages, and are used as prerequisite conditions for jobs run under Control-M that require IDMS status information.

While startup or termination is in process—but not yet completed—the IOA environment considers IDMS as both "not up" and "not down." Therefore, IDMS not being up is not necessarily the same as IDMS being down, and vice versa.

Throughout this solution, IDMS C.V. stands for IDMS Central Version.

Rules

The IDMS Startup and Termination solution includes the following rules:

IDMS C.V. Initialization Started
IDMS C.V. Initialization Completed
IDMS C.V. Termination Started
IDMS C.V. Termination Completed
Suppress S IDMS if IDMS Is Active

Rules Structure

The following tables describe the structures of the IDMS Startup and Termination solution rules.

Table 118 IDMS C.V. Initialization Started Rule Structure

Item	Description
Title	IDMS C.V. Initialization Started
Name	IEF403I
Table	IDMS
Message	IEF403I jjj STARTED { - TIME=hh.mm.ss} when the message is issued from job IDMS*.
Message Description	Job jjj starts.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	As soon as IDMS is started, the IOA environment is informed that IDMS is no longer down.
Rule Actions	Deletes condition or date CTO-idmsname-DOWN 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 mechanism that controls IDMS conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule. Change the name of the prerequisite condition indicated in this rule to match your previous definition if both of the following are true: The IOA environment already contains a prerequisite condition indicating that IDMS is up or down. For example, if such a condition is already referenced by a Control-M job scheduling definition. The prerequisite condition has a different name than the one indicated in this rule. The rule assumes that the name of the production IDMS jobs or started tasks starts with IDMS. This prefix may need to be changed (in the rule’s ON statement) in order to match site conventions.

Table 119 IDMS C.V. Initialization Completed Rule Structure

Item	Description
Title	IDMS C.V. Initialization Completed
Name	IDMS DC013
Table	IDMS
Message	IDMS DC013005 IDMS-CV/DC INITIALIZATION COMPLETE
Message Description	IDMS completed initialization and is up.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	As soon as IDMS initialization is completed, the IOA environment is informed that IDMS is up.
Rule Actions	Adds condition or date CTO-idmsname-UP 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 mechanism that controls IDMS conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule. Change the name of the prerequisite condition indicated in this rule to match your previous definition if both of the following are true: The IOA environment already contains a prerequisite condition indicating that IDMS is up or down. For example, if such a condition is already referenced by a Control-M job scheduling definition. The prerequisite condition has a different name than the one indicated in this rule.

Table 120 IDMS C.V. Termination StartedRule Structure

Item	Description
Title	IDMS C.V. Termination Started
Name	IDMS DC201
Table	IDMS
Message	IDMS DC201002 IDMS CENTRAL VERSION QUIESCING
Message Description	IDMS C.V. termination started.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	Intercepts IDMS termination message and informs the IOA environment that IDMS is no longer up.
Rule Actions	Deletes condition or date CTO-idmsname-UP 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 mechanism that controls IDMS conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule. Change the name of the prerequisite condition indicated in this rule to match your previous definition if both of the following are true: The IOA environment already contains a prerequisite condition indicating that IDMS is up or down. For example, if such a condition is already referenced by a Control-M job scheduling definition. The prerequisite condition has a different name than the one indicated in this rule.

Table 121 IDMS C.V. Termination CompletedRule Structure

Item	Description
Title	IDMS C.V. Termination Completed
Name	IEF404I
Table	DMS
Message	IDMS DC201003 IDMS CENTRAL VERSION SHUTDOWN or IEF404I jjj ENDED { – TIME=hh.mm.ss} when the message is issued from job IDMS*.
Message Description	IDMS DC201003 – IDMS C.V. shutdown successful. IEF404I – Job jjj ended.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	When IDMS terminates successfully or when the IDMS job ends, the IOA environment is informed that IDMS is down.
Rule Actions	Deletes condition or date CTO-idmsname-UP STAT, where idmsname is the name of the IDMS job or started task. Adds condition or date CTO-idmsname-DOWN 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 mechanism that controls IDMS conditions (utility IOACND, Control-M Event Manager, etc.) is already implemented, the mechanism must be removed before implementing this rule. Change the name of the prerequisite condition indicated in this rule to match your previous definition if both of the following are true: The IOA environment already contains a prerequisite condition indicating that IDMS is up or down. For example, if such a condition is already referenced by a Control-M job scheduling definition. The prerequisite condition has a different name than the one indicated in this rule.

Table 122 Suppress S IDMS if IDMS Is Active Rule Structure

Item	Description
Title	Suppress S IDMS if IDMS Is Active
Name	S IDMS
Table	IDMS
Command	S IDMS
Command Description	This command starts IDMS (the rule suppresses the command).
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	IN !CTO-idmsname-DOWN STAT
Global Variables	None.
Rule Logic	In general, if command S IDMS is issued when IDMS is already up, the new started task is immediately shut down and normal termination messages are issued. These messages, however, give the appearance that the active IDMS has gone down and this may incorrectly trigger other rules in this solution and cause erroneous updating of prerequisite conditions, thus incorrectly triggering jobs in Control-M. This rule prevents the situations described above by suppressing the S IDMS command if IDMS is already up. In this way, issuance of the termination messages is prevented and rules are not incorrectly triggered. This rule serves as a sample rule. A similar rule must be created for each IDMS environment in the site.
Rule Actions	Suppresses the command. Sends a message to user U-SHIFTOPER indicating that command S IDMS was suppressed.
Activating the Rule	Once scheduled, the rule becomes active when prerequisite condition or date CTO-idmsname-DOWN STAT is deleted, where idmsname is the name of the IDMS job or started task.
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	The rule must be duplicated for each IDMS job or started task in the site. To adapt each rule, the IDMS name in the rule’s ON statement and IN condition must be changed. Change the name of the prerequisite condition indicated in this rule to match your previous definition if both of the following are true: The IOA environment already contains a prerequisite condition indicating that IDMS is up or down. For example, if such a condition is already referenced by a Control-M job scheduling definition. The prerequisite condition has a different name than the one indicated in this rule.

Solution: Copy and Clean the IDMS Journal and Log

The IDMS journal and log are datasets that keep track of IDMS activity. The log must not be allowed to reach full capacity and must be cleaned when its utilization passes a certain threshold. The journal must be cleaned when it becomes full.

This solution intercepts messages regarding the utilization of the IDMS log and journal and schedules jobs in Control-M to copy them to backup datasets and clean them when necessary.

Rules

The Copy and Clean the IDMS Journal and Log solution includes the following rules:

IDMS Log Is nn% Full
IDMS Journal Is Full

Rules Structure

The following tables describe the structures of the Copy and Clean the IDMS Journal and Log solution rules.

Table 123 IDMS Log Is nn% Full Rule Structure

Item	Description
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.

Table 124 IDMS Journal Is Full Rule Structure

Item	Description
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.