The point of installing the maintenance is to be proactive in solving
problems, not reactive as suggested in the file you cited.  Then again, you
have a problem (ADSM does not run)!

Seriously, I have done several NetWare 3.11 systems, and have applied at least
the base maintenance level suggested (STRTL3, CLIB3 and TCP187) without having
any problems come back from the NetWare users.  These are old by now, and
pretty much a known quantity in NetWare circles.  There are several newer rele
ases out (STRTL4 and CLIB7), and I have also installed those without problems
too.

NetWare LAN administrators, in my experience, tend to be ultra-conservative
when it comes to maintenance.  The believe in the "If it ain't broke - don't
fix it" school of maintenance, I believe in part because they don't have to do
that much of it (anymore) and are not familiar with the maintenance processes
used by Novell.  Novell doesn't help by not having a consistent method of
applying maintenance (They need SMP or SES!)

Enough of my ramblings.  My advice is to apply all of the maintenance as
suggested.  It will require taking the server down, but you are better to
apply all of it than just a few bits and pieces.

Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Novell Netware Version 3.11 Questions.....
05-08-96 02:59 AM

 We are running an MVS ADSM server Version 2, Release 1, Level 3.  I have
 a Novell Netware client with some questions.  Any help in answering them
 would be greatly appreciated.

 He has upgrade the Novell Netware Version 3.11 (250) User license) with the
 drivers, lan files and NLM's to the level as per the Novell Technical
 Information from Netware.  He has not yet loaded all the patches as per their
 311PTD.EXE file - because it says only load those NLM's that correct the
 problem you are experiencing (the server has been and continues to work
 fine - at least as far as he knows).  When he enters "load dsmc" is appears
 to load OK, but as soon as he tries to do anything, (such as change the
 password) it blows out with an IP error.

 Is there something we are missing in setting up a Novell 3.11 ADSM client?

                         Thanks,
                         Tammi
    "Things which matter most must never be at
       the mercy of things which matter least" - Goethe