Re: Guaranteeing re-resolution on CALL statements

James,

Interesting RPG Cafe discussion - http://www-949.ibm.com/software/rational/cafe/thread/1872?tstart=0 and the subsequent link back to Midrange for some more dicsussion on this.

I think you can use rslvsp to force the program to re-resolve the pointer but that's an old cobweb that I can't seem to clear up, so you'd have to try it out...

Perhaps someone can tell me I'm dreaming before you waste too much time with that route...

Crispin.

----- Original Message ----- From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
To: <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, August 12, 2009 2:17 PM
Subject: Guaranteeing re-resolution on CALL statements

I have a situation (in an update utility) in which a statement of the form

C CALL FOO
C PARM BAR
. . .

is called repeatedly for different "elements" of the update. It can,
under certain circumstances, result in FOO itself being replaced,
producing a MCH3402 exception on subsequent iterations.

Anybody know of an easy way to guarantee re-resolution of FOO to the new
version, if it gets updated?

--
JHHL
(wishing I could ANSWER somebody's question for a change!)
--
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.