Charles Mills wrote:
>This is the world's dumbest question if you're a sysprog but I'm a developer
>with nearly zero sysprog experience.
This is not a dumb question. Only wise people ask questions! ;-)
>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.
Sort of 'replace', yes, but see my comments below.
>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.
True.
>Is my latter impression more correct?
Yes. Look at these two I did in the past:
PROGXX:
EXIT DELETE
EXITNAME(SYS.IEFUTL)
MODNAME(IEFUTL)
LPA DELETE MODNAME(IEFUTL) FORCE(YES) CURRENT
Later after assembling a new IEFUTL, I did this:
PROGYY:
LPA ADD MODNAME(IEFUTL)
DSNAME(SYS??.LPALIB)
EXIT ADD EXITNAME(SYS.IEFUTL) MODNAME(IEFUTL) STATE(ACTIVE)
DSNAME(SYS??.LPALIB)
>I'm more familiar with SET SMF=xx and that's how it works. SMFPRMxx does not
>add to what came before; it replaces it.
True.
What I usually do is:
I create a brand new SMFPRMxx. Modify the DSNAME or whatever (remove IEFUTL for
example) and then do my SET SMF=xx. When finished, I issue my SET SMF=xx last
used in IPL.
All in all, I don't touch the *official* live PROGxx and SMFPRMxx members.
Groete / Greetings
Elardus Engelbrecht
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
