Okay, one more possibility. What are you passing as parms to procedure #1?
The field that you place in the call, is it some stand-alone field that
you've defined in the program, or could it be another display file field?
As someone else stated, CONST passes by reference sometimes, if it can, so
your procedure #2 could be playing with the value, without Procedure #1's,
or the main procedure's knowledge.
darren@xxxxxxxxx
Sent by:
rpg400-l-bounces@ To
midrange.com RPG programming on the IBM i /
System i <rpg400-l@xxxxxxxxxxxx>
cc
09/10/2009 04:14
PM Fax to
Subject
Please respond to Re: Problem Clearing Procedure
RPG programming Parameters
on the IBM i /
System i
<rpg400-l@midrang
e.com>
There are no parameters for Procedure #2. Procedure #2 gets called when
certain conditions are met. It only initializes some screen fields and
indicators.
It sounds like memory corruption to me. You're not using a level check *no
on the display file right? You're not placing the names of the actual
screen fields in a datastructure in your program? I'm not talking about
overlaying, just listing the field names in a datastructure.
--
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
