Messages › GTAF and TPCF Messages › MIM2140W

MIM2140W

Note: The content of the MIM2140W message varies depending on the detected delay.

Delay Detection Notifications have the following format:

If there is a Contention:

MIM2140W Tape Device Allocation Delay Warning
  TYPE          CONTENTION
  DURATION  .... Minutes
  SYSTEM    ........
  CAUSE     ................................................
  -------------------------------------------------------------------
  JOBNAME  ASID TCB     WAITERS
  ........ .... ........    ....
  -------------------------------------------------------------------
End of Tape Device Allocation Delay Warning

If there is a WaitNoHold:

MIM2140W Tape Device Allocation Delay Warning
  TYPE           WAITNOHOLD
  DURATION  .... Minutes
  SYSTEM    ........
  CAUSE          Excessive Wait/NoHold Replies
  -----------------------------------------------------------------------
  JOBCOUNT
      ....
  -----------------------------------------------------------------------
End of Tape Device Allocation Delay Warning

Reason:

Delay Detection and Notification optionally issues this message if an allocation delay is detected.

TYPE

CONTENTION

Indicates a scenario where one job or task is unable to allocate one or more devices and is delaying other jobs or tasks from allocating one or more devices.

WAITNOHOLD

Indicates a scenario where two or more jobs are excessively responding WAIT/NOHOLD to allocation recovery messages. This scenario can prevent allocations on external systems in the MIAplex.

DURATION

Identifies the amount of time in minutes that have passed since the delay started.

SYSTEM

Identifies the MIA system name where the delay originates.

CAUSE

This field describes the cause of the delay. Such as:

• WAIT/HOLD Reply Received
• Excessive Wait/Nohold Replies
• WTOR REPLYID= xxxx Outstanding
• Unable to Determine

JOBNAME

Identifies the name of the job causing the delay.

ASID

Identifies the ASID of the job causing the delay.

TCB

Indicates the TCB of the job or task causing the delay.

JOBCOUNT

Identifies the number of jobs that are participating in the WAIT/NOHOLD loop.

WAITERS

Identifies the number of jobs that the owner is delaying.

Action:

To diagnose the delay, see Troubleshooting, in the CA MIA Programming Guide. If you are unable to resolve the issue, contact CA Support.