To All of those who responded to this email indicating that the upgradebd
parameter WAS required, could you write back exactly what your ADSM code
levels were BEFORE your upgrade to 3.1.2.0.

I had a V2 server that I upgraded to 3.1.2.0 and, yes, it did require the
upgradedb parm (which makes sense because the act of going from 2 to 3
requires this). However, my 3.1.1.0 server did not require this parm to
start and run. Now, I am really confused - is something wrong with my V3 to
V3.1.2.0 server since it did not require this parm - all of yours did?

What indicatation did you have that told you that this was necessary since
the server READMEs that I checked make no mention of this requirement?

Thanks,

Jennifer :-(


At 08:37 AM 10/7/98 -0400, you wrote:
>Yes, the Upgrade from 3.1.1.3 to 3.1.2.0 on the NT platform involved a
>\dsmserv.exe upgradedb  command before the database could be opened.
>
>Regards,
>John Stephens
>**********************************
>Date:    Tue, 6 Oct 1998 16:12:02 -0500
>From:    Julie Phinney <jphinney AT HUMANA DOT COM>
>Subject: Upgrade to 3.1.2.0
>
>Does anyone know if the server upgrade from 3.1.1.3 to 3.1.2.0 requires an
>/UPGRADEDB?   I can't seem to find that in the doc, but it was in a hold
>system action  on the PTF for MVS.
>Thanks,
>Julie
>
>----------------------------------------------------------------
>The information transmitted is intended only for the person or entity to
>which it is addressed and may contain confidential and/or privileged
>material.  Any review, retransmission, dissemination or other use of, or
>taking of any action in reliance upon, this information by persons or
>entities other than the intended recipient is prohibited.   If you received
>this in error, please contact the sender and delete the material from any
>computer.
>
>