CA MII Statements and Commands › (MII) DEQJOB Command-Dynamically Release a Resource

(MII) DEQJOB Command-Dynamically Release a Resource

The DEQJOB command lets you bypass the integrity processing of GDIF for a local job that needs a resource held on another system. You can use this command to create an immediate, controlled integrity exposure when a local job is involved in a cross-system resource conflict and no other local job needs that resource. As soon as the job releases the resource, integrity processing of GDIF is restored.

Scope: Local

This command has the following format:

DEQJOB JOB=name

JOB

Identifies the job for which GDIF should bypass its integrity processing. GDIF bypasses integrity processing for all resources that this job cannot obtain currently. Specify the name of this job in place of name.

The resource that this job needs must be held by a task on another system. In addition, this job must be the only task on the local system that needs the resource.

Usage Notes: DEQJOB Command

• The DEQJOB command usually is issued from a console, rather than from the MIMPARMS data set.
• You must be authorized to issue system control commands to issue the DEQJOB command. TSO users generally are not authorized to issue system control commands.
• All QNAMEs that you want to dequeue must be managed QNAMEs, and must have EXEMPT=YES specified on the QNAME statement.
• Because the DEQJOB command immediately suspends the GDIF integrity processing for the jobs whose requests are currently in global conflict, you must ensure that no other local job needs those resources. You can use the DISPLAY CONFLICTS command to display information about resources that other local jobs need.

Example: DEQJOB Command

To enable job LEDGER to use a resource that is held by a task on another system, issue this command:

DEQJOB JOB=LEDGER