Peter wrote: You've got good replies. Please check all of them!
>I am running which is a long running job but it keeps abending with s322. How long? What is your TIME on JOB and/or EXEC statements? Do you have any IEFUTL exit active? (D PROG,EXIT,EX=SYSSTC.IEFUTL,DIAG can help) What is your JES2 JOBCLASS time definition? Perhaps there are SMF and/or JES2 exits which enforce the time limit despite what you wrote on the JCL. Oh, some JES2 exits may scan your JCL and modify TIME= at will if those exits are written to do that. >I have used all the long running WLM initiators but still abends. I'm not sure WLM can influence that TIME, but I could be wrong. >I am not sure if IEFUTL exit is restricting it. Only if IEFUTL is active as per your SMFPRMxx and you have coded TIME= as others said. >The error message doesn't produce much information to diagnose. This is WAD. >Is there a way to bypass any EXIT which might be timing out the Jobs ? Yes, but if your datacenter enforced the installation of IEFUTL and JES2 JOBCLASS and setup of SMFPRMxx, you may be SOL. If I'm in charge, I would be a BOFH in no TIME= ... ;-) Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
