Steve O'Connell wrote:
The only difference I see is that with the broken drive being flagged unavailable the job may fail, whereas if it tries to assign the broken drive because it is flagged as available it will hang indefinitely.
In practice the job that hangs in allocation can be held and restarted, thus allowing the operator to release it when the drive does become available. In many installations a job with such a requirement would be likely to run at night, when the originating programmer would not be available to resubmit it.
Personally, I'd rather the job failed and freed up all 7 other tape drives for use by other work if the drive is broken.
Even if it's your company's money maker? Or perhaps the payroll run?
Gerhard Postpischil Bradford, VT new e-mail address: gerhardp (at) charter (dot) net ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
