Gil's point raises an issue more critical than just the question at hand. Once upon a time, 'reading JES2 parms' would have been a reasonable strategy in general for determining how JES2 runs. Since the advent of pervasive dynamic changes, however, the init deck as coded is no longer a reliable window into JES2 processing. A great many changes are now made simply by command. Old values are ignored on hot start and in many cases even on all-system warm start. Only a cold start will reinstate coded parm values that might actually be years out of date.
There is today no substitute for a display command with full detail. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com OR jo.skip.robin...@att.net OR jo.skip.robin...@gmail.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, December 07, 2015 7:18 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Inquire intrdr default job class On Mon, 7 Dec 2015 16:15:16 +0100, Gabor Hoffer wrote: >Default jobclass of INTRDR, so before submit. > Might that be available by tediously parsing a PARMLIB member? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
