If you can prove, in procedure 1, that the parameter fields and the screen
fields can be different, then that points to them being independent.
Assuming that this is true, the issue somehow lies in procedure #2. You
did not specify how procedure #2 was designed.
"Robert J.
Mullis"
<robertmullis99@h To
otmail.com> <rpg400-l@xxxxxxxxxxxx>
Sent by: cc
rpg400-l-bounces@
midrange.com Fax to
Subject
09/10/2009 03:16 Problem Clearing Procedure
PM Parameters
Please respond to
RPG programming
on the IBM i /
System i
<rpg400-l@midrang
e.com>
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.
midrange.com
