On Thu, 13 Nov 2008 09:07:48 -0500, Peter Relson <[EMAIL PROTECTED]> wrote:
>Obviously I was wrong in asserting that the publications are correct with >respect to the sentence > > >During unallocation (when LLA is stopped or the system is reIPLed), the >system recatalogs the library data sets to the volume that was current at >LLA initialization. > >Clearly there is no recataloging when "the system is reIPLed". And there is >no recataloging when LLA is stopped. LLA uses what is in the catalog when >it was initialized. That is why stopping and restarting LLA lets LLA use a >newly cataloged (or a recataloged) data set. I suspect that there is (unbeknown to you) recataloging happening when LLA is stopped. Customers with RACF hit a similar situation when trying to move RACF databases. The correct sequence is: (a) tell RACF to deallocate the database (b) copy/recatalog the DB (c) tell RACF to reallocate the DB. If you do (b) first, then when you do (a) RACF closes the DB, and deallocates it, and somewhere in there the system notices that the volume in the catalog changed and sets it back to what it was previously when RACF allocated/OPENed the DB originally. And then things start failing when you get to step (c) because the wrong database (on the old volume) is used. I think that processing is what the documentation was trying to describe, for the non-reIPL case. -- Walt Farrell, CISSP IBM STSM, z/OS Security 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
