Re: Problem with ADSM on OS/390
1999-09-20 15:29:17
Jorge,
Well I will assume that you do not want to jump right into ADSM V3 without some
up front planning and perhaps communication with your clients. What you need to
do is find the volumes containing all your ADSM V2 libraries and modify your
ADSM JCL to point to them (i.e. by coding volume and unit information). Your MVS
systems programmers should be able to help you with this. Note that they will
have to APF authorize the old SYS1.LINKLIB containing the ADSM V2 code (assuming
they have not already done this for some other reason).
DO NOT start ADSM with the UPGRADEDB parm unless you plan to go to V3 and stay
there. The only way back would be to restore a backup of your database.
Shelby
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Problem with ADSM on OS/390, Rodriguez Jorge
- Re: Problem with ADSM on OS/390, Rodriguez Jorge
- Re: Problem with ADSM on OS/390, Brian Nick
- Re: Problem with ADSM on OS/390, Shelby Beach
- Re: Problem with ADSM on OS/390, Rodriguez Jorge
- Re: Problem with ADSM on OS/390, James SPORER
- Re: Problem with ADSM on OS/390, Rodriguez Jorge
- Re: Problem with ADSM on OS/390,
Shelby Beach <=
- Re: Problem with ADSM on OS/390, Shelby Beach
- Re: Problem with ADSM on OS/390, Rodriguez Jorge
- Re: Problem with ADSM on OS/390, Bill Colwell
- Re: Problem with ADSM on OS/390, Rodriguez Jorge
|
|
|