IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> wrote on 02/11/2013 01:58:22 PM:
> Well, this is actually personally of interest to me. But trying to > understand your reply seems to indicate that 1) IEFUSI can't control > INIT/IEFIIC and 2) there is not a GUPI/exit that will allow the INIT > to be controlled? Is that the correct understanding? The purpose of IEFUSI is to control limits for the active step of a started task or a piece of work running under an initiator. In between steps (or between jobs), the operating system can do as it sees fit with respect to limit settings. There should be nothing relevant for IEFUSI to control. It is probably the case that when IEFIIC is initially attached by started task control when an initiator starts, that IEFUSI can set the initial limits. But IEFIIC processing is within its rights to immediately do something which changes that if it so desires. If you were to explain exactty what you are trying to do which would cause between step or job limits to be of interest to you, I might be able to provide a more relevant answer for your circumstances. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
