Sound like the TCPIP NLM is either not loaded or configured properly.
Did you check the DSM.OPT file to see if you have the IP address of the
ADSM server - I don't think that Novell's TCPIP NLM can use DNS so you
either need to put the address in the DSM.OPT file or maybe an entry in
the /ETC/HOSTS file would do.  It's recommended that you stay as current
as possible on the TCPIP, TSA311, and SMDR NLMs.  Some of these may have
corequisites which will require that some other NLMs be brought up to
date also (i.e. CLIB, etc.).  You're not establishing a session with the
ADSM server when you type in LOAD DSMC, that occurs when you enter a
command.

Good luck !!!
Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  Tammi Belcher[SMTP:TBELCH AT SCM1.BEMS.BOEING DOT COM]
>Sent:  Wednesday, May 08, 1996 2:45 AM
>To:    Multiple recipients of list ADSM-L
>Subject:       Novell Netware Version 3.11 Questions.....
>
> 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
>