×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
We're relooking at the naming conventions we are using for parameters in procedures.
RPG III was simple, with 6 character field names we had two syllables of 3 characters followed by 2 characters and a prefix I or O.
Then, when RPGIV came, we kept the 6 character field names but the prefix A was used for input and output. If the parameter name began with a vowel, the suffix is An. Nobody knows why.
Eg Elephant Name would have been IELPNM. Now it would be AnElpNm.
Furthur imposed, is the use of 2 data structures for the parameters.
So, we now have, for the procedure MonPrcNom (mon procédure nom !)
D MonPrcNom PR N
D AMonPrcNomIn LIKEDS (MonPrcNomInDs) CONST
D AMonPrcNomOut LIKEDS (MonPrcNomOutDs)
In the definition of the DS you find the actual parameter names eg,
D MonPrcNomInDs DS TEMPLATE QUALIFIED
D AnElpNm LIKE(DFN_ELPNM)
Note that the prefix A or An is now in 2 places, because the actual parameter name is AMonPrcNomIn.AnElpNm. Somewhere in there is the elephant's name!
Any thoughts?
Thanks.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
