Text item: Body.822
If you can't get an IPL soon, you can copy the DSM* modules from
sys1.lpalib to wherever you have the ADSM load modules, and then add a
steplib to the adsm jcl.

Being downlevel on the SVM component is a grip I have with IBM.  Why can't
they post to this list a note that a new level of SVM will be required by
the next release or fix tape, so that we can get the ptf installed and
IPL'ed before we install ADSM?

Bill Colwell
The Charles Stark Draper Laboratory
Cambridge Ma.


_________________________Reply Header_________________________
Author: ADSM-L AT vm.marist DOT edu
Subject: Re: Upgrade V2 databse to V3
12-12-1997 09:02 AM

Date: Fri, 12 Dec 1997 09:02:02 -0500
From: "Spearman, Wayne" <Wms1 AT phsc DOT com>
Subject: Re: Upgrade V2 databse to V3
To: ADSM-L AT vm.marist DOT edu

We had the same problem when we upgraded from v2 to v3. The soulution
for us was to apply PTF UW41097. It hit LPALIB, an IPL was required to
pick up the change.

Hope this helps,

> ----------
> From:         Joubert Eugene Datavia[SMTP:EugeneJo AT TRANSNET.CO DOT ZA]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Friday, December 12, 1997 5:42 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Upgrade V2 databse to V3
>
> Hi
> We are currently running ADSM V2 on MVS 5.22. We were trying to
> upgrade to V3 by using the UPGRADEDB parm on the exec statement. When
> we executed this command, we got the following message :
> ANR5958E SVM is at Mod Level 20, ADSM requires at least Mod Level 22,
> unable to continue.
> What we also notice was that in ANRLEVEL member in the SAMPLIB
> dataset, there is a member (DMSSVM5) that is in SYS1.LPALIB.
> What we need find out is where in the ADSM startup is this member
> referenced, whether it has to be in SYS1.LPALIB or can it be in
> another dataset as long as it is APF authorised
>
> I will be appreciated if we can get some feedback ASAP !!!!
>
> Thanks
>
> Eugene Joubert
> EugeneJo AT Transnet.co DOT za
>