|
Are you sure the L1 indicator is only on the field in the primary record and not the similar field in the secondary file? --------------------------------- Booth Martin http://www.martinvt.com --------------------------------- -------Original Message------- From: RPG programming on the AS400 / iSeries Date: 04/07/05 20:39:48 To: 'RPG programming on the AS400 / iSeries' Subject: RE: primary and secondary files, match fields, summarizing/printing single line per key Mike, Sudha, Rick, Thank you for answering. I'm sorry if my replies are coming in late. I'm in a GMT+8 time zone. I can say for certain (using the interactive debugger) that all the control fields have the same value, and *INL1 is triggered twice every time, once for the primary and another time for the secondary. I also tried Rick's suggestion of using the MR indicator, but the result is the same. Is this perhaps a limitation of the language? And can't be done without the use of an extract file as Mike suggested? -- Carl Mañoso "It is not real work unless you would rather be doing something else." [J.M.BARRIE] > -----Original Message----- > From: Barton, Mike > Sent: Thursday, April 07, 2005 11:20 PM > > Carl > using matching records the way u are should be able > to achieve what you want. > I suggest you check the values in all the *INL1 fields to > accertain that they are the same for the 2 separate lines. > L1 will only come on after all records from both files have > been read. > > One only other way is to create an extract file from the > 2 (or more files) and then read the result file with > level breaks. > > HTH > > Mike > > -----Original Message----- > From: "Mañoso, Carl" [mailto:ManosoCS@xxxxxxxxxxxxxxxxx] > Sent: 07 April 2005 01:29 > To: rpg400-l (E-mail) > Subject: primary and secondary files, match fields, > summarizing/printing > s ingle line per key > > > Mabuhay RPG gurus! > > A colleague has this problem, which I cannot solve, involving > primary and > secondary files and match fields. Here are the relevant code > fragments and a > sample output. A record pertaining to a particular key > doesn't necessarily > have to be in both files. > > SAMPLE PROGRAM > ============== > IPLNMJ1 01 > I PLOYER M6 > I PLOMKTL3M5 > I PLOIGRL2M4 > I PLOCSZL1M3 > I PLOCVTL1M2 > I PLOITML1M1 > IINVSUM 02 > I IVSYER M6 > I IVSMKTL3M5 > I IVSIGRL2M4 > I IVSCSZL1M3 > I IVSCVTL1M2 > I IVSITML1M1 > ---------- > MAIN > ---------- > . > . > . > CL1 EXSR PRTDTL > . > . > > > SAMPLE OUTPUT > ============= > Cur > Mo. Total > Item_ Size__ Variety___ Market_PO_Description____ > ___PO__ Shipmts > CONC FOR DC OR DIRECT > > *1* 01160 12-46 PO EUROPE MARKET 1,000 > > *1* 01160 12-46 PO EUROPE MARKET > 204 > > *2* 01254 6-10 J- EUROPE MARKET > 1,000 > *2* 01254 6-10 J- EUROPE MARKET > 272 > > Sub-total > 2,000 476 > > > QUESTION > ======== > *INL1 controls the printing of a detail line. In the sample > output above, > lines indicated by *1* should supposedly appear in one line, > lines indicated > by *2* also in one line. However, as you can see, *INL1 is > triggered twice, > one for each file (primary and secondary), so that they were > printed on two > separate lines. Printing on every other setting of *INL1 also > doesn't work > because the records pertaining to a particular key need not > appear in both > files. > > Does anybody here knows of a technique that will print the > summary of a > record with details coming from two separate files in a > single line? We are > using RPG/400 on V4R5M0 (by order of our BDFL). > > Thanks in advance. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. .
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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.