×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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?
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
