> >SETPROG LNKLST DEFINE NAME(COPY) COPYFROM(CURRENT) > >SETPROG LNKLST ACTIVATE NAME(COPY)
>Can you please explain why you recommend this? What does it accomplish? This functionality is one of the main reasons dynamic LNKLST was developed (the other main one, of course, being to add another data set). 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. But since "current" is after the new extent showed up, it will have that extent represented, and thus can be used to access that additional extent. Of course, without explicit (unpredictably dangerous, don't "complain" to IBM if something bad happens) action (LNKLST UPDATE), the newly activated LNKLST set is used only by jobs that start after that activation has occurred Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
