The system is only doing what you told it to.

Post the d-specs that define the varibles being passed, the prototype and the interface for the
procedure, along with the actual call and we'll try to figure out what you did wrong.

Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Chandra Krieg
Sent: Monday, August 04, 2008 12:08 PM
To: 'rpg400-l@xxxxxxxxxxxx'
Subject: Two memory location

I am calling a procedure that passes in 12 parameters. Two of these parms
are populated within the procedure and the new values are passed back to
the calling pgm. These two variables, when testing, are using the same
memory address in the system. As soon as one is assigned a new value they
both are updated with the new value.

I have changed the order of the parameters, re-compiled, logged off and
other various means of trying to resolve the address issue. Can anyone
tell me why the system might be assigning these two variables the same
memory location or a way to avoid this?

Chandra Krieg
i5 Programmer/Analyst
(P) 1.800.348.1831 ext 311
(F) 1.920.568.1403

This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].