× 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: STRDBG giving wrong data
  • From: boldt@xxxxxxxxxx
  • Date: Mon, 14 Feb 2000 09:35:15 -0500



Dean wrote:
>Perhaps Hans can expound on the underlying technical reasons for this
>long-time and _ABSOLUTELY RIDICULOUS_ behavior of long RPG parameters
passed
>from CL (an explanation of 15 and 5 numerics would be nice, as well).
It's
>been going on since the advent of the AS/400, and the only way to fix it
is
>to check the last position of the first parameter in the CL program prior
to
>building the second, and inserting an "X" or some such in that position if
it
>is blank...

Hey, ask me an easy question, like "What are next Wednesdays
lottery numbers?"

I believe the CL parameter passing protocols go back to the
S/38.  RPG III in those ancient days supported only 15 digit
numerics, which partially explains things.

Perhaps the reason for the behavior was to encourage
programmers to implement command interfaces for all
user-callable programs.

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com


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