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



On 10/19/05, vhamberg@xxxxxxxxxxx <vhamberg@xxxxxxxxxxx> wrote:
> I'm not sure this is what Steve means, but if you use a PLIST in RPG, there 
> is no data type checking. We know that. But if you prototype your RPGLE, then 
> data types ARE checked at the linking stage. As Elvis said, get into ILE, 
> make modules, prototype stuff in RPG, and you have mapping. In addition, as I 
> said, there are these operational descriptor thingies that are usable if you 
> choose to do so - one would have to do a search on that term to see how - 
> I've not done so yet.
>

Vern,

you are right about the opdesc. I was reading the F1 documentation of
the CALLPRC command today and it has specific statements as to what to
watch out for when calling a procedure using CALLPRC.  The variable is
passed as is, unmapped.  The programmer is supposed to use OPDESC to
know the actual length of the data that was passed.

-Steve

> -------------- Original message --------------
>
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Richter
> > Sent: Wednesday, October 19, 2005 8:25 AM
> > To: Midrange Systems Technical Discussion
> > Subject: Re: iSeries 25% Growth 3rd Quarter
> >
> >
> > of course. are you aware that it does not map the CL variable into
> > the argument of the called procedure? that is a bug waiting to
> > happen. You can make a strong case that CALLPRC should not be used
> > because of this. otherwise, someone in the organization comes along
> > after you, makes an innocent code change to the procedure being called
> > - the result being code that fails the next time the CLLE module is
> > run.
> >
> > -Steve
> >
> > What do you mean, "it does not map the CL variable into the argument or
> > the called procedure."?
> >
> > CALLPRC can pass a parameter by reference or by value....what else is
> > needed?
> >
> >
> >
> >
> > Charles Wilt
> > --
> > iSeries Systems Administrator / Developer
> > Mitsubishi Electric Automotive America
> > ph: 513-573-4343
> > fax: 513-398-1121
> >
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.