Previous Topic

Next Topic

Book Contents

Book Index

Rules Structure

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

Table 53 Device-Not-Available—Option 2 Rule Structure

Item

Description

Title

Device Not-Available Handling—Option 2

Name

IEF238D

Table

DEVICES2

Message

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

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 the message appeared with the WAIT option, the reply is answered WAIT. 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.

If the WAIT option does not appear and the job is a test job, the rule replies CANCEL. The owner of the test job must then investigate the situation.

If the WAIT option does not appear and the job is a production job, the rule sends a highlighted message to the operator console prompting the operator to take action. The production job awaits the operator’s actions and is not automatically canceled.

Rule Actions

If the message contains the WAIT option, the rule performs the following 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

If the message does not contain the WAIT option, the rule performs the following actions:

  • for a test job, replies CANCEL to the message using the message reply number
  • for a production job, sends a message to the operator

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—this rule is provided as an example. Implementation of the rule requires some customization.

Customization

This rule identifies test and production jobs by prefix. All test jobs are assumed to have a prefix of TEST; all jobs with a prefix other than TEST are assumed to be production jobs. Adapt these values to reflect site job prefix conventions.

Parent Topic

Device-Not-Available Handling—Option 2