Hi:
Yes the maxsessions was the cause of the message. However, we have suddenly had the
situation where a number of clients begin to transfer data then abruptly appear to
'stop'. They are qued up and transfer small amounts of data with long periods of
inactivities. When this occurs the restores also appear to drag. Has anyone
experienced this? This is new to our environment and I'm wondering if others have
experienced this after migrating to TSM 3.7.2
Larry Clark
NYS Thruway Authority
>>> [EMAIL PROTECTED] 10/24/00 08:02AM >>>
Larry,
Query Status and look at the "Maximum Sessions" and Maximum Scheduled
Sessions. The maxsessions is the total sessions that can go on at once and
the maxschedsessions is the percent of those that can be initiated by a
schedule. Reset these by "SET MAXSCHEDSESSIONS #" and "SETOPT MAXSESSIONS #"
if they aren't large enough.
-----Original Message-----
From: Lawrence Clark [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 24, 2000 7:25 AM
To: [EMAIL PROTECTED]
Subject: session rejected
Hi:
We are experiencing a number of sessions that seen to sit idle and not
complete. This message, not in the message manual, appears:
ANS1351E Session rejected. All server sessions are currently in use.
Has anyone seen this one before?
Larry Clark
NYS Thruway Authority
