Can't remember this one  being mentioned and I didn't find anything on a
search of adsm.org so I though I'd toss this to the group...

anyone seen this in their client dsmerror.log ?

06/15/01   15:41:32 cuSignOnResp: Server rejected session; result code: 53

AIX 4.3.3 server running TSM 3.7.2 and the clients seem to mainly be sun
solaris 6 with tsm 3.7.2.0 client code

hugh amounts of zero activity sessions from client to server.... (they have
nothing to do with the scheduler)

3,0,ADSM,07/01/2001,00:50:33,SUNDEV1,oracle,SUN
SOLARIS,1,Tcp/Ip,1,0,0,0,0,0,0,0,0,3,7,7,0,0,4,0,0,0,0,7,2
3,0,ADSM,07/01/2001,11:31:32,TDCCDPD1,,SUN
SOLARIS,1,Tcp/Ip,1,0,0,0,0,0,0,0,0,1,0,0,0,0,4,0,0,0,0,7,2

Even if root simply initiates a "dsmc" session and then does anything to
contact the server (such as a "q sched") it opens a session that terminates,
writes the record to the dsmerror.log and then performs the desired action
and gives the proper info  back to the dsmc session
BUT each action initiates at least two sessions.

Is a little bit of a pain because after only  being up for 45 days, this
specific tsm server is on client session 985,043
The accounting log is rather large.

I know... 4.1 or 4.2, I'll head there quick enough but this seems to have
started out of the blue a couple months ago and I haven't figured it out
yet...

any thoughts ?

Dwight