On Fri, 22 Feb 2008 08:15:44 -0500, Peter Relson wrote: >> >SETPROG LNKLST DEFINE NAME(COPY) COPYFROM(CURRENT) >> >SETPROG LNKLST ACTIVATE NAME(COPY) > >When a concatenation is opened (for example, the IPL-time LNKLST), the DEB >that is built represents all of the extents that currently exist for all of >the data sets in the concatenation. If the data set grows into another >extent, then that DEB cannot be used to access that additional extent. > >When you activate a new LNKLST set, that LNKLST set has a newly opened >concatenation. Again, its DEB represents all of the extents that currently >exist.
I see. Thank you. Of course, an LLA REFRESH (or UPDATE) is also needed to find the new member. This could be very useful when a product data set in the linklist goes into another extent, especially if it is a product that can be stopped and restarted. or one that is not constantly in use, such as, for example, a compiler. -- 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
