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


  • Subject: Re: RPG/400 pgm strange behaviour
  • From: Mark Holliday <mholliday@xxxxxxxxxxx>
  • Date: Thu, 13 Jul 2000 06:21:41 -0500

> Is there any restriction about entry parms length ?

Although this doesn't appear to be the cause of your problem, Silvio, it
might be worth noting that CL will only allocate enough memory for a 32A
field IF positions 33 and up are unused.  

For example, passing a 100A field from a CL pgm containing 'Jon Paris' will
have this value
but also garbage from positions 33 to 100 (whatever happens to be residing
in memory).  What
we'd do in this case is just move it to a 101A field with a value placed in
position 101.
That way enough memory is allocated and you just work with the first 100A in
the receiving pgm.  Please note that we do this with the %substr bif in
RPGIV, though.  At least this 
might rule-out something for you....

BTW  by referencing Jon Paris with 'garbage' I in no way meant any
disrespect, as he is a true gentleman and a founding father of RPGIV (and
who knows what else!) <g>. 

Mark




+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.