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

× 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: Odd CALLPRC behavior when using RPG indicator with RTNVAL
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Wed, 11 Mar 2009 16:42:08 -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>

David Gibbs wrote:

The functionality I'm trying to use works on V5R4 (compiled to V5R2) but doesn't seem to work on V6R1.

I just reconfirmed it.

On V5R4, the returned value is x'F140'.

On V6R1, the returned value is x'00F1'.

There is an PTF that's supposed to fix a problem when returning a single byte value to a CL if the program is optimize *FULL ... but we have that PTF and the program is not optimized *FULL.

david

As an Amazon Associate we earn from qualifying purchases.

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.