Julie,

I have encountered both of these problems on an ADSM/MVS version 2.1
server.  We used the following techniques to work around these nuisances:

1) We went ahead and "licensed" the DRM feature on the server (i.e. we
issued the register license command).  We notified our IBM contact of this
action and agreed to start paying for this option when/if we started using
it.

2) We set up a procedure to automatically recycle the ADSM server whenever
TCP/IP was recycled.

I realize that these "solutions" are trivial, but they work.  I hope this
helps.

DanC
=============================================
Daniel G. Crouse
IBM Certified Specialist - ADSM
Mainstar Software Corporation
Storage and Recovery Solutions
  URL:  <www.mainstar.com>
Email:  Dan.Crouse AT mainstar DOT com <mailto:Dan.Crouse AT Mainstar DOT com>
Vmail:  800-233-6838
Voice:  404-714-5754
   Fax:  770-682-7739
=============================================

> Date:    Mon, 27 Apr 1998 18:54:42 -0500
> From:    Julie Phinney <jphinney AT HUMANA DOT COM>
> Subject: ADSM V3 on MVS errors
>
> Has anyone had either of these problems?  How did you get around them?
> 1.On startup of the ADSM server, I get an error saying not in compliance
> with License terms.  If I do a Q LIC it says I am using the DRM but don't
> have it licensed.  (I'm not using it)
> 2. After recycling TCP/IP 3.1 on MVS, ADSM sometimes refuses all TCP/IP
> sessions until it is recycled as well.
> Thanks!
> Julie