Thanks everyone, I knew it was a bad idea, so didn't get too
Now you have woken me up from my dream, I will get back to
From: James Campbell [mailto:[login to unmask email]
Sent: Tuesday, March 21, 2017 7:43 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: db2 z/os upgrade vs v12 new install
"Time is short" - for what?
If it is to get to a version of DB2 that will be supported in
October then you really only need to apply the
compatibility/fallback PTFs for V10 (were you were frozen before
they came out?), migrate to NFM, and then V11 CM. Probably doable,
if you get the appropriate outages.
I did a skip level migration from V7 to V10 using DSN1COPY. Because
of the differences in the internals of tablespaces created in CM8*
and before and V12, I would only attempt this one by an
unload/reload strategy. As was mentioned, can your site afford the
On 20 Mar 2017 at 19:42, Vickers, Mark wrote:
> These are very early thoughts and may get shot down before it
even takes off...
> 1. Time is short and being
at DB2 v10 CM8* means apply maintenance/NFM/ then
> upgrade toolsets and then upgrade DB2.
> (toolset upgrade willy apply to either path)
2. Our DB2 was
> frozen by management in 2013 as it was going away and after
> ERP attempts, we are suddenly back on the grid, so I have 4
years of PTFs to
> apply !
> 3. No skip level migration
> 4. Cloning objects across
would save having to convert tablespaces to UTS and
> hopefully eliminate other depreciated possible issues etc.
> 5. User data is just over
> I do realize there are many reasons why this is probably not a
> idea, especially since it is not supported by IBM, but I was
> whether anyone had successfully done a new install and ported
> objects and data etc. instead of an upgrade ?
> Feel free to shoot flak at this.
-----End Original Message-----