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


  1.  Home
  2. RPG400-L
  3. July 2004

Re: Procedure with varying parm

> Procedure 1 returns a variable length field and
> procedure 2 receives a variable length field.
> Procedure 2 is getting memory garbage in its
> input parm.  Any ideas?

That's the way it works.  P1 initialises 51 bytes of storage and P2 is
reading 1024 bytes of storage (which have only the first 51 bytes set
to a known value.)  The answer is to make P2 only use the number of
bytes that P1 sets.  You can look into %len, operational descriptors,
and passing another parameter indicating the size of P1's variable and
see what works best for your situation.
  --buck

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.