|
James, Unforunately, I am not aware of any way to suppress the level 0 records on a Query/400 summary output file. And there could easily be ++++++ dates at other levels. I don't think a four digit year will help, because, the customer is summarizing the file by date. That means that the grand total record does not have a valid date. Perhaps Query/400 is not the best way to summarize a file. I would recommend using SQL, Query Manager, or Format Data to summarize the file. Anyway, I will try to replicate this problem tomorrow and see if I can update the file. Peter Lunde lunde@xxxxxxxxxxxx ============================================================ From: "James H H Lampert" <jamesl@xxxxxxxxxxx> Date: 2006/04/25 Tue PM 12:00:30 EST To: MI Programming on the AS400 / iSeries <mi400@xxxxxxxxxxxx> Subject: Re: [MI400] Weird problem a customer is having with a file (James H H Lampert) <snip> 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.