Previous Topic

Next Topic

Book Contents

Book Index

Rules Structure

The following tables describe the structure of the Device-Not-Available Handling—Option 1 solution rules.

Table 52 Device-Not-Available—Option 1 Rule Structure

Item

Description

Title

Device-Not-Available—Option 1

Name

IEF238D

Table

DEVICES

Message

IEF238D jjj - REPLY {DEVICE NAME} {,}{‘WAIT’} OR ‘CANCEL’

when the message contains the string WAIT.

Message Description

Device allocation cannot be performed (completed) by MVS for specified jobname jjj.

Basic Scheduling Parameters

Always schedule this rule.

Runtime Scheduling Parameters

No special considerations.

Global Variables

None.

Rule Logic

If a device is currently not available and the WAIT string appears in the message text, the rule replies WAIT, which instructs MVS to have the job wait for the devices to become available. The rule then expects MVS to issue message IEF433D, which asks whether to hold already allocated devices. Since holding already allocated devices can result in a deadlock, the rule replies NOHOLD.

Rule Actions

  • Sets AutoEdit reserved user-defined variable %%RESPMSG to IEF433D.
  • Replies WAIT to the message, using the message reply number.
  • If a response message (IEF433D) is intercepted, replies to that message with NOHOLD.

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 1— little or no customization is required before implementation.

Parent Topic

Device-Not-Available Handling—Option 1