On Wed, 21 May 2008 13:53:43 -0400, Daniel McLaughlin wrote: >In your PARMLIB create: > > BROWSE SYS1.TEST.ZOS17.PARMLIB(PROGDM) - 01.01 Line 00000000 Col >001 080 > Command ===> Scroll ===> >CSR >********************************* Top of Data >********************************* >LNKLST DEFINE NAME(LNKLSTAA) COPYFROM(CURRENT) >LNKLST ADD NAME(LNKLSTAA) DSN(SYS4.FA.V8R8M2.LOAD) > VOLUME(O2A010) >LNKLST ACTIVATE NAME(LNKLSTAA) > >a member that looks like this. Then on the console SET PROG=DM (for my >example).
If you don't specify ATTOP or AFTER(...) you get ATBOTTOM. I like to use AFTER to put it after the data set that I am replacing and then issue a LNKLST DELETE for the old one. That leaves the new data set in the same place in the LNKLST set as the old one. You can also use SETPROG with similar commands: setprog lnklst,define,name(update_prodname),copyfrom(current) setprog lnklst,add,name(update_prodname),dsn(new.dataset),after (old.dataset) setprog lnklst,delete,name(update_prodname),dsn (old.dataset) setprog lnklst,activate,name(update_prodname) Note that the name of the LNKLST set can be 16 characters and does not have to begin with LNKLST. I like to set it to a name that clues me in as to why I created the new LNKLST set. Also note that while the System Commands manual describes the commands as keyword=value and Init and Tuning says keyword(value), the implementation allows you to specify them either way. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
