Cross posted to CICS-L and IBM-Main We have an occasional problem where an operator inadvertently issues the JES $E restart command against one of our CICS regions. The effect of the $E command is deferred until the current job step ends...typically with the weekly restart. The problem is that the job never really ends, AF/Operator doesn't continue shutting down the rest of the CICS regions and the batch process waiting on CICS waits until an astute operator detects the problem and manually cancels the CICS job.
Is there any way to nullify the effect of the $E command after it has been issued? If so I could have AF/Operator issue the appropriate commands. ________________________________ Donald Grinsell State of Montana 406-444-2983 dgrins...@mt.gov<mailto:dgrins...@mt.gov> "Learn from the mistakes of others. You can't live long enough to make them all yourself." -- Eleanor Roosevelt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
