I am preparing a change to move a few linklist datasets to another volume. As I have done many times in the past, I created new copies of the datasets, and recatloged them with the new volser, knowing the linklist will continue to use the old datasets until the planned IPL. Likewise, LLA was apparently unaffected. I did this on four systems in the sysplex.
LLA was restarted on one system, and we subsequently started getting fetch I/O errors. A little checking revealed that LLA was using the cataloged datasets and not the linklist datasets. I recataloged the datasets and restarted LLA again to get around this issue. However, this got me to wondering why LLA wasn't using the linklist concatenation as expected. A little research of the Init and Tuning Guide uncovered a little-known section titled, "Recataloging LLA-Managed Data Sets While LLA Is Active." <rant> This entire section is disturbing. The first paragraph says that when LLA is stopped or the system is IPLed, the system will recatalog datasets to the volume that was current at LLA initialization. Say what?! Ok, that isn't what actually happened when LLA restarted, so the statement is wrong. Nevermind that if I went and clicked on the load icon to IPL the system that I seriously doubt any recataloging would occur (except when I have to manually correct the damage I caused). Further down in the section under item 3, it states that "Recataloged linklist libraries cannot be put back into LLA management. This causes fetch failures." No kidding! That's because LLA isn't using the linklist concatenation to read directories. Does anyone else see the irony in this little scenario? </rant> ---------------------------------------------------------------------- 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
