Last weekend I completed upgrading TSM from 4.2.3 to 5.2.2. The upgrade went very smoothly and with hardly any problems. I do have three issues so far.
During the expiration process I receive "hundreds" of ANR0106E messages Imarqry.(4863) Unexpected error 2 fetching row in table "archive.descriptions". This doesn't seem to affect the correct functioning of the expiration process. This looks like a known problem addressed by IC39132. I also see many ANR0480W messages session xxx for node yyy () connection with client severed. This happens for many of my clients that I use schedule=prompted. Although annoying, it also seems that the sessions are working OK. Looks like this issue may also be already addressed by IC37862. Perhaps my biggest "gotcha" is that the maxnummp setting for each nodename no longer seems to be honored. This is especially true for clients that have resourceutilization set greater than 1. This has caused havoc with my tape drive use, mostly overcommitting the resource and making everything run longer. Is anyone else experiencing this behaviour with 5.2.2? Thanks, Rod Hroblak ADP __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html
