Hi Wanda,

I don't know what the deal is, but for starters (if you haven't done so
already), do a QUERY STATUS and check to see if the scheduler is disabled
(either while the server was running or if someone put DISABLESCHEDS YES
in dsmserv.opt), or if someone's been playing with MAXSCHEDSESSIONS. If
that yields a clue, then go through the actlog to see if anything caused
the central scheduler to become disabled.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/08/2001 09:52
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Here's a new one - no Scheduled sessions



We'll the TSM server is nothing if not creative.  We are TSM 4.1.3 on AIX
4.3.3.

Night before last, during the DB BACKUP, the TSM server inexplicably
starting issuing the message:

ANR2571W Scheduled session from node xxxxxxxx has
been denied, scheduled sessions are not currently available.

And it kept doing that for hours.  When we came in the next morning, Q
SESSION showed NO client sessions at all, 3 admin sessions running (all of
them us confused admins trying to figure out what's going on...), still
issing ANR2571 any time a client tried to connect.

We killed the only process running, which was a BACKUP STGPOOL.  And that
left TSM sitting in spendid isolation twiddling its thumbs, still refusing
sessions.

Bouncing the server fixed it.  NOTHING WHATEVER in the TSM log to indicate
other problems.

Anybody seen this one before?