ADSM V3 on MVS errors
2015-10-04 17:59:02
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
*** Comments From: STEWAJM - Stewart, Mike; 04/28/98 08:51am
FWIW, we don't have the DRM license problem (ADSM MVS 3.1.02).
We don't have a license statement in our options file
for DRM, and don't have any DRM definitions.
Some time back we had a problem with ADSM 0C4'ing if TCP/IP
was taken out from under ADSM. That problem seemed to be
fixed. But about the only time TCP/IP goes down here is
in preperation for an IPL, so ADSM is taken down as well.
So we probably wouldn't notice the TCP/IP problem.
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- ADSM V3 on MVS errors, Julie Phinney
- Re: ADSM V3 on MVS errors, Lambelet,Rene,VEVEY,FC-SIL/INF.
- ADSM V3 on MVS errors, Daniel G. Crouse
- ADSM V3 on MVS errors, Jerry Lawson
- Re: ADSM V3 on MVS errors, Smith, Richard
- ADSM V3 on MVS errors, owner-adsm-l
- ADSM V3 on MVS errors,
owner-adsm-l <=
|
|
|