On my test lpar I applied some DB2 maintenance to a module. I could browse the module and indeed the fix was on.
On my production LPAR, I wanted to copy that module over to the product libraries, so I did a TSO =3.3 copy and placed it in the production load library. I browsed that production load library, and the fix was not on. I browsed the original library, and the fix was not on. The original library is cataloged to the same volume (usercat), so I know it was pointing to the same place. I tried LLA, refreshes, inactivating LLA, and even IPL'ing, but could not see the fix on the load libraries from my production LPAR (still looked good in test). Finally, on the TSO =1 screen, I entered the dataset name AND the volser and then I could see that the fix was on. I went out and went back in without specifying the volser, and the fix was STILL on. It appears it was cached or something, even through an IPL....? Any suggestions? Dennis ---------------------------------------------------------------------- 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
