Julie,

        We also had this problem at one time... When we upgraded to V3
we also upgraded our TCP/IP software, and that seems to have fixed the
problem.

Rick Smith
Maritz, Inc.
Storage & Security Administration
smithrr AT maritz DOT com
(314) 827-1584

> ----------
> From:         Jerry Lawson[SMTP:jlawson AT THEHARTFORD DOT COM]
> Sent:         Tuesday, April 28, 1998 8:03 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      ADSM V3 on MVS errors
>
> ---------------------------- Forwarded with Changes
> ---------------------------
> From: owner-adsm-l AT VM.MARIST DOT EDU at SMTP
> Date: 4/27/98 8:31PM
> To: Jerry Lawson at ASUPO
> *To: ADSM-L AT VM.MARIST DOT EDU at SMTP
> Subject: ADSM V3 on MVS errors
> ----------------------------------------------------------------------
> ---------
> Julie -
>
> FWIW, there was a similar discussion about V3 licensing a couple of
> weeks
> ago, but it applied to an AIX box, I think. There was, however, a PTF
> issued,
> so maybe there is a similar fix for MVS.
>
> As for TCP/IP, we have had the same problem, on occasion, with V2.  We
> now
> recycle ADSM whenever we recycle TCP/IP as a matter of course.
>
> Jerry Lawson
> jlawson AT thehartford DOT com
>
>
>
> ______________________________ Forward Header
> __________________________________
> Subject: ADSM V3 on MVS errors
> Author:  owner-adsm-l AT VM.MARIST DOT EDU at SMTP
> Date:    4/27/98 8:31 PM
>
>
> 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
>