Re: Passing data structure to batch job

That wasn't the scenario I had Jerry. In my case the LDA was being used to contain variables that customized the software for the user. It was set when they signed in and used throughout the application. Trouble was nothing stopped you from calling other apps from the command line within the primary app. The called app looked to the LDA to see if it had already been initialized for its use. Found a flag that indicated the data had been populated and then blew sky high because the data in the LDA wasn't what it expected because it was actually residual from the first app.


On 2012-05-24, at 3:19 PM, rpg400-l-request@xxxxxxxxxxxx wrote:

I've seen these problems, too, Jon. Always when the programmer hard-coded
the definition of the LDA in the program. That is, the LDA was "flexible"
for each procedure.

On the other hand, I have never had an issue with using the LDA because the
definition is defined in a copy book so it is always the same regardless of
which program is using it.

That said, I use it only for passing things like report selections from one
program to another, not data.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com