Hi Chad,

You should check a couple of items:

1) dsmerror.log - what messages are in here that accompany the failure?

2) ADSM server activity log - what messages accompany the failure? Typically
I'd expect to see some kind of ANR04xxx message, i.e. ANR0480W, ANR0481W,
ANR0482W, etc.

Also, make sure your TCP/IP maintenance on MVS is up to date, as there are
several APARs that impact ADSM.

Does this happen on other NT clients as well?

Regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com



ADSM-L AT VM.MARIST DOT EDU on 07/30/98 08:22:47 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: ADSM v3 client with NT


Hello, after lurking on this list for a week now, I must say everyone
here seems to know there stuff and be very helpful.

Now that I've buttered everybody up :) here is my question.  I have an
NT4 workstation with SP3 using ADSM v3.1.0.3 that refuses to do a
backup.  I'm attempting to do an incremental backup from the command
line.  The machine connects to the server (MVS w/ server ver 2.1) and
inspects 35-40 items and then stops.  After a bit this error message
appears.

ANS1809E Session is lost; initializing reopen procedure
          A reconnection attempt will be made in 00:00

The reconnection occurs, but when it reaches the same file it goes
through the same routine.  After the fourth try it gives up on the file
and moves on.  It then will scan a few more objects, get stuck and
repeat the same thing.

Any thoughts would be greatly appreciated.  I've already tried playing
with the TCPBUFFSIZE, TCPWINDOWSIZE, and setting TCPNODELAY to yes, all
with no afffect.

Thanks in advance!
Chad Spurley