I don't have any system I can try the command on, but it is interesting the response you got back. Your output from the command would seem to indicate that you have no exits other than exit 0 enabled.
This is an example of what the JES2 command manual shows for the command I gave you. $d exit(*),status=enabled,routines $HASP823 EXIT(5) ROUTINES=(OURCMD,QUEBRK) $HASP823 EXIT(24) ROUTINES=(FIXMAP) $HASP823 EXIT(26) ROUTINES=(FREEMAP) Paul -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Phil Smith III Sent: Tuesday, September 16, 2025 10:52 AM To: [email protected] Subject: Re: JES weirdness Ok, both say: RESPONSE=S0W1 $HASP823 EXIT(0) $HASP823 EXIT(0) STATUS=ENABLED,ENVIRON=JES2,ROUTINES=(), $HASP823 SPLEVEL=CHECK,TRACE=YES,USECOUNT=0 I'm assuming ROUTINES=() means "I see no exits here"? -----Original Message----- From: IBM Mainframe Discussion List <[email protected] <mailto:[email protected]> > On Behalf Of Paul Feller Sent: Tuesday, September 16, 2025 11:47 AM To: [email protected] <mailto:[email protected]> Subject: Re: JES weirdness You could try $d exit(*),status=enabled,routines to see what it shows. It should work on either level. Got this out of the JES2 command manual. Paul -----Original Message----- From: IBM Mainframe Discussion List <[email protected] <mailto:[email protected]> > On Behalf Of Phil Smith III Sent: Tuesday, September 16, 2025 10:34 AM To: [email protected] <mailto:[email protected]> Subject: Re: JES weirdness 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] <mailto:[email protected]> > On Behalf Of salva Sent: Tuesday, September 16, 2025 12:29 AM To: [email protected] <mailto:[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] <mailto:[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] <mailto:[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] <mailto:[email protected]> > On > >Behalf > Of Mike Schwab > >Sent: Monday, September 15, 2025 9:32 PM > >To: [email protected] <mailto:[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] <mailto:[email protected]> > wrote: > > > >> From what I can tell, settings are the same on both systems. > >> > >> -----Original Message----- > >> From: IBM Mainframe Discussion List <[email protected] <mailto:[email protected]> > On > >> Behalf Of salva > >> Sent: Monday, September 15, 2025 4:32 PM > >> To: [email protected] <mailto:[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] <mailto:[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] <mailto:[email protected]> with the > >> > message: INFO IBM-MAIN > >> > > >> > >> ------------------------------------------------------------------- > >> --- For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected] <mailto:[email protected]> with the message: INFO > >> IBM-MAIN > >> > >> ------------------------------------------------------------------- > >> --- For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected] <mailto:[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] <mailto:[email protected]> with the message: INFO IBM-MAIN > > > >--------------------------------------------------------------------- > >- For IBM-MAIN subscribe / signoff / archive access instructions, > >send email to [email protected] <mailto:[email protected]> with the message: INFO > >IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] <mailto:[email protected]> with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] <mailto:[email protected]> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] <mailto:[email protected]> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] <mailto:[email protected]> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] <mailto:[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
