Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL

Not quite fair Rob...

In both cases, the code that breaks wasn't "correct" in the first
place. In may have worked, but that was basically luck.

When your files are properly tagged with CCSID, CPYxxxIMPF works fine.
When you use the *CL keyword added in v5r1, everything's fine too.

While it may be a pain, David has had plenty of time to stop using the
original work around once IBM provided a correct way to handle the
issue.

All and all, we're taken much better care of by IBM than Windows
programmers are by Microsoft.

Charles

On Thu, Mar 12, 2009 at 3:42 PM, <rob@xxxxxxxxx> wrote:

I feel your pain.  However IBM's done this for many releases - come out
with something that busts code that's been fine for years.  Sort of like
the way they furbared CPY...IMPF in V5R3.  Rather shoots the "same code
been running for years".  Well, I guess that's true if it's a one line RPG
program that only outputs a line that says "hello world".  And then only
if observability, was never removed.  I guess we're to supposed to console
ourselves with the fact that it's better than Window's record.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
David Gibbs <david@xxxxxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
03/12/2009 03:27 PM
Subject:
Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



David Gibbs wrote:

I'm not sure that's correct ... if the RPG procedure has
extproc(*cl:name) defined, I *THINK* that should allow the procedure
to be called from both RPG and CL, but it will use CL return
parameter mechanism.

At this point, my biggest gripe is the fact that I have to rework and
retest code that's worked fine for years.

david

--
IBM i on Power - For when you can't afford to be out of business
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.