Service Programs and Naming Conventions

["Marvin Radding" <MRadding@xxxxxxxxxxxx>]

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