Steve O'Connell wrote:
Perhaps there is a good reason why they never have - does anybody know what that is?
They probably wanted to reduce call center work load? A drive flagged with the OLTEP bit is not considered for allocation under any conditions. When a job requests more units than are currently available, it waits, but the "available" count does not include the OLTEP units, and can thus result in allocation failures. E.g., if you ran a tape sort with one input and output tape, and six work tapes, and you had one string of 8 drives, it would sit in allocation until all 8 drives were available. But if even one drive were flagged for OLTEP, the allocation would fail, resulting in an irate user.
OTOH, I used this under normal conditions to reduce SYSGENs for MVT & MVS. I included additional strings of DASD and tape, but after the GEN zapped the non-existent UCBs in the nucleus to include the OLTEP bit, and used DYNAMASK to remove them from the name tables.
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
