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



-----Message d'origine-----
De : rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Scott Klement
Envoyé : mardi 22 décembre 2009 19:11
À : RPG programming on the IBM i / System i
Objet : Re: EXTPROC(*CL) and V6R1

hello David,

The argument is simple. Modify the parameter list on the called
procedure, recompile and no need to touch the callers that
don't use
the parameter.

Given the example that you posted... if a new numeric field
were added, you'd get a decimal data error, because it'd be
initialized to blanks.

I have asked around, and I'm informed that the callers are SUPPOSED to issue a CLEAR InDS, then fill the subfields before calling the procedure. The first line of the called procedure issues a CLEAR OutDS.

Does that not take care of this error? I haven't been using this method as long as the others in the shop, as I resisted for quite a while. I'm unaware that any errors at run time have been produced.

I don't understand why someone with no experience in a new
paradigm for programming would be allowed to set shop
standards and force all of the other programs to use it. Why
wouldn't they get someone with knowledge and experience to
draw up their standards? Or wait until they've had
experience with it?

I get another chance to say what I think of this method soon, as I'm being asked for suggestions for improvement. I'll be taking as many notes as possible from this thread. Thanks again for everyone's input.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.