RE: Service Programs and Naming Conventions

Yes, the could exist two different programs callig two different
versions of MyProc.  The copy file that provides the PR interface will
dictate which version of MyProc is actually called.

Marvin

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Lim Hock-Chai
Sent: Thursday, September 15, 2005 9:24 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Service Programs and Naming Conventions

Interesting approach.  Probably nothing new in other environment, as
Paul indicated.

What is the benefit of doing below?  
I see a potential problem of two different programs in a system uses two
different version of MyProc.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Marvin Radding
Sent: Thursday, September 15, 2005 10:18 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Service Programs and Naming Conventions


The idea is to be able to have new versions of module in the service
program without disturbing the old ones.

For example:

1st version: MyProc   pr  extproc('MyProc.01.00')
2nd version: MyProc   pr  extproc('MyProc.01.01')
3rd version: MyProc   pr  extproc('MyProc.02.00')

Each version would replace the previous one in the copy file forcing
each new program to all the most recent version transparently.  Any old
programs that are recompiled would default to the newest version.  All
other programs would not need to be changed or updated.

All I am trying to do is provide a single object in a service program
that can be distributed to all systems without having to also update all
the programs. Simplifying modification/enhancement of the service
program and the programs that use it.

Marvin