Hi,

we encountered similar problems migrating to OS/390 2.5 and later to
OS/390 2.7. This is indeed very poorly documented (if indeed at all
...).

The thing to do is to start-up the server adress space (only the first
time) with a parameter '/UPGRADEDB', the exec-card being something like:
//SERVER  EXEC PGM=DSMSERV,PARM='/UPGRADEDB',DYNAMNBR=300,TIME=1440, 
//       REGION=128M                                                 

There are some messages indicating that the upgrade is happening, it
doens't take too long (to ADSM standards ...). 
We never had a problem with this, but it might be a good idea to back-up
the database first.

Good luck,
Chris
>-----Original Message-----
>From:  Rodriguez Jorge [SMTP:jrodr5 AT CANTV.COM DOT VE]
>Sent:  maandag 20 september 1999 15:14
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Problem with ADSM V2 on OS/390 2.5
>
>Hi there...
>
>Yesterday, we migrated our operating system in mainframe to OS/390 2.5. We
>are running ADSM V 2 as server, but ADSM doesn´t want to run with the new
>OS. The error message is the follow:
>
>ANR0983W The server database was recorded by a down-level version of the
>server
>program. The UPGRADEDB parameter is required to start the server and
>automatic-
>ally upgrade the database contents to the current server version.  Please
>refer
>to installation instructions for precautionary backup procedures prior to
>doing
>this.
>ANR5963I ADSM server termination complete.
>IEF142I ADSM ADSM - STEP WAS EXECUTED - COND CODE 0001
>
>I've been looking for information in Book Manager, but I haven't found
>anything about.
>
>Thanks in Advance
>
>Jorge Rodríguez
>ADSM Administrator
>CANTV
>Caracas, Venezuela