Re: LDA with various pgms

Any program that changes an lda value, and within that pgm makes a call to
another pgm,
and that called pgm uses that lda value - then the 1st pgm must do an OUT
before the call.

If that "called" pgm changes the lda, then ends, returning to the 1st pgm,
and the 1st pgm is
going to check the lda for a new value, the 1st pgm must do an IN after the
call.

Think of the lda like a single record file - you have to "update" a record
before another pgm could see the changes. And if you have already chained to
a record, then called to another pgm that also
updated that record - when returning to 1st pgm you would have to re-read
the record to see the change. (i hope this is clear..)
jim
----- Original Message ----- 
From: "Marla Snow" <MSnow@xxxxxxxxxxxxxxxxxx>
To: <rpg400-l@xxxxxxxxxxxx>
Sent: Thursday, June 30, 2005 10:41 AM
Subject: RE: LDA with various pgms


Hi Steve,
I don't do an OUT *LDA, the program just updates the fields in the LDA and
then the program ends.
I just spoke with the person who will be using this new function and because
I can't build the "F12" in there with the F3 he said to forget about it.  He
doesn't want to F3 through all those screens if he really does want to
exit - he said I would rather not have one function that is different than
the rest.
Oh well... I am putting the code back the way it was.  If there is a simple
answer, though, I would like to know for any time in the future that I might
need to do something like this.
Thanks!
Marla
____________________________________________________________________________
_____________
Hi Marla, You are updating the field in the LDA in your program then doing
an OUT *LDA before you come out of the program?

<snip>