You can't really bypass the system exits, but that doesn't mean that the exits might not include certain "secret" triggers that might allow you to specify a higher time value on the job card. E.G. if the job is in this class and it's this time of day and this job name, then allow/set something higher. Talk to your friendly system programmer responsible for maintaining such controls. (If that's you because you've inherited a situation, you'll have to go do some research.)
In the distant past I remember using Omegamon to dynamically extend the limit of a running job. I don't remember the details at this point, but I think it was just adjusting the existing time limit, not doing something like taking it out of control of the exit or anything like that. Of course, when anybody came to me complaining about an S322, assuming it was already in one of the classes that allowed them to get the max we allowed of 1 or 2 hours of CPU time, my first reaction was always something along the lines of "Are you sure you aren't looping? Are you sure you don't have a tuning opportunity that needs to be fixed?" An hour of CPU time is usually a whole lot of work. Scott On Tue, 13 Sep 2016 18:35:15 +0530, Peter <[email protected]> wrote: >Hello > >I am running which is a long running job but it keeps abending with s322. I >have used all the long running WLM initiators but still abends. I am not >sure if IEFUTL exit is restricting it. > >The error message doesn't produce much information to diagnose. > >Is there a way to bypass any EXIT which might be timing out the Jobs ? > >Peter > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
