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.