-------------------------<snip>-------------------
In your case, the correct solution would be to set up SDSF command security
to prevent the operators from changing the service classes. Of course this
will probably become a management political hot potato. As a "carrot" I
would also sit down with operators and determine what changes could be made
with the batch service classes to keep them from moving things around.
------------------------<unsnip>--------------------
GOD, I miss the old SRM setups. My operators were so afraid of messing
up that they wouldn't use the PERFORM= parameter for ANY reason. They
didn't know what PERFORM values did what and if they started to get
"smart", I could re-arrange the parms.
----------------------------------------------------------------------
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