In <[EMAIL PROTECTED]>, on 03/24/2007
at 10:43 AM, Clark Morris <[EMAIL PROTECTED]> said:
>This may relate to the user-surly approach of a lot of mainframe
>implementation. People should know enough not submit a job / start a
>task when a library is being updated. Similarly people should
>memorize the legal list of job classes for each set of resource
>requirements. It is easier to fail the job in JES2 than to change
>the job class,
In the sense that it is easier to send a passenger home for his wallet
than to let him ride for free. Job classes exist for a reason, and
automatically changing the job class would subvert those reasons.
The original problem may be a case where the software should be moore
user friendly, but the example of job classes is nonsense.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
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
