---------------------------- Top of message ----------------------------
>>--> 12-06-02  14:37  S.SHEPPARD     (SHS)    Re: 4.2.3 Upgradedb  - ??

I made the mistake of reading the README file, the first item of which
stated (seemingly unequivocally) that you needed to do an UPGRADEDB.
After letting it sit for some time, I realized that I didn't recall ever
having to do this for an upgrade within versions (well, maybe from 3.1
to 3.7), so I just halted it and brought it up normally and everything
was fine.   Seems like when you specify the upgradedb parm and it's not
needed, there should be some indication given.  But, live and learn.
Thanks
Sam Sheppard
-----------------------------------------------------------------------`


---------------------------- Top of message ----------------------------
>>--> 12-06-02  12:08  ..NETMAIL     ()     Re: 4.2.3 Upgradedb  - ??
Date: Fri, 6 Dec 2002 09:00:18 -0500
From: "Matt Simpson" <msimpson AT UKY DOT EDU>
Subject: Re: 4.2.3 Upgradedb  - ??
To: ADSM-L AT VM.MARIST DOT EDU
_________________________________Top_of_Message_________________________________

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.

-----------------------------------------------------------------------`