Our Novell administrator has also encountered restore problems on our NW 4.11 
server
running the ADSM client 2.1.0.6.  Using the -todate option caused the server
to abend during initialization locking up the server.  Using -pick did not 
cause the
problem.  We have opened a problem with ADSM Level 1 who passed it on to
Level 2.  I will post their reply when I get it.

Previous Mail List Issues:

I have encountered a problem with using the -vol option during a
restore where the OS is NW 4.11 and ADSM is at 2.1.0.6f.  If one uses
the option, the restore behaves very erratically, sometimes just
hanging, or sometimes getting partway through the process before a
TCPIP error/timeout occurs (i.e.  when doing a PIck from an INActive
list, the restore will go as far as giving you the list after
considerable delay, then will hang/timeout after your selection). I
ran into this again today at MSCSS where Gerard Rose was doing a
restore with -pi -ina -vol (and the other standard options), getting
his list to pick, selecting a file, proceeding with Okay - then
hanging there til TCPIP failure. The instance that I saw with -vol
took 40 minutes for the start of restore to timeout, but when we
dropped -vol, the file restored successfully in 7 minutes.

I have encountered similar problems under NetWare 4.1 and 4.11.  Although
not exactly the same scenario as yours, I have seen unexplainable TCP/IP
connection failures during the restore of inactive files from our MVS
v2.1.12 server.  My solution to date has been to back-level the ADSM
NetWare client to version 2.1.05 temporarily while I do the restore.
Back-leveling is simple to do and will most likely allow you to complete
the restore in a normal time frame.

This problem has only happened a couple of times in my environment so I
haven't pursued a fix through IBM.


Lisa Childs
Hoechst Marion Roussel, Inc.
ADSM Administrator
(816) 966-5990
lisachilds AT hmri DOT com