AW: Problem Clearing Procedure Parameters

Hi,

there was a problem with constant parameters that get cleared.
Using the opcode CLEAR it was possible while using for example EVAL
Par=*BLANKS or MOVE *Blanks Par never was allowed.
AFAIK there is a PTF that solves the problem.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Robert J. Mullis
Gesendet: Thursday, 10. September 2009 21:46
An: RPG programming on the IBM i / System i
Betreff: Re: Problem Clearing Procedure Parameters

I have checked the compile listing. FIELDA and FIELDB (CONST from Procedure
#1) are only being modified in the one place in the program, which was the
original location that sets the initial value.

--------------------------------------------------
From: "Charles Wilt" <charles.wilt@xxxxxxxxx>
Sent: Thursday, September 10, 2009 3:32 PM
To: "RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Subject: Re: Problem Clearing Procedure Parameters

Robert,

You're missing something somewhere....

As you say, a constant parameter can't be changed (well technically
there are ways to do it, but you have to lie to the compiler which
isn't easy to do. Particularly when dealing with internal procedures)

Check the cross reference on the compile list to see where FIELDA and
FIELDB are defined and modified.

You you still can't find it, you might consider posting the code on
http://code.midrange.com and posting the link to the list so another
set of eyes can look at it.

Charles


On Thu, Sep 10, 2009 at 3:09 PM, Robert J. Mullis
<robertmullis99@xxxxxxxxxxx> wrote:

I have a program that has two internally defined procedures.

Procedure #1 has two fields as input parameters, FIELDA and FIELDB, both
defined as CONST. In Procedure #1, the two input fields are moved into
two fields on a screen called SFIELDA and SFIELDB. If certain conditions
are met, Procedure #1 calls Procedure #2. In Procedure #2, the two screen

fields, SFIELDA and SFIELDB, are cleared. I noticed that the fields
passed into Procedure #1, FIELDA and FIELDB are getting cleared at the
same time. I put the program in debug and verified this.

How is this possible? First of all, I thought if a parameter to a
procedure was defined as CONST, it couldn't be changed. I have searched
through the program to make sure there were no datastructures, etc. that
might be overlaying the fields and the DDS for the screen to make sure
the procedure parameters are not defined on a screen.

Any advice and/or help would be greatly appreciated.

Thanks,

Robert
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.