Hi, Bit of a JES3 question.....
Yesterday we had a developer who ended up submitting thousands of batch jobs through a looping CICS transaction. This ended up filling all our JES3 job numbers and eventually locking up JES3 on all the systems in our JESPLEX. I have been trying to think of preventative measures to stop this from happening again and haven¹t really been able to come up with anything to date. Would anyone know of a way to prevent this in the future ---- apart from changing the developer :)...... Mark ---------------------------------------------------------------------- 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
