Hi David
I had a contract at a major pharmaceutical organisation where they used data
structures as parameters for 99.99% of all their program and module calls.
Each program and module had a controlling data structure passed as the first
parameter with further data structures passed as necessary.
All of the data structures were defined as external data structures for the
sake of consistency and to avoid lengthy subfield names the PREFIX(xxx)
keyword was used instead of QUALIFIED. For example:
D* Entry parameters...
D Parm01A E Ds ExtName(SYS6001) PREFIX(p1)
D Parm01B E Ds ExtName(SAL1001) PREFIX(p1)
Regards
Jonathan
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [
mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of David Foxwell
Sent: 18 June 2007 09:59
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
midrange.com
