I have been given the task of designing a way to prevent batch jobs from filling up our spool packs. The main culprits are traces with large input files that result in 10's of millions of lines of trace data on the spool volumes. The DD names for these is usually SYSOUT so it appears the best solution is to use SMF exit IEFUSO. I see in IESUSO the Common Exit Parameter Area which has some fields I need: LPAR in the SID field, a JOBNAME field and most importantly the JOBCLASS field. The JOBCLASS is important because the limits are to be enforced on test jobs on and that will be determined by the JOBCLASS the job is running in. This is what my questions are:
1.) I also need the logon id the job is running under. We will allow even test jobs with certain logon ids to continue on. Can I get to that in IEFUSO somehow? 2.) Can I put a WTO to the SYSLOG from this exit? This exit is not going to cancel the job. It will put a message to SYSLOG and the automation's software will do that if further examination determines that should be done. 3.) The exit has a field that is used to pass back a SYSOUT limit extension. I don't really want to do that. What happens if I don't do anything with that field. I also considered JES2 EXIT 9. The manual says EXIT 9 is not used for jobs that exceed OUTLIM values and to use IEFUSO. Thank You, Paul Strauss Integrated Technology Delivery, Global Services, IBM L0DB z/OS MVS/Program Products/Security 150 Kettletown Rd. Southbury, CT 06488 (203) 272-2758 strau...@us.ibm.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html