×
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.
Code changes from PTFs to old releases typically will become part of
the base release of the OS in later releases; in the source that is
recompiled for the new release, not as applied PTFs. As I recall, the
changes for those Record Format Level Identifier differences, for which
APARs were opened against V5R3 and V5R4, were part of the base OS IBM i
6.1 [v6r1]. I believe one later nuance may have had an additional APAR
and PTF in v6r1; though presumably such a fix also would have been in
the base of v7r1.
Regardless of similarity to or even by the exact same origin to, an
APAR in v5r3, a problem which exists in v7r1 [IBM i 7.1] is a separate
problem... if even there is a problem. Sometimes what is perceived as
identical between DDS and SQL DDL are in fact legitimate differences.
Not knowing the DDS and the DDL prevents any informed and legitimate
comment about the specific situation; i.e. likely any feedback could
only be a WAG, without the sources.
Also FWiW, the Level Check feature of the Data Management is not
specific to the RPG.
Regards, Chuck
On 31-Jan-2012 15:17 , Kurt Anderson wrote:
After looking this over, there's definitely a PTF that looks like it
would fix the issue, but it's from V5R3. We're at 7.1. I had thought
old PTFs got applied at newer versions of the O/S automatically.
Maybe not?
Rory Hewitt on Tuesday, January 31, 2012 4:58 PM wrote:
Here it is!
http://www-912.ibm.com/n_dir/nas4apar.NSF/1be1a5b61b213a6c86256c23007048f4/21529fcce2f4b070862571010041fe11?OpenDocument
As an Amazon Associate we earn from qualifying purchases.
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.