RE: V5R1 upgrade

[rob@xxxxxxxxx]

And this might explain why the first RCLSTG on one of our machines after an
upgrade to V5R1 was amazingly long.  Many multiples of the previous time.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    Dwayne Lindner
                    <Dwayne.Lindner@writ.wesfarme       To:     
"'midrange-l@midrange.com'" <midrange-l@midrange.com>
                    rs.com.au>                          cc:
                    Sent by:                            Fax to:
                    midrange-l-admin@midrange.com       Subject:     RE: V5R1 
upgrade


                    01/09/2002 02:40 AM
                    Please respond to midrange-l







> >
> > Yep, after you do the install, do something to touch all of
> the files on the
> > system - a RCLSTG, a DSPOBJD *ALL/*ALL, anything really
> just touch every
> > file on the system - we found heaps of unconverted files on
> our production
> > system - it's a known problem where the files don't get
> converted during the
> > upgrade but nobody knows why.
>
> "Converted"? From what to what? I'm not aware of any specific
> V5R1 conversion for database objects except for the system
> cross-reference info.
>

All IBM told me at the time was the new V5R1 database format.  Conversion
is
supposed to take place during the upgrade.  Ours didn't (on two out of two
upgrades that we've done so far) and when access attempts were attempted on
production files, things went belly up.  I can't remember the full details,
it was a while ago, but a targetted "touching" of the files fixed the
problems.

Regards,

Dwayne Lindner
Team Leader - Data Centre
Wesfarmers Rural Information Technology
184 Railway Parade, Bassendean WA 6054
Ph: (08) 9273 5365    Mob: 0407 386 693
Email: dwayne.lindner@writ.wesfarmers.com.au

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.