Re: ADSM v3 client with NT

Thanks for the response Andy,

Here is a sample of what is in the dsmerror.log, there seem to be two
sets of errors:

07/30/1998 11:24:14 AltStreamSize(): CreateFile: Win32 RC=32
07/30/1998 11:24:14 AltStreamSize(): CreateFile: Win32 RC=32
07/30/1998 11:24:14 AltStreamSize(): CreateFile: Win32 RC=32
07/30/1998 11:24:14 AltStreamSize(): CreateFile: Win32 RC=32
07/30/1998 11:24:14 AltStreamSize(): CreateFile: Win32 RC=32
07/30/1998 11:25:11 TcpRead: Error reading data, rc: 10054
07/30/1998 11:25:11 sessRecvVerb: Error -50 from call to 'readRtn'.
07/30/1998 11:25:11 ANS1809E Session is lost; initializing session
reopen procedure.
07/30/1998 11:25:11 ANS1809E Session is lost; initializing session
reopen procedure.
07/30/1998 11:25:26 ANS1810E ADSM session has been reestablished.

...

And then:

07/30/1998 12:06:11 ANS1228E Sending of object 'C:\adsm.sys' failed
07/30/1998 12:06:11 ANS1228E Sending of object 'C:\HPFonts' failed
07/30/1998 12:06:11 ANS1228E Sending of object 'C:\Internet Explorer 4.0
Setup' failed
07/30/1998 12:06:11 ANS1228E Sending of object 'C:\Multimedia Files'
failed
07/30/1998 12:06:11 ANS1228E Sending of object 'C:\NTRESKIT' failed
07/30/1998 12:06:11 ANS1228E Sending of object 'C:\Program Files' failed
07/30/1998 12:06:11 ANS1228E Sending of object 'C:\RECYCLER' failed
07/30/1998 12:06:11 ANS1228E Sending of object 'C:\SQLLIB' failed
07/30/1998 12:06:11 ANS1228E Sending of object 'C:\TEMP' failed
07/30/1998 12:06:11 ANS1228E Sending of object 'C:\WIN32APP' failed

I'm not sure about the server logs, versions, etc.  I'm trying to get in
contact with the person in charge of that...

As far as other NT clients, we have other clients that do not get this
error.  However,  we have one NT client that is failing with a different
error.  That one recieves "ANS1030E System ran out of memory. Process
ended."  I'm not sure if that's related or not.

Thanks for the ideas and help,
Chad

Andrew Raibeck wrote:
>
> 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