What scheduling mode are you in?  I would bet prompted.  With prompted when
the scheduler service is restarted (service stopped then started, or machine
rebooted) it contacts the TSM server and requests schedules.  After it does
this, then it waits to be contacted by the TSM server.  You may want to try
the TCPCLIENTADDRESS and TCPCLIENTPORT options to specify which tcpip
address the MVS server should use to contact this machine.  Or you can
change the scheduling mode and see if that helps.

James Thompson

From: Tim Brown <tbrown AT CENHUD DOT COM>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TCP/IP communications errors
Date: Tue, 20 Feb 2001 08:45:52 -0500


Have started to recieve these errors on an NT4.0 client, if i reboot the
server
the next scheduled backup event completes but the next subsequent one
fails.
The client is at 4.1.20, the NT server is at service pack 6a, the tsm
server
on os390 is at 4.1.20. the server has 2 nics, i changed the nics and
still
see this problem. tcpip seems to be functioning ok.

any suggestions...

02/19/2001 21:53:01 TcpOpen: TCP/IP error connecting to server.
02/19/2001 21:53:01 sessOpen: Failure in communications open call. rc:
-50
02/19/2001 21:53:01 ANS1017E Session rejected: TCP/IP connection failure




<< tbrown.vcf >>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com