The usual circumvention for S322 is to increase the TIME= value, not play with exits. For one thing, IEFUTIL can extend the time, but even with no exit in place, the system will abend a job eventually. Be sure to increase the time value on both the job card and on the step (EXEC) card. Exceeding either one will cause S322.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Tuesday, September 13, 2016 9:06 AM To: [email protected] Subject: (External):Re: Bypassing s322 I would compare the Run time(Clock) with CPU TIME. You may be exceeding the CPU Time limit set for that Class. We have an exit that produces a nice little map of CPU usage details. CPU TIME is one of the fields. I recently had a job running in INPUT CLASS X that kept timing out no matter what the TIME was set on the JCL. Turns out the INPUT Class X had a 60 min CPU time limit set. So even though the job ran for 3 hours - it actually used 60.01 minutes of CPU Time. Hence the failure. Always check the job while it is running with SDSF and see if the CPU Time increases quickly. Your task may be in a loop. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Peter > Sent: Tuesday, September 13, 2016 6:05 AM > To: [email protected] > Subject: Bypassing s322 > > 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
