Thanks TOM for the information.... one more related question.........

Since the UPGRADEDB is required, I would presume that there are some updates
to the database tables (or something along those lines). If I wanted to
deinstall 3.1.2.0 code, leaving my database and recovery log in place, and
then install my base code again (plus pre 3.1.2.0 ptfs) for any reason, can
I just restore a pre 3.1.2.0 backup over the existing DB and log to getback
to a pre 3.1.2.0 state? Or do I have do issue a dsmserv format before the
restore db?

Thanks for your clarification!!
P.S. Do you have any influence with getting the README files updated to
reflect this great information that you have clarified for us?

Jenn


At 01:41 PM 10/8/98 PDT, you wrote:
>OK, here is the word on Upgradedb to 3.1.2.0. UPGRADEDB is required! However,
>on AIX it is done automatically from the scripts provided with ADSM install
>process. Once the upgrade is done, the server halts. For N/T, the UPGRADEDB
>is also done automatically. If the DSMSERV command includes UPGRADEDB and
>RUNFILE as parameters, the server is halted after the upgrade. If RUNFILE is
>not included, the server stays up after the upgrade. For MVS and SUN, the
>UPGRADEDB must be explicilty specified. I'm not sure about the HP server.
>If in doubt, specify the UPGRADEDB parameter. It will be ignored if the
>upgrade has already taken place. Or, start the server, either background or
>foreground. If the parameter is required but not specified, the server will
>not start, but will issue a message to forgeround attempts. Also, the
>UPGRADEDB requirement is discussed in the Quick Start Guide.
>
>Tom Brooks
>ADSM Development
>
>