On Thu, 15 Apr 2010 13:46:26, Ted MacNEIL <[email protected]> wrote:
>Third, with the restructuring of the way initiators work, where draining an >init actually terminates the offending address space underpinning that init, rather than a random one, we found most of the reasons for the exit disappeared. Not that JES flavor was specified, but with JES3, draining the init takes more effort. Quiesce the entire class/group (set INIT counts to zero and wait for jobs to complete), then restart the class/group. Is this still effective with WLM-managed INITs? We don't use them, but ISTR you lose the ability to manually drain/start inidividual initiators, and therefore would have to quiesce an entire job class. In these cases, IEFUSI seems like the easier path. CHECKREGIONLOSS looks interesting, too... Regards, Art Gutowski Ford Motor Company ---------------------------------------------------------------------- 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
