|
In this particular case you'l want an indicatore on the the detail line anyway or you will get an awful lot of lines you don't want. Do not turn on theat indicator until after the first cycle. ----------------------------------------------- Booth Martin ResoDirect, ext. 528 BMartin@ResoDirect.com Booth@MartinVT.com http://www.MartinVT.com ----------------------------------------------- -------Original Message------- From: rpg400-l@midrange.com Date: Wednesday, May 22, 2002 16:18:43 To: rpg400-l@midrange.com Subject: Re: Difference bet. Primary and Full procedural file. This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] One obscure question about the cycle. If you are using internally defined printer files with detail, not exception, output won't it write out a detail line BEFORE reading the first record or performing any calculation? Thus you would need to put a record identifying indicator on your I spec and your O spec. This has been my experience, and is my interpretation of page 4 of the ILE RPG Programmers Guide V5R1 available at: http://publib.boulder.ibm.com/html/as400/v5r1/ic2924/books/c0925073.pdf As much as I like the cycle, and use it the few times where it is appropriate, I did confuse the heck out of Jon Paris when I had him look at a snippet I wrote. :-) Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Rich Duzenbury <rduz@westernmidrange.com> Sent by: rpg400-l-admin@midrange.com 05/22/2002 12:03 PM Please respond to rpg400-l To: rpg400-l@midrange.com cc: Fax to: Subject: Re: Difference bet. Primary and Full procedural file. WooHoo! Well said. I've been writing them this way for years, but it took me a long time to come up with the 'right' way. All the examples in our codebase at the time were coded 'in-line', and what a pain to work on. > FMaster IP E K Disk > > IMasterRec > I Division L4 > I Zone L3 > I Territory L2 > I Salesman L1 > > C L4 Exsr NewDivision > C L3 Exsr NewZone > C L2 Exsr NewTerritory > C L1 Exsr NewSalesman > > C Exsr Detail > > CL1 Exsr EndSalesman > CL2 Exsr EndTerritory > CL3 Exsr EndZone > CL4 Exsr EndDivision > CLR Exsr EndProgram > _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
