Hi Mauro,

I saw the same problem with sessions within hours of 3.1.2.50 and
after 36 hours we had 5 festering sessions.  I reported it as PMR
83211 and then went back to 3.1.2.42 as we would soon run out of
session slots at that rate!  I believe others have also reported
this problem but as yet there is no fix available.

Other problems at 3.1.2.50 that we have seen are the invalid replies
from the current_timestamp and current_date (using select built-in
funcions).  [APAR taken out for this is IY06877]

Also the new functionality relating to session throughput gives
worrying references to admin sessions when you do something like:

  query sess maxthr=100

and really it should be talking only about client sessions - as you
wouldn't want to risk thinking of cancelling your admin sessions by
mistake.  [APAR for this is IY06909].

I haven't seen the tape drive problems - that needs reporting, it
shouldn't do that?

Anyone care to share how TSM 3.7.1 server is going on a large system?

Anyone upgraded a large system yet from 3.1 to 3.7.1?

Best regards, Sheelagh
------------------------------------------------------------------------
Sheelagh Treweek                   Email: sheelagh.treweek AT oucs.ox.ac DOT uk
Sheelagh Treweek                   Email: sheelagh.treweek AT oucs.ox.ac DOT uk
Oxford University Computing Services           Tel:   +44 (0)1865 273205
13 Banbury Road, Oxford, OX2 6NN, UK           Fax:   +44 (0)1865 273275