>It means that LLA is not simply managing >data sets, as I thought I understood it to do. >Rather, it must be managing >data sets within linklist sets.
Data sets are managed one by one. But directories are managed both one by one and for (every) entire LNKLST. This is where "FREEZE" and "NOFREEZE" come into play. >Still, a long running job will continue to get the old >copy of the module because it is using the old LNKLST. That is a major intent of LKNLST sets, for compatibility reasons. >it sounds safer to define and activate a new LNKLST set when >updating a LNKLST library than to perform a REFRESH or UPDATE It does depend on whether you need an "old" job to be able to access the new module. 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
