Re: Maintaining Service Program signatures

I have a lot of versions and deliver program to lot of environments I don't.

For each service program I have 4 sourcemodule:

PXAPICGI RPGLE powerEXT: API Basic HTTP Connector & Prod Services
PXAPICGIB BND powerEXT: General Service Program Binding
PXAPICGICN TXT powerEXT: Service Program Connector or copybook if
you like
PXAPICGIZ CLLE powerEXT: Create Service Program

The RPGLE source is the actual serviceprogram and I compile it as a
*module. New
subprocedures are inserted where the logically fits in.


The BND source has a

STRPGMEXP PGMLVL(*CURRENT)
EXPORT SYMBOL(clearSrvPgm)
....

where new subprocedures are added in the buttom. If I need to put new PARM
to
an existing subprocedure I do it as the last field in the subprocedure and
the new
PARM has always options(*nopass) otherwise the old subprocedure is kept as a
depreciated subprocedure.

and a

STRPGMEXP PGMLVL(*PRV)
EXPORT SYMBOL(clearSrvPgm)

section for each previously version


In the TXT source I have a connector/copybook that is a copy of the
procedure
definition section in the service program. This will also be in a logically
order.


In the CL source I have a program that creates the service program and
removes
the module.


All service programs are placed in a generic binding directory that is
referred
to in all programs.

You may wonder why the source modules has different names, but I keep all
my
source in one QSRC source file because it saves me a lot of time changing
back
and fourth between source files





On Wed, Feb 20, 2013 at 6:46 PM, Rory Hewitt <rory.hewitt@xxxxxxxxx> wrote:

Yeah, the "orders them alphabetically" thing can be a problem...


On Wed, Feb 20, 2013 at 9:42 AM, Mark S Waterbury <
mark.s.waterbury@xxxxxxxxxxxxx> wrote:

Hi,

You can also retrieve (generate) "binder source" from the *MODULE or
*SRVPGM using the RTVBNDSRC command.

There was a good thread about this here:

http://archive.midrange.com/rpg400-l/200408/msg00646.html

Read the entire thread, especially comments by Simon Coulter:

http://archive.midrange.com/rpg400-l/200408/msg00652.html

All the best,

Mark S. Waterbury

> On 2/20/2013 10:50 AM, RPGLIST wrote:

I would also assume that binder file as well as the prototype copybook
must be promoted to a production box along with the service program,

but

the module would not since its incorporated into the service program,
unless of course the objects are recompiled when promoting which isn't

the

case with all systems.

--
This is the RPG programming on the IBM i (AS/400 and 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.

--
Rory Hewitt

http://www.linkedin.com/in/roryhewitt
--
This is the RPG programming on the IBM i (AS/400 and 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.