-----------------<snip>---------------
Thanks for the quick and informative response. I will look into your
suggestions. I am a little leery about putting TSO above hot batch as well.
Part of the problem is that the operators pretty much open the flood gates
at about 10 pm and let all the batch compete. That is a whole different
battle that we have discussed on a fairly regular basis with operations but
nothing has changed. I know the REAL answer is to deal with the lack of
resources this habit creates but, for the short term, I just want to make
sure that a programmer that gets called to fix a problem can actually get
logged on and do something.
Thanks again for your help.
------------------<unsnip>--------------
Have you tried breaking operators' fingers? Baseball bat does nicely. :-)
On a more serious note, we found that putting first-period TSO at a
IMP=2, for most trivial transactions, was sufficient to alleviate that
problem in our shop. Batch work was either PRODSTD or PRODHI, both with
IMP=3; other parms were juggled to differentiate the two batch groups.
----------------------------------------------------------------------
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
