>I would have to argue that to obtain the current linklist concatenation, LLA is >most likely looking at the current linklist data set list in memory, and not trying >to use the parmlib progxx members to piece it together. The volsers are right >there. Why not use them?
While almost anything is possible given time and resources, this will almost certainly not be done. The entire intent for allowing VOLSERs on LNKLST library specification is to allow the customer not to have to manipulate the master catalog. It is not to allow the customer to avoid cataloging the data set. >I prefer predictability. >... >Yes, of course the systems must stay up, and the data sets must be moved. >Alternative 3: Wait You didn't say why the data sets "must" be moved. The normal reason for wanting to move a data set is so that you can take a volume offline. Is that your case? Irregardless of LLA, you cannot safely both recatlog and start using the recataloged data set. Recataloging is no different in this regard than copying, renaming, and deleting the original. "Wait" works. 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
