Title

SMF Dataset Switched, No Empty Dataset Found

Name

IEE362A

Table

SMF

Message

Any of the following messages:

IEE362A SMF ENTER DUMP FOR SYS1.MANx ON volser

IEE361I SMF DATA LOST - NO DATASETS AVAILABLE, DATA BEING BUFFERED TIME = hh.mm.ss

IEE366I NO SMF DATASETS AVAILABLE - DATA BEING BUFFERED TIME= hh.mm.ss

Message Description

• IEE362A – The current SMF dataset has filled up, or a HALT EOD or SWITCH SMF command has been issued. No more SMF records are written to the old SMF dataset, whose name and volser are indicated in the message.
• IEE361I, IEE366I – The current SMF dataset has filled up and no empty alternate dataset was found.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations

Global Variables

%%DUMP_SYS1MANx\
Flag that indicates whether to dump SMF dataset SYS1.MANx. This variable is set for every SMF dataset.

Valid values are:

• YES
• NO

Rule Logic

The rule is triggered either when SMF dataset SYS1.MANx is switched, or when no empty SMF dataset is found. Either situation requires a user response to initiate a job or started task that executes utility IFASMFDP. This utility dumps and cleans the full SMF datasets.

The rule issues command D SMF to obtain SMF dataset information from response message IEE949I and then uses the "percentage-full" value of each dataset to determine which SMF datasets are to be dumped. The current SMF dataset is not dumped by the rule.

Flags for each SMF dataset, which indicate individually whether to dump the dataset, are set in Global AutoEdit variables that are referenced by the job JCL. This is done by including the Control-O $GLOBAL member in the job JCL and defining %%LIBSYM and %%MEMSYM AutoEdit control statements.

The rule sets a condition to trigger a pre-scheduled job in Control-M. The job executes utility IFASMFDP that dumps SMF 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-SMFDUMP-GO 0101. (For more details on the job scheduling definition, see Customization in this table.)

Once the rule has been triggered, it is temporarily deactivated by setting its own inverse IN condition. This prevents multiple triggering of the rule caused by messages appearing before the job has finished cleaning the SYS1.MANx datasets.

Once the job has successfully executed, condition CTO-IEE362A-HANDLED is deleted to reactivate the rule. The condition that triggered the cyclic job is also deleted upon completion of the job.

Rule Actions

• Sets a condition to deactivate the rule temporarily (see Rule Logic in this table.)
• Sets variable %%RESPMSG to IEE949I.
• Issues operator command DISPLAY SMF.
• If a response is received, the following actions are performed:
  – Analyzes response message IEE949I and sets Global variable %%DUMP_SYS1MANx for each SMF dataset to either YES (if it needs dumping) or NO (if it does not need dumping).
  – Issues a command to instruct Control-O to write the Global variables.
  – Adds a prerequisite condition to start a job in Control-M to dump the SMF dataset.

Activating the Rule

Once ordered, the rule remains active until one of the messages IEE362A, IEE361I or IEE366I exceeds a predefined threshold. (For more information regarding threshold handling, see SMF Rule Thresholds.)

The rule is also temporarily deactivated when it is triggered and reactivated after the copy and clean job finishes OK (see Rule Logic in this table).

Recommended Mode or Category

If a different automatic mechanism to clean SYS1.MANx (for example, SMF Exit IEFU29) is already implemented, the mechanism must be removed before testing this rule.

During the testing period the rule must be activated 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 dumps each dataset whose "percentage-full" value is not less than a certain value. Currently, the rule dumps datasets that are at least 90% full. This value must be adapted (in the rule definition) to site requirements.

A job scheduling definition and JCL for the SYS1.MANx copy and clean job must be created. The SOLVSCHD and SOLVJCL libraries contain a sample scheduling definition and JCL to copy and clean SYS1.MANx. These samples can be adapted to a site's conventions and requirements.

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 the prerequisite condition or date CTO-SMFDUMP-GO 0101. 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.

Prerequisite condition or date CTO-IEE362A-HANDLED 0101 must be deleted at time of IPL to make sure the rule is active after system startup (see SolveWare Initialization.)