*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.*
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If I'm not sure of a command,I put it into a file and issue it via ISFSLASH.

One store of these commands can be a PDS. Just add them in some logical
sequence. When you can't remember,"what was that command". Just refer to
the command file.

I find the JES2 commands incredibly cryptic and from time to time, we're
asked to $T a jobclass. That's when my file comes in handy.

I issue the commands via a REXX program which reads the PDS. Easy to
comment out a command when parsing it to decide when to issue it or not.


On Sat, Apr 18, 2020 at 6:35 AM Charles Mills <[email protected]> wrote:

> 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
>


-- 
Wayne V. Bickerdike

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to