|
When I see "MMVI" I know it is 2006, but do all others who come after me? Maybe. When I see an @ or $ or # in a variable name, I see System/3 RPGII legacy code that's been ported and my first instinct is to delete it and rewrite it. -Bob Cozzi www.RPGxTools.com RPG xTools - Enjoy programming again. -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael_Schutte@xxxxxxxxxxxx Sent: Monday, April 24, 2006 3:23 PM To: RPG programming on the AS400 / iSeries Subject: RE: EXTFLD Question Okay thanks... that's what I was looking for. RBFUTUSEA is defined in a file on the FSPEC. As for the "@", I'm just copying code from other renames, keep it uniform. But why does it suck so bad? It's not a big deal. When I see the "@", I immediately know that the field is program described. Also, the last time I checked, you can't begin a field with a number. Maybe that's changed with V5R3. Michael Schutte "Bob Cozzi" <cozzi@xxxxxxxxx> Sent by: To rpg400-l-bounces+ "'RPG programming on the AS400 / michael_schutte=b iSeries'" <rpg400-l@xxxxxxxxxxxx> obevans.com@midra cc nge.com Subject RE: EXTFLD Question 04/24/2006 04:16 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@midrang e.com> Once you override the external field name using EXTFLD, that name no longer exists in the program. If you are able to refer to RBFUTUSEA in your code, then you have it defined elsewhere in the program, probably via a file or another data structure. In either case, RBFUTUSEA does not exist in the 12DBRC data structure ("at signs" in names suck, by the way) and therefore moving anything into it, does not get reflected in FutureUseA or its overlaid subfields. -Bob Cozzi www.RPGxTools.com RPG xTools - Enjoy programming again. -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael_Schutte@xxxxxxxxxxxx Sent: Monday, April 24, 2006 3:11 PM To: rpg400-l@xxxxxxxxxxxx Subject: EXTFLD Question D @12DBRC E DS EXTNAME(BEF012) D FutureUseA E ExtFld (RBFUTUSEA) D ProdPlantYN 1 OverLay(FutureUseA:1) D FutureUseA2 9 OverLay(FutureUseA:*NEXT) We have a future use field in a file that we are going to begin to use. I only need to use one character of it. Anyway, I was under the impression that I can use FutureUseA in the program as it was RBFUTUSEA, so that when an update was executed the RBFUTUSEA field will be changed to what was in FutureUseA. To break up the field, I used the Overlay for ProdPlantYN. When the program executes, ProdPlantYN is populated to 'Y' and while in debug mode, FutureUseA = 'Y ', however, This value doesn't get updated to RBFUTUSEA. Am I suppose to move it there? I thought the purpose of ExtFld was to rename the field for the program? Is there something I'm doing wrong? NOTE: BEF012 is defined in the FSPEC, but there is NOT a prefix on it. Thanks in advance. Michael Schutte -- 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. -- 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.