Troubleshooting › Delay Detection and Notification

Delay Detection and Notification

Use the information in this section to diagnose and respond to Delay Detection and Notification (DDN) warnings.

Contention Detection

Possible Cause:

Received a WAIT/HOLD reply

The response of Wait/Hold was issued to an outstanding allocation recovery message.

Solution:

Provide more eligible devices, wait for devices to be deallocated from other tasks, or cancel the task.

Note: Request more information by issuing the following command:

ANALYZE TAPEDELAY DETAIL(JOBNAME=jobname,TYPE=CONTENTION)

Possible Cause:

An outstanding WTOR REPLYID nnnn

An allocation recovery message with the shown reply ID is awaiting a response. Device allocation group locks are held until a message response is received.

Solution:

Respond to the allocation recovery message.

Note: Request more information by issuing the following command:

ANALYZE TAPEDELAY DETAIL(JOBNAME=jobname,TYPE=CONTENTION)

Possible Cause:

Unable to Determine

A task has held locks for an extended amount of time but CA MIA is unable to determine the reason for the delay.

Solution:

• On the system of the owning task, look for outstanding allocation recovery messages.
• VARY devices online that can satisfy the tasks request.
• If no reason for the delay can be determined, canceling the task releases held device allocation group locks.
• If the task cannot be canceled or the device allocation group locks are not released, then contact CA Technical Support.

Note: Request more information by issuing the following command:

ANALYZE TAPEDELAY DETAIL(JOBNAME=jobname,TYPE=CONTENTION)

Wait/NoHold Detection

Possible Cause:

Excessive Wait/Nohold Replies

Two or more tasks are in allocation recovery for two or more devices. When one task replied to allocation recovery with WAIT/NOHOLD, the second task is posted and enters allocation recovery. No tasks on external systems are able to allocate devices from the device group.

This warning is issued when the problem persists for an extended time.

Solution:

To determine tasks contributing to the problem, issue the following command:

ANALYZE TAPEDELAY DETAIL(TYPE=WAITNOHOLD)

To alleviate the problem, add devices for the tasks to allocate or cancel tasks causing the delay.

If the problem cannot be resolved, contact CA Technical Support at http://ca.com/support.