Hi Robert,
              It happened to us. Although  I am referring to our site having
AIX version ADSM server v3. and NT client. The solution might interest you.
We had initially a v2 client. Subsequently we went in for for a v3 Client.
Now this v3 Client had functioned correctly  for 2 months and came  up with
all kinds of read errors.

Solution : The concerned person did not reboot the client node after having
uninstalled the older version. Thus files from a new version of the ADSM
seems to have been marked for deletion . Thus after a reboot of the node it
started giving all kinds of read errors etc.  After pondering over variables
like permissions , I decided to reinstall the client. Since last three weeks
there was no problem.

Please try and reinstall your client.

Hope this helps


Sri



> -----Original Message-----
> From: ROBERT OTT [SMTP:Robert.Ott AT TLC.STATE.TX DOT US]
> Sent: Monday, August 24, 1998 3:48 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Netware & OFM
>
> Hello,
>
> We are running an ADSM for MVS Ver 3., Rel 1., Lev. 0.2 server and our
> client is Netware 4.11 with all the latest service patches.  We have
> Open File Manager (OFM)  ver. 3.1 running on this client.
>
> We are receiving 'read failure' errors from several of the databases
> that need to be backed up.  They are not always the same db's either.
> These db's can't be shutdown to run the backups, at this time.
>
> I'm hoping for any input regarding the use of 'OFM' with ADSM.  Any
> suggestions would be greatly appreciated.
>
> Thanks in advance,
> Robert