|
1a. Then when I see module names in upper/lower case that must mean that it was not written in RPG but probably C or C++ 1b. I was planning to use the dots in the name of the module thinking that it would be hidden inside quote marks. 2. Yes I mean service program. I understand the need to not disturb the order as this would force an update of the program, which I am trying to avoid while making improvements/enhancements to the service program. On your last statement, wouldn't adding a parameter even if it was OPTIONS(*NOPASS) change the signature forcing an update of the program? That is what I am trying to avoid. I want to make changes and enhancements without the necessity of updating all program to make sure there won't be any fatal errors when the user goes to use a program. The update could take a long time with over 2,000 programs over 6 systems. Marvin -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Francis Lapeyre Sent: Wednesday, September 14, 2005 8:00 PM To: 'RPG programming on the AS400 / iSeries' Subject: RE: Service Programs and Naming Conventions 1A. OS/400 and the RPG compiler is case-insensitive. Any source you supply is interpreted as upper case by the compiler. You can use mixed case for readability, but remember that Foo is the same as fOO and foO. 1B. You can't use dots in a variable name unless you use the QUALIFIED keyword on a data structure. I'd use an underscore instead. 2. If by "module", you really mean "service program", yes, as long as you add the new versions after everything else in the service program. Never add anything in the middle. Personally, I would modify the existing function within the service program to do things the new way, when it is passed an optional parameter (OPTIONS(*NOPASS)). -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Marvin Radding Sent: Wednesday, September 14, 2005 7:15 PM To: RPG programming on the AS400 / iSeries Subject: Service Programs and Naming Conventions I am designing a service program and considering version, revisions and naming conventions. Here's what I am proposing so far. 1. Every program has a name that consists of upper/lower case letters ending with a release.version numering. a. How do I get the upper/lower case name? The D-Spec always comes out in upper case. b. Can I append a number.number to the end of the name? I tried but the compiler rejects the dots. 2. When an enhancement/improvement is made to a module, the release.version will change and the new module will be added to the service program but the old module will not be replaced. This way no recompilations/modifications will be necessary. Is this idea feasible? Can I added different modules for basically the same program without encountering any problems as long as the external/exported names are different? Any idea if this is possible? Marvin -- 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.