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&[email protected] ------- Original Message ------- On Friday, April 7th, 2023 at 1:50 PM, Steve Thompson <[email protected]> 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&[email protected] > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
