--------------------<snip>------------------------
Some jobs are real problems. For instance, we had one that required six
tape drives (out of eight), and lots of work space. We had a special
class, without a matching initiator, and required the jobs for that
class to be scheduled by Operations. Just changing the class wouldn't
have accomplished the scheduling. Furthermore, some jobs do horrible
things to the system, but not in a fashion that's apparent from the JCL;
again, changing the job class wouldn't do any good, and would severely
impact other users.
--------------------<unsnip>--------------------
We used a slightly different approach at Clearing. First, we disallowed
TEST jobs from mounting tapes at all. Business production had the same
limitation, due to the time-critical nature of the work; only site
maintenance could mount tapes, for backups, incremental backups, etc.
Then we started assigning time limits to classes, and rigidly enforcing
them. Then we disallowed the TIME parameter on JOB and EXEC statements.
Worked like a champ and most (but not all) of our scheduling problems
went away in the test environment.
----------------------------------------------------------------------
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
