obs 0224d287a4b1-dmarc-requ...@listserv.ua.edu
> Sent: Tuesday, September 22, 2020 9:35 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JCL examination prior to execution
>
> We've had developers fill up spool with unnecessary dumps in the past. Yes,
> you're co
W dniu 22.09.2020 o 14:11, Mark Jacobs pisze:
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
From: IBM Mainframe Discussion List on behalf of
Mark Jacobs <0224d287a4b1-dmarc-requ...@listserv.ua.edu>
Sent: Tuesday, September 22, 2020 9:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL examination prior to execution
We've had developers fill up
t: Tue, Sep 22, 2020 8:35 am
Subject: Re: JCL examination prior to execution
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 en
ussion List IBM-MAIN@LISTSERV.UA.EDU on behalf of
> Mark Jacobs 0224d287a4b1-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
Thanks.
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:06 AM, Binyamin Dissen
wrote:
> IEAVTABX.
>
> Real time, whe
on behalf of
Mark Jacobs <0224d287a4b1-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
IEAVTABX.
Real time, when there is a dump.
Check if SYSMDUMP is to SYSOUT, and then suppress it.
On Tue, 22 Sep 2020 12:11:43 + Mark Jacobs
<0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote:
:>We have developers who put SYSMDUMP output to SYSOUT rather than a dataset.
I'm looking at
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](http
