That gave me a headache... For better or worse, I test new OS versions in a LPAR with fully shared DASD, catalogs, RACF and etc. (NJE not MAS). What I envision if this ever comes to pass is that testing will cause way more problems than production. Those test datasets are the ones living on ML2.
If I had a recall on my test lpar, the dataset would be fixed! Cool, I think, I could fix datasets with a hmig/hrecall on the test system. I guess if I found a inaccessible dataset on the newer test system, I could hmig it on production (back level os) then recall it on test! > > It most likely won't happen, but if: > > 1) All DASD Datasets are fixed. > 2) Install new OS without support. > 3) User(s) restore datasets from HSM to DASD with > IMBED/REPLICATE/KEYRANGE attributes. > 4) Implement OS without support > 5) User can't access datasets > > Will HRECOVER then perform the attribute removal, or is the removal only > done on recalls? > > Mark Jacobs > ---------------------------------------------------------------------- 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
