Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL
From: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
Date: Fri, 13 Mar 2009 11:31:21 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hi Barbara,

There was no way to fix it without breaking existing applications. If either RPG+COBOL or CL had changed how they handle 1 byte character/indicator return values, it would have required a recompile of all existing programs.

That's my point. Err, maybe I didn't say it clearly.

Changing the system to use a register, and breaking the *CHAR 2 workaround for the problem WILL BREAK EXISTING APPLICATIONS. Now you have change the code to use EXTPROC(*CL) and recompile everything.

If you're going to force us to recompile everything -- why not fix the underlying problem, since we have to recompile everything, ANYWAY...

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 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.