That leads to one of my points of curiosity: why did we make this
change? I'm not really concerned about the actual differing values; we do no
chargeback, and I'm not worried about whether a job is using 70 minutes instead
of 60 minutes of CPU time. (I may become worried about it at some point, but
not yet.) I'm just curious as to why we did it, and also why the goofball
number of 72? I could see 75 or 90, but 72?
I have looked back a few weeks for the command with no joy, so I may
reload a year's worth or so of syslog and check it next week.
Thanks for the responses, folks. You answered my question, as usual.
Jon
<snip>
Yes, but I would not recommend people just go around and issue this command
without research. I'm thinking a lot of people are running with JOBCLASS
parms that have been changed and aren't reflected in the JES2 PARMs (just
check the archives for similar threads). OS/390 2.4 was a long time ago.
</snip>
----------------------------------------------------------------------
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
