I am in the processes of upgrading to that release on z/OS 1.4. What has IBM said about this? I would report it as a problem ASAP. I am on 5.1.8.1. What release were you at that didn't have it? I have to get on 5.2 to handle the Win2003 SYSTEM STATE backups. My options may be limited, but I don't think I want to jump into the frying pan you are in. Matt
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Weichler, Stefan Sent: Tuesday, August 10, 2004 8:33 AM To: [EMAIL PROTECTED] Subject: TSM 5.2.3.1 SMUTIL Problem Hello, last week we updated our 6 TSM-Sever at the mainframe (z/OS 1.4) to 5.2.3.1. Today we found following errors in our actlog: 2004-08-09 22:30 ANR9999D SMUTIL(12815): ThreadId<10591> Session 5837 attempted to associate itself with the wrong node Callchain follows: pkShowCallChain+2E2 <- outDiagf+27E <- SmAddSessionToAffinityCluster+27C <- SmNodeSession+1D6 <- SmSchedSession+114 <- HandleNodeSession+21F8 <- DoNodeSched+76 <- smExecuteSession+3330 <- Bpx1Session+222 <- pkThreadHead+4FA (SESSION: 5837) 2004-08-09 22:30 ANR9999D SMUTIL(12817): ThreadId<10591> Statistics for Session 5837 will not be kept Callchain follows: pkShowCallChain+2E2 <- outDiagf+27E <- SmAddSessionToAffinityCluster+2AE <- SmNodeSession+1D6 <- SmSchedSession+114 <- HandleNodeSession+21F8 <- DoNodeSched+76 <- smExecuteSession+3330 <- Bpx1Session+222 <- pkThreadHead+4FA (SESSION: 5837) Any ideas? Is this a well-knwon problem? Should i open a pmr at ibm? Regards Stefan Weichler
