On Mon, May 15, 2017 at 6:26 PM, Charles Mills <[email protected]> wrote:
> This is the world's dumbest question if you're a sysprog but I'm a > developer > with nearly zero sysprog experience. > > Whenever in the past that I have taken a quick look at SET PROG=(xx,yy) I > assumed that PROGxx + PROGyy in the parmlib concatenation *totally > replaced* > the contents of whatever PROGaa and PROGbb had been specified in IEASYSxx > at > IPL. > > But as I read the documentation now I get the impression instead that SET > PROG=(xx,yy) causes PROGxx and PROGyy to be processed essentially as > scripts > each line of which incrementally modifies whatever is already in effect. In > other words, if I entered SET PROG=ZZ and PROGZZ was devoid of statements > other than comments then the system would be left unchanged, regardless of > what had been in PROGaa and PROGbb at IPL. If PROGZZ contained one APF ADD > statement, then that DSN would get added to the APF list, much as if I had > entered SETPROG APF,ADD,DSN=...; and every other system parameter would be > left unchanged. > > Is my latter impression more correct? > > (And yes, I'm contemplating playing with a sandbox system, not a production > system. I get that this is serious stuff. That's why I'm asking.) > > Thanks, > > Charles > > You are correct. What you have in the PROGnn member is an "update" to whatever. Anything which is not changed is left as it was. I do your APF ADD type operation as my normal (via SET PROG=nn and not SETPROG APF,ADD,...) Why? Because if it is correct, I can simply edit the production PROGnn member and copy in the one which worked. -- Advertising is a valuable economic factor because it is the cheapest way of selling goods, particularly if the goods are worthless. -- Sinclair Lewis Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
