RE: Service Program Export Order

The binder language EXPORT's are the thing that matters. If you're using
binder language nothing else is important. You may make the order of the
procs in your source anything you want. Just add the new ones to the end of
the EXPORT list and either UPDPGM to the programs that use the *SRVPGM or
make the Signature a fixed value (unless it is currently *GEN) and you
probably won't have an issue.  If you use *GEN, copy the export group within
the same QSRVSRC source member, change the original signature from *GEN to
*PRV, and change the new export group's signature to some fixed/known value.

The existing code will continue to work unmodified, and new code will use
the new export group and hard-coded signature.
-Bob Cozzi

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Chris_Bougher@xxxxxxxxxxxxx
Sent: Friday, May 21, 2004 6:47 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Service Program Export Order

How important is the order of the following in service programs?

Prototype declarations

Procedures

Binder exports

The reason I ask is I have a service program in production and need to add
some procedures to it and I noticed that the prototypes are not in the same
order as the binder exports. The binder exports are in alphabetical order
and the prototypes are in order by what they do. The procedures are in the
same order as the prototypes.


Thanks
Chris Bougher
8


_______________________________________________
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.