It depends on the release and how they package it.

Some releases don't need the upgradedb, because there are no changes to the
DB format that require it.
Some releases need the upgradedb, and they package the install stream so it
is done automatically.
Some releases need the upgradedb, and they DON"T package it that way.
Go figure.

The times I have seen the 3rd case, when you try to restart the server after
the upgrade it just won't start, and you get a message that you need the
upgradedb.

I've never seen a case where you can do yourself harm by not doing it; if
you need it, TSM should either do it for you or let you know.


-----Original Message-----
From: Matt Simpson [mailto:msimpson AT UKY DOT EDU]
Sent: Friday, December 06, 2002 9:00 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: 4.2.3 Upgradedb - ??


At 13:54 -0800 12/5/02, Sam Sheppard wrote:
>I have just installed the 4.2.3 server upgrade and have been running the
>UPGRADEDB process for almost 3 hours now.

When we upgraded from 4.2.2 to 4.2.3, we didn't do an Upgradedb.  We
didn't see anything in the install doc that said it was necessary.
How do we know which version upgrades require an upgradedb? And what
happens if we don't do it?  TSM still seems to be running OK .. or as
close to OK as it ever gets.
--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506
<mailto:msimpson AT uky DOT edu>
mainframe --   An obsolete device still used by thousands of obsolete
companies serving billions of obsolete customers and making huge obsolete
profits for their obsolete shareholders.  And this year's run twice as fast
as last year's.