|
Thanks Scott. I will keep these in mind and simplify my code. Sudha Ramanujan SunGard Futures Systems sramanujan@xxxxxxxxxxxxxxxxxx (312) 577 6179 (312) 577 6101 - Fax -----Original Message----- From: Scott Klement [mailto:rpg400-l@xxxxxxxxxxxxxxxx] Sent: Friday, January 07, 2005 4:13 PM To: RPG programming on the AS400 / iSeries Subject: RE: QMHRTVM Hi Sudha, --- Scott Klement http://www.scottklement.com > d WPMsgInfo ds > d Data 1 dim(32767) This type of array logic is no longer necessary. It was required in V3R2 because you didn't have pointer arithmetic... using an array for this sort of thing makes the code more complicated. (And, indeed, the problem with your code not having +1 is due to the array logic. If you used ordinary pointer logic, you wouldn't have needed to use +1, and you wouldn't have made this mistake) Personally, I'd suggest using pointers instead of using an array in this manner. Stick a generic "data" field at the end if you just want to reserve extra memory. > d BytesRet 1 4B 0 > d BytesAvail 5 8B 0 > d MsgSevL 9 12B 0 > d AlertIndex 13 16B 0 Same is true for the 'B' fields. You should be using the 'I' data type instead. If your code needs to run on a V3R1 system, you'll need it to be 'B', but I doubt that you're supporting releases that are that old at this point. I see that you've already gotten it working, so I won't bother describing it further... -- 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.