We've had developers fill up spool with unnecessary dumps in the past. Yes, you're correct, they can do as you said, but they don't. It's pure user error.
Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, September 22, 2020 9:29 AM, Seymour J Metz <sme...@gmu.edu> wrote: > Why? My understanding is that you can retrieve an SVC dump from SPOOL and > process it in IPCS. As long as it is in a hold class, what problems does it > cause? > > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU on behalf of > Mark Jacobs 00000224d287a4b1-dmarc-requ...@listserv.ua.edu > > Sent: Tuesday, September 22, 2020 8:11 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: JCL examination prior to execution > > We have developers who put SYSMDUMP output to SYSOUT rather than a dataset. > I'm looking at ways to prevent those jobs from executing until they make JCL > changes. Are there any other exits, processes other than a JES2 exit (looking > at exit 6/60) to do so? > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://secure-web.cisco.com/1gV3QlDEC4whhAOpxGDqlWhtt9-Vum1-s6zU_qe0Q1Q3aPU1FE-A90GeTPpz8jKMhzcZVcfg6b6k5_7EC3d3RcoB3IEi6T0Znq9kwpDNzuoNXOFZy44tM4Lu7OcfqHR66zi9MQdIlEyX18kKI1-uyZrD1tQfcoLhPP0vvD2fG4Az6VK8S5R4449KcpF93hlyFnGO29LfHJWgTQUgwGOmsAwq5HlKn07Fugxsjgnv4dg-XtmWUi0Exd3Pt_p6cfHqmS8_GCvni0WjqRy07gZnTOMCLLVCAV8rTILJ8vtI2JEVZpf7fI3oPe2IP4BYs5pLmzCN6W1nR-27mgDwuZTDw_lMAT-WvQarzSxkU-0L75vCJNbRwEoNOVCHsX_y6FqWNwHDwIxCE2cUcMKYLjwrh1TDYQfEGK83ZQmF7emCkNwQxJTgbVBGIGNYaBrT2EsMk/https%3A%2F%2Fapi.protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40protonmail.com > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > --------------------------------------------------------------------------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
