When you're the only kid in the toy store, you have free reign. Even z HMC uses the 'write-back' function for tuning updates. But z/OS is a complex shared environment. You can't allow random process-altering commands to update common control data sets. Recipe for chaos.
. . . 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 [email protected] OR [email protected] OR [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Monday, December 07, 2015 3:46 PM To: [email protected] Subject: (External):Re: Inquire intrdr default job class On 2015-12-07 09:58, J O Skip Robinson wrote: > 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. > More modern systems, often on desktops, have similar dynamic change facilities. However they often have a "Save as Default" checkbox which does the equivalent of writing the changes back to the init deck and making them persistent. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
