>Tends to tick off JES when that happens with one of its initiators (caused by >you running as a batch job and not a started task).
I thought a lot of that was fixed circa 2.8. IBM did a very good job of associating an INIT with a logical initiator and keeping that binding. Before that, INIT-1 may do have always been associated with I1, so all sorts of cr*p happened with an unexpected failure. Now, when you do a $PIx, the 'correct' address space is terminated, rather than a 'random' one. . Questions? Concerns? (Screams of Outrage?) ---------------------------------------------------------------------- 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
