This is weird. We have WLM-managed initiators on and all JES initiators are normally drained. WLM service classes are assigned according to the userid of the submitted batch job.
If I submit a batch job with a development userid, which gets a development service class and a WLM-managed initiator, the job suffers the SA78-1C. If I submit the job with a production userid, which gets a production service class and a WLM-managed initiator, the job completes without incident. If I start a JES initiator, set MODE=JES for its jobclass, and run the job in that jobclass, it completes without incident - even with a development userid. I think I feel an IPL coming on, assuming we make it to Sunday without falling over.. Unless anyone knows any fancy WLM commands that might flush out whatever may be causing this..?? Brian - This e-mail message is for the sole use of the intended recipient(s)and may contain confidential and privileged information of Transaction NetworkServices. Any unauthorized review, use, disclosure or distribution isprohibited. If you are not the intended recipient, please contact thesender by reply e-mail and destroy all copies of the original message. ---------------------------------------------------------------------- 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
