I looked at our inittab, and the only reference to tsm was to start TSM,
not the scheduler.
Is it possible that I don't need that entry at all?  I don't have any
issues with the scheduler...
What I mean is, I can't change what I  don't have!  =)  any thoughts...




                    Rik Foote
                    <Rik_Foote@WESTPACTR        To:     ADSM-L AT VM.MARIST DOT 
EDU
                    UST.CO.NZ>                  cc:
                    Sent by: "ADSM: Dist        Subject:     Re: errors 
(Possible Solution)
                    Stor Manager"
                    <ADSM-L AT VM.MARIST DOT ED
                    U>


                    06/06/2001 03:24 PM
                    Please respond to
                    "ADSM: Dist Stor
                    Manager"





Gidday people.

A while ago I posted a similar problem and got some resolution via the list
and Tivoli Support.
See below - hope it helps.

Rik Foote
IBM NZ
---------------------- Forwarded by Rik Foote/WestpacTrust/NZ on 07/06/2001
08:26 ---------------------------
08:26 ---------------------------

From: Rik Foote on 13/09/2000 09:09

To:   "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
cc:
Subject:  TCP/IP errors - SOLUTION

Hi all.

A while ago I reported this problem. Its fixed now and I thought I'd pass
on what the fix was.

"Bob Bennett from Tivoli has rung back with a fix for our TCP/IP protocol
error problem. He said this fix is mentioned in the 3.7 manuals but not
before.

In /etc/inittab we are starting the scheduler with:
dsmc::once:/usr/bin/dsmc sched                               # ADSM
scheduler

When any output comes from the scheduler the TCP/IP protocol error is
produced...

The fix is to start the scheduler with:
dsmc::once:/usr/bin/dsmc sched > /dev/null 2>&1    # TSM scheduler

Apparently you MUST pipe the output to /dev/null."

Cheers.

Rik
---------------------- Forwarded by Rik Foote/WestpacTrust/NZ on 13/09/2000
08:10 ---------------------------
08:10 ---------------------------

From: Rik Foote on 04/08/2000 08:33

To:   "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
cc:

Subject:  TCP/IP errors?  (Document link not converted)

Hi all.

Running ADSM 3.1.2.50 on Solaris 2.6, client is 3.1.0.8.

We are getting these errors quite frequently in the dsmerror.log. They
happen every 5 seconds for a few hours then taper off to every 20 minutes.

08/01/2000 03:19:39 TcpRead(): recv(): errno = 131
08/01/2000 03:19:39 sessRecvVerb: Error -50 from call to 'readRtn'.
08/01/2000 03:19:39 QueryPendingSchedule(): optSendQuery(): reasoncode =
-50
08/01/2000 03:19:39 ANS1017E Session rejected: TCP/IP connection failure
08/01/2000 03:19:39 ANS1017E Session rejected: TCP/IP connection failure

A bounce of the client dsmc sched task seems to set it all right again, but
often this cannot be done until we arrive at work in the morning (no 7x24
monitoring). Which is too late to complete overnight backups,
unfortunately.

I have asked our LAN/network guys to look into why it might be occurring,
and they will be getting back to me soon I hope.

Has anyone else had this problem, and if so what was the cause/solution?

Thanks in advance.

Rik Foote
Storage Management
WestpacTrust Bank
New Zealand
  The contents of this e-mail are confidential. If you have received this
 communication by mistake, please advise the sender immediately and delete
                     the message and any attachments.
 Westpac Banking Corporation is incorporated in New South Wales, Australia








---------------------------------------------------------------------
The contents of this e-mail are confidential.
The contents of this e-mail are confidential.
If you have received this communication by mistake,
please advise the sender immediately and delete the message and
any attachments.
The views expressed in this e-mail are not necessarily the views of
Westpac Banking Corporation.
Westpac Banking Corporation is incorporated in New South Wales, Australia.
---------------------------------------------------------------------
=========================================================================