ADSM-L

Re: NT and 2.1.6 client problems continue

1997-06-06 08:37:23
Subject: Re: NT and 2.1.6 client problems continue
From: "Brown, Steven M" <smbrown AT AMP DOT COM>
Date: Fri, 6 Jun 1997 08:37:23 -0400
Len,

Thanks for the input.  NFS is not being used... however, I did notice
that cdrom towers were mentioned as a possible cause... and something
about zero available capacity and music cdroms(?).

While we don't have a tower, we do have a microtest discport (network
cdrom server) with five individual cdrom drives attached to it.  There
is also a single cdrom drive on the server itself and all the cdrom
drives are shared from the server.  Also, these drives never contain
audio cdroms - only data.  Seems like zero available capacity on a file
system (what you have w/a cdrom) should be handled by ADSM and not cause
a divide-by-zero abend.

The question is (if a cdrom is causing the error), what is the actual
problem and how is it solved?  Input from IBM?

Thanks.

Steve Brown
AMP Incorporated


>----------
>From:  Leonard Boyle[SMTP:SNOLEN AT VM.SAS DOT COM]
>Sent:  Thursday, June 05, 1997 6:59 PM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: NT and 2.1.6 client problems continue
>
>On Thu, 5 Jun 1997 11:17:17 -0400 Brown, Steven M said:
>>Tim... just saw your postings - I ran into the same situation w/2.1.6
>>client.  I'm also running NT 3.51 server (on an IBM PC 750 (P90)).
>>Since I couldn't find anything that documented the problem (nor any
>>postings), I assumed it was a quirk of my system/configuration.
>>
>>2.1.6 would install fine but during configuration would blow up w/the
>>divide by zero error.  I removed and re-installed several times
>>(different locations, made sure nothing else was running, etc...) as you
>>did but never got it to work.  As you stated - it was not the music CD
>>situation for me either.  I went back to 2.1.5 to get backups going
>>again.
>>
>>Would really like to find a solution as well...
>>
>>Steve Brown
>>AMP Incorporated
>>
>
>Steve the apar says that an using some nfs software can cause the same
>symptom.
>Are you using any remote file systems that might be triggering the problem?
>
>len
>
>-------------------------------------------------------------------------
>Leonard Boyle, Mainframe support            snolen AT vm.sas DOT com
>SAS Institute Inc.                          ussas4hs@ibmmail
>Room E206                                   (919) 677-8000 ext 6241
>203 SAS Campus Drive
>Cary NC 27513
>