Okay, I logged onto to work to see what was happening. JES3 shop. Every night at 22:00, the following command is issued: *F J=NETVIEW,NOLOG,N=ALL
I don't know if this is an equivalent command for JES2 ( https://www.ibm.com/docs/en/zos/2.4.0?topic=section-t-reqjobid-set-jobid-attributes ): $T REQJOBID,JESLOG=SUPPRESS or maybe ( https://www.ibm.com/docs/en/zos/2.4.0?topic=crs-t-job-change-jobs-class-scheduling-priority-affinity ): $T J,NETVIEW,SPIN On Fri, Apr 7, 2023 at 1:21 PM Mark Jacobs < 00000224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: > I just tried that. No difference in what I'm observing in JESMSGLG. > > 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 Friday, April 7th, 2023 at 2:13 PM, Steve Horein < > steve.hor...@gmail.com> wrote: > > > > We do START NETVIEW,SUB=MSTR,MSGLEVEL=(0,0) for NetView. > > I have not tried omitting the MSGLEVEL parameter to see if it really > makes > > a difference or not. > > > > On Fri, Apr 7, 2023 at 1:01 PM Mark Jacobs < > > 00000224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: > > > > > The problem is with our Netview STCs. They execute under MSTR and on > our > > > GDPS systems can stay up for months and months at a time. Their > JESMSGLG > > > can grow to several million lines which consumes a non-insignificant > amount > > > of spool space. I was hoping to add JESLOG=SUPPRESS to its job card to > > > suppress this unneeded data. It didn't work. I opened an idea on IBM's > idea > > > portal for future support. > > > > > > 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 Friday, April 7th, 2023 at 1:50 PM, Steve Thompson ste...@wkyr.net > > > wrote: > > > > > > > I think it depends on the started task first issuing a Request > > > > JOB ID CALL to JES. Then you get minimal JES support. At that > > > > point the JOBLOG= may possibly have meaning. Take this with some > > > > salt, because I haven't done this level of programming for many > > > > years and do not currently have the ability to try this on the > > > > system I am using. > > > > > > > > Otherwise I think you have to then issue the equivalent call to > > > > JES for this. > > > > > > > > Steve Thompson > > > > > > > > On 4/7/2023 1:18 PM, Mark Jacobs wrote: > > > > > > > > > This might be a silly question, but does the JESLOG parameter on a > job > > > > > card do anything when a started job executes under the master > subsystem > > > > > rather than under JES2? > > > > > > > > > > Mark Jacobs > > > > > > > > > > Sent from ProtonMail, Swiss-based encrypted email. > > > > > > > > > > GPG Public Key - > > > > > > https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.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 > > > > > > ---------------------------------------------------------------------- > > 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
