Chuck,
I think we are talking about two different things. When
doing a V5R3 to V5R4 upgrade, you are required to do a conversion to objects
that contain SQL statements. I wasn't talking about access plans or files,
I was just talking about programs that have SQL statements inside of them.
Here is an excerpt from the IBM V5R4 upgrade guide.
Conversion of objects that contain SQL statements: Chapter 15.
Software reference page 189
In V5R4, the internal representation of SQL statements has been changed to
support statements up to 2 097 152 bytes in length. The first time these
objects are referenced after an upgrade to the new release, the internal
representation of SQL statements in programs, service programs, Distributed
Relational Database ArchitectureT (DRDAR) packages, and extended dynamic
packages that were created before V5R4 is converted automatically to the new
format. This conversion should not significantly affect the time to install
the release, but could be noticed after the installation is complete and
objects that contain SQL statements are referenced for the first time. To
control when these object conversions are performed, use the Start Object
Conversion (STROBJCVN) command after you upgrade. For further information,
see Informational APAR II14080 on the Support for iSeries Web site
(www.ibm.com/servers/eserver/support/iseries/). In the navigation bar, click
Technical databases; then click Authorized Problem Analysis Reports APARs.
STROBJCVN is not just for V6R1 and programs.
Pete
Pete Massiello
iTech Solutions
www.itechsol.com
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Friday, August 22, 2008 1:34 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: unexplained performance problems with SQL after upgrading to
V5R4
AFaIK a STROBJCVN should play no role in the noted upgrade; reload or
not. SQL program access plans are rebuilt automatically by the database
such that no explicit action is required. The only explicit action that
I know that would do that, would be a recompile; i.e. object conversions
will not. Note also: any database file related conversions [e.g. v5r4
alignment] would be implicitly completed by a reload of those objects,
so database *FILE conversion by STROBJCVN is also not an issue.
Regards, Chuck
Pete Massiello wrote:
Something doesn't sound right. Why did they reload all their data for
a V5R3 to V5R4 upgrade? <<SNIP>>
Did you do a STROBJCVN on all the SQLPGMs after the upgrade or are you
relying on first touch?
midrange.com
