Drifting the topic, any product that lets you make changes via command really could use an option to generate a new startup options file that reflected all of the cumulative changes.
It would take some doing to do it in way that preserved comments. And avoided misleading comments. Original options file: FOO = NO ; Turn off the FOO option Assuming FOO was then turned on dynamically, you would not want an updated file that now said FOO = YES ; Turn off the FOO option Perhaps the trick would be to comment out any changed statements and put documenting comments on generated statements, so the result would be ; FOO = NO ; Turn off the FOO option FOO = YES ; Generated by AUTO-OPTION Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Seymour J Metz Sent: Friday, April 17, 2020 1:10 PM To: [email protected] Subject: Re: JES2 parm change - how make sure it's right? Is there an RFE or Share requirement to examine the running JES2 and produce an updated initialization <anachronism>deck</anachronism> that reflects the initial parameters and the dynamic updates? ISAGN. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
