Also check: Syslog for messages Jes Policies Autooperator/Netview actions
El mar, 16 sept 2025, 17:06, Phil Smith III <[email protected]> escribió: > Well, I did the LONG and compared the output, generated differences. > > Class O > 3.1 only: > 3.1 JESCANCEL=ALLOWED > 3.1 RESOURCE(JOE)=(LIMIT=DEFAULT,ACTION=DEFAULT) > 3.1 RESOURCE(TG)=(LIMIT=DEFAULT,ACTION=DEFAULT) > > 2.4 MSGLEVEL=(0,1) > 3.1 MSGLEVEL=(1,1) > 2.4 OUTDISP=(,) > 3.1 OUTDISP=(HOLD,HOLD) > 2.4 SWA=BELOW > 3.1 SWA=ABOVE > 2.4 SYSSYM=DISALLOW > 3.1 SYSSYM=ALLOW > 2.4 TIME=(000030,00) > 3.1 TIME=(001440,00) > > Class H > 3.1 only: > 3.1 JESCANCEL=ALLOWED > 3.1 RESOURCE(JOE)=(LIMIT=DEFAULT,ACTION=DEFAULT) > 3.1 RESOURCE(TG)=(LIMIT=DEFAULT,ACTION=DEFAULT) > > 3.1 BLP=NO > 2.4 BLP=YES > 2.4 JOURNAL=NO > 3.1 JOURNAL=YES > 2.4 OUTDISP=(,) > 3.1 OUTDISP=(HOLD,HOLD) > 3.1 SYSSYM=ALLOW > 2.4 SYSSYM=DISALLOW > > I changed OUTDISP to (,) for both, verified that it took, then reran my > job--no change. > > Would any of the other differences cause this change in behavior? Doesn't > look like it to me, but what do I know? Did I miss something I should have > $Ded? > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf > Of Chalk, Shelia > Sent: Tuesday, September 16, 2025 7:47 AM > To: [email protected] > Subject: Re: [EXT] Re: JES weirdness > > Hello, > $T JOBCLASS(STC),OUTDISP=(WRITE,WRITE) - change jes on the fly $T > JOBCLASS(STC),MSGCLASS=V - change jes on the fly > $D JOBCLASS(STC),LONG - display > > Then go change it in the parmlib. Jobclass can be changed to outclass(A) > > Thanks > > Shelia Chalk > Mainframe System Programmer > [email protected] > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf > Of salva > Sent: Monday, September 15, 2025 11:29 PM > To: [email protected] > Subject: [EXT] Re: JES weirdness > > Please Note: This email is from an [EXTERNAL] sender. Do not click on > links or attachments unless you expect them from the sender and know the > content is safe. Please contact the Service Desk if you have any concerns > regarding this message. > > > > Try the LONG option: $D JOBCLAS(x),LONG > Also, compare $D INTRDR > > I had a similar problem, but I do not remember the details. > > El mar, 16 sept 2025 a las 6:14, Brian Westerman (< > [email protected]>) escribió: > > > I believe that he is trying to tell you that your settings for the > > MSGCLASS that you are using and the settings for the output DD class > > arE different on your two LPARs. > > > > Brian > > > > On Mon, 15 Sep 2025 23:44:30 -0400, Phil Smith III <[email protected]> > > wrote: > > > > >Ok, and that means...? Sorry, you're clearly saying something > > >significant > > but I can't grok! > > > > > >-----Original Message----- > > >From: IBM Mainframe Discussion List <[email protected]> On > > >Behalf > > Of Mike Schwab > > >Sent: Monday, September 15, 2025 9:32 PM > > >To: [email protected] > > >Subject: Re: JES weirdness > > > > > >The MSGCLASS controls where the JOB log, JCL, and Allocation / steps go. > > >SYSOUT on DD statements control output for that DD. > > > > > >On Mon, Sep 15, 2025 at 5:21 PM Phil Smith III <[email protected]> wrote: > > > > > >> From what I can tell, settings are the same on both systems. > > >> > > >> -----Original Message----- > > >> From: IBM Mainframe Discussion List <[email protected]> On > > >> Behalf Of salva > > >> Sent: Monday, September 15, 2025 4:32 PM > > >> To: [email protected] > > >> Subject: Re: JES weirdness > > >> > > >> Output class parameters can be updated dinamically after JESPRM init. > > >> Also, this changes may remain noted in Jes Checkpoint. > > >> > > >> Try some commands and compare output: > > >> $D Outclass(x) > > >> $D Jobclass(x) > > >> ... > > >> > > >> El lun, 15 sept 2025, 21:57, Phil Smith III <[email protected]> > escribió: > > >> > > >> > More 2.4 vs. 3.1 oddness: on 2.4 if I run a very basic COBOL > > >> > compile/link/run job, I get two SPOOL files in the O queue. One > > >> > has the RUN output; the other has the JESMSGLG, JESJCL, JESYSMSG, > > >> > COMPILE, and LKED output. > > >> > > > >> > The same JCL run on 3.1 puts the JESMSGLG, JESJCL, and JESYSMSG > > >> > on the H queue and two files in the O queue: one with the RUN > > >> > output and the other with the COMPILE and LKED output. > > >> > > > >> > The only differences that I know of are the z/OS version and the > > >> > COBOL compiler version. The JES configuration on 3.1 matches 2.4, > > >> > allegedly (I don't know enough to be sure). > > >> > > > >> > Any ideas? This isn't a huge deal but it's kinda irritating--I > > >> > just a lot of small jobs to verify stuff and keep having to find > > >> > the > > "other" > > >> > file(s) in the other queue. > > >> > > > >> > ----------------------------------------------------------------- > > >> > --- > > >> > -- 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 > > >> > > > > > > > > >-- > > >Mike A Schwab, Springfield IL USA > > >Where do Forest Rangers go to get away from it all? > > > > > >--------------------------------------------------------------------- > > >- 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 > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to [email protected] with the message: INFO IBM-MAIN > ======================================= This email, and any files > transmitted with it, is confidential and intended solely for the use of the > individual or entity to which it is addressed. If you have received this > email in error, please notify the system manager. This message contains > confidential information and is intended only for the individual named. If > you are not the named addressee, you should not disseminate, distribute or > copy this e-mail. Please notify the sender immediately by e-mail if you > have received this message by mistake and delete this e-mail from your > system. If you are not the intended recipient, you are notified that > disclosing, copying, distributing or taking any action in reliance on the > contents of this information is strictly prohibited. > > ---------------------------------------------------------------------- > 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
