Hello...

8.60 on Win2k-Serv. When a scheduled job detects a device
offline, it goes into a permanent Device Paused mode. I'm
disappointed that BE cannot trigger a Job Failed or at least a
Job Cancelled when such an obvious job-killing state is found.

Beyond that, Veritas tells me there's no way to force a time-out
the Device Paused mode (in a manner similar to how Operator
Attention's can be timed-out to result in a Job Cancelled).

A Device Paused means my post-job script (start the Oracle
instance!) will never run until the job is manually cancelled.
Not only that, but I will not be notified by email notifications
that there's a problem with the job. The only way I can notice
something is amiss is by the *absense* of the notification. As
they say in "Apollo 13": "That's not a good way to fly."

Any suggestions? (Other than scheduling a second, tiny, job
immediately prior to the main backup job).

Thx,
D.