|
Rolf Mittag wrote:
"2" or "-2" ? "-2" means corrupted data according to http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm?info/rzajp/rzajpmst13.htm
I think that solves the problem of the "2" (and it is a positive 2) in the nullmap. Given that in the MI-level, runtime-level buffer for a file, a +1 in the nullmap indicates a null field, it's logical to assume, by analogy, that +2 in the nullmap would indicate corrupt data. At least, that explanation for the "2" in the nullmap seems to pass Occam's Razor, if nothing else.
Regarding the origin of the file (apparently through Query/400), I have this from the customer:
The file is a dump of a physical file with report summary function count on date. So output file contains all summarized records with break level 1 and a final summarized record break level 0 with datepost field as ++++++.
. . .
Do not know how this can be avoided.
I reiterated my suggestion that he use a 4-digit year date format in the query (not even knowing if this is possible in Query/400), but if anybody else has a better idea, I'll be happy to pass it on.
-- JHHL
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.
midrange.com
