ADABAS

ADABAS solutions are designed to keep track of the status and workload of ADABAS in order to enable integration with Control-M and to automate the cleaning of ADABAS protection log. Integration achieved through IOA prerequisite conditions is useful for scheduling jobs that use ADABAS only when ADABAS is active.

Some messages (DO SHOUT actions) in the ADABAS rules are sent to INCONTROL users (U-SYSDBA or U-SHIFTOPER). Users with these names can be defined in the IOA Dynamic Destination table (CTMDEST). For details, see the considerations chapter of the INCONTROL for z/OS Installation 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 Inverse IN Conditions.

Solutions Provided

SolveWare subject ADABAS contains the following solutions:

ADABAS Startup and Termination
Intercepts all messages related to ADABAS initialization or termination and updates the appropriate IOA prerequisite conditions.
Copy and Clean ADABAS Protection Log
Handles situations where the ADABAS protection log dataset becomes full. A copy and clean job is submitted automatically to prevent loss of information.

ADABAS Startup and Termination

This solution handles ADABAS startup and termination.

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

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

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

Rules

The ADABAS Startup and Termination solution includes the following rules:

ADABAS MPMxx Initialization Started
ADABAS Initialization Completed
ADABAS Termination Started
ADABAS MPMxx Termination Completed
Suppress S MPMxx if ADABAS Is Active

Rules Structure

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

Table 112 ADABAS MPMxx Initialization Started Rule Structure

Item	Description
Title	ADABAS MPMxx Initialization Started
Name	IEF403I
Table	ADABAS
Message	IEF403I jjj STARTED { - TIME=hh.mm.ss} when the message is issued from job MPM*.
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 ADABAS is started, the IOA environment is informed that ADABAS is no longer down.
Rule Actions	Deletes condition or date CTO-adabasname-DOWN 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 mechanism that controls ADABAS 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 ADABAS 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 ADABAS environments starts with MPM. This prefix may need to be changed (in the rule’s ON statement) in order to match site conventions.

Table 113 ADABAS Initialization Completed Rule Structure

Item	Description
Title	ADABAS Initialization Completed
Name	ADAN01
Table	ADABAS
Message	ADAN01 adabasname time ADABAS IS ACTIVE
Message Description	ADABAS has 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 ADABAS initialization has been completed, the IOA environment is informed that ADABAS is up.
Rule Actions	Adds condition or date CTO-adabasname-UP 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 mechanism that controls ADABAS 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 ADABAS 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 114 ADABAS Termination Started Rule Structure

Item	Description
Title	ADABAS Termination Started
Name	ADAN51
Table	ADABAS
Message	ADAN51 adabasname OPER,TYPEIN:xxxxxx when xxxxxx is ABEND
Message Description	xxxxxx indicates the last operator command issued to ADABAS. When this command is ABEND, the message indicates that ADABAS termination started.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	ADABAS received an ABEND command from the operator and the IOA environment is informed that ADABAS is no longer up.
Rule Actions	Deletes condition or date CTO-adabasname-UP 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 mechanism that controls ADABAS 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 ADABAS 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 115 ADABAS MPMxx Termination Completed Rule Structure

Item	Description
Title	ADABAS MPMxx Termination Completed
Name	IEF404I
Table	ADABAS
Message	IEF404I jjj ENDED { – TIME=hh.mm.ss} when the message is issued from job MPM*.
Message Description	Job jjj ended.
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	No special considerations.
Global Variables	None.
Rule Logic	When ADABAS job ends, the IOA environment is informed that ADABAS is down.
Rule Actions	Deletes condition or date CTO-adabasname-UP STAT, where adabasname is the name of the ADABAS job or started task. Adds condition or date CTO-adabasname-DOWN 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 mechanism that controls ADABAS 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 ADABAS 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 each production ADABAS environment starts with MPM. This prefix may need to be changed (in the rule’s ON statement) in order to match site conventions.

Table 116 Suppress S MPMxx if ADABAS Is Active Rule Structure

Item	Description
Title	Suppress S MPMxx if ADABAS Is Active
Name	S MPMxx
Table	ADABAS
Command	S MPMxx
Command Description	This command starts ADABAS (and the rule suppresses the command).
Basic Scheduling Parameters	Always schedule this rule.
Runtime Scheduling Parameters	IN !CTO-adabasname-DOWN STAT where adabasname is the name of the ADABAS job or started task
Global Variables	None.
Rule Logic	In general, if command S MPMxx is issued when ADABAS is already up, either the new started task is immediately shut down, or it waits until the currently running task goes down and then starts automatically. In either case, other rules in this solution can be triggered, causing erroneous updating of prerequisite conditions, thus incorrectly triggering jobs in Control-M. This rule prevents the situations described above by suppressing the S MPMxx command if ADABAS is already up. In this way, issuance of the termination messages, or starting of the task without a message being sent, is prevented and rules are not incorrectly triggered. This rule serves as a sample rule. A similar rule must be created for each ADABAS environment in the site.
Rule Actions	Suppresses the command. Sends a message to user U-SHIFTOPER indicating that command S MPMxx was suppressed.
Activating the Rule	Once scheduled, the rule becomes active when prerequisite condition or date CTO-adabasname-DOWN STAT is deleted (where adabasname is the name of the ADABAS 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	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 ADABAS 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 must be duplicated for each ADABAS job or started task in the site. To adapt each rule, the ADABAS name in the rule’s ON statement and IN condition must be changed.

Copy and Clean ADABAS Protection Log

The ADABAS protection log is a dataset that keeps track of ADABAS activity. Usually the log is kept in dual mode, which means that two datasets are alternately used by ADABAS. When the current protection log becomes full, ADABAS switches to the other dataset and issues a message. This solution intercepts this message and schedules a job in Control-M to copy the full protection log to a backup dataset and clean it. This solution eliminates the necessity to code the ADABAS EXIT 2 routine, which is otherwise responsible for cleaning the protection log.

Rules

The Copy and Clean ADABAS Protection Log solution includes the ADABAS Protection Log Is Full rule.

Rules Structure

The following tables describe the structures of the Copy and Clean ADABAS Protection Log solution rules.

Table 117 ADABAS Protection Log Is Full Rule Structure

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