×
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.
I think Scott is right with his assumption.. I documentation for V4 indicates the %scan bif returns an unsigned integer value, and intermediate precision rules might be getting fouled up by the unsigned value.... Can you try the EXPROPTS(*RESDECPOS) control keyword (H spec)? Perhaps you could wrap the %scan() bif in a %int() to cast it to signed integer...
Eric
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of James Lampert
Sent: Monday, February 11, 2008 12:57 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Why would this statement fail?
vhamberg@xxxxxxxxxxx wrote:
In debug, do a hex display of "path" and see what
the first 2 bytes have in them - how is that variable populated?
It can make a difference with VARYING.
Well, I've definitely determined that it was the combination of the
%SCAN() call and the "-1" in the same EVAL statement, not something in
the %SCAN. Probably the compiler generating something funky. Works fine
if the two are separated.
midrange.com
