Forgot to do the $D INTRDR before. Only difference is DEVICE=YES on 2.4 and DEVICE=NO on 3.1.
-----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of salva Sent: Tuesday, September 16, 2025 12:29 AM To: [email protected] Subject: Re: JES weirdness 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
