|
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Foxwell
Sent: Monday, June 18, 2007 4:59 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Adding parameters to procedures
Hi,
We are looking at the possibility of standardizing our
procedures in the manner described at the link below.
The aim is to avoid touching any procedures that don't use a
parameter that has been added to an exported procedure. We
just recompile everything.
Each procedure uses a DS for entry and another for output
parameters. If a new parameter has to be added it is just
added to the DS in question.
I have a problem with this : it gives rise to horribly long
parameter names ( I've simplified in the example) and
debugging is annoying.
But my biggest concern is what else are we missing? Someone
out there MUST have already tried this system.
Any comments would be greatly appreciated.
http://code.midrange.com/index.php?id=703f46126a
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.