|
Hmm.. out of all the solutions, I think I like this one the best. As I understand it, my programs remain exactly the same, but I add the externally defined data structure to my programs redefining the range of my array. There are a few problems with this on, such as when D6 moves in the file layout, I will have to change the program to match. There are so many ways to do it, but not the one way I would love. A R CODEFLA01 <SNIP> A D6(1) P 9 0 A D6(2) P 9 0 etc... But I am quite sure this is never going to happen. Well, thanks again, I have a bit to think about, gotta find one that works best for all circumstances. Regards, Jim Langston Joel Fritz wrote: > Another approach uses an externally defined data structure with an array > overlay: > > Dcodefrec e ds extname(codeflc01) inz > D D6 1 30p 0 dim(6) > > Note that the beginning and end of D6 are arbitrary and just accomodate six > 9 packed numbers (I hope.) The beginning should be the offset of the first > field and the end should be the end of the last field. Don't know if it has > any advantage at all over the pointer method. I do know it violates style > criteria for overlays. I've used this a lot with records with buckets in > them. Also works nice for moving one line of screen data into a file > record. > > > -----Original Message----- > > From: Jim Langston [mailto:jlangston@conexfreight.com] > > Sent: Wednesday, November 03, 1999 7:47 AM > > To: RPG400-L@midrange.com > > Subject: Re: DDS arrays > > > > > > A R CODEFLC01 > > <SNIP> > > A CFDX1 9P 0 > > COLHDG('Decimal Value 1') > > A CFDX2 9P 0 > > COLHDG('Decimal Value 1') > > A CFDX3 9P 0 > > COLHDG('Decimal Value 1') > > A CFDX4 9P 0 > > COLHDG('Decimal Value 1') > > A CFDX5 9P 0 > > COLHDG('Decimal Value 1') > > A CFDX6 9P 0 > > COLHDG('Decimal Value 1') > > > > FCODEFLC01 IF K DISK > > > > D ArrayPtr P * INZ(%ADDR(CFDX1)) > > D D6 P 9 0 DIM(6) BASED(ArraPtr) > > > > Would that work in this case? I remember hearing somewhere > > that fields > > were not guaranteed to be contiguous in memory, is that true > > for external > > declarations also? If it would work this way, I think it > > would be the way > > to go, everything is self documented. > > > > This is what I am going to try to see if it works. > > > > Thank you for your help, Eric, Douglas and Peter, I appreciate it. > > > > Regards, > > > > Jim Langston > > > > <SNIP> > > > > +--- > > | This is the RPG/400 Mailing List! > > | To submit a new message, send your mail to RPG400-L@midrange.com. > > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > > | To unsubscribe from this list send email to > > RPG400-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > > david@midrange.com > > +--- > > > +--- > | This is the RPG/400 Mailing List! > | To submit a new message, send your mail to RPG400-L@midrange.com. > | To subscribe to this list send email to RPG400-L-SUB@midrange.com. > | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.