We're preparing to upgrade our TSM 5.1.6 server to 5.2.x. We run on z/OS and have seen the writeup on apar PQ80211. IBM recommends either coming up to TSM 5.1.7.3 and running CLEANUP BACKUPGROUPS prior to beginning the upgrade to 5.2.x, or upgrading straight to 5.2.1.3 (which doesn't seem to be available yet - don't you just love being on the edge?) to get the fix for the apar. There's also a zap available to fix the problem with CLEANUP BACKUPGROUPS. Has anyone been through this? What seems to be the cleanest way to deal with this issue?
Joe Howell Shelter Insurance Companies Columbia, MO --------------------------------- Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard
