Re: Seeking inspiration ...

Jon:

Actually it is beginning to look as if the environment variable is the only

option that will work - the problem I face with it is the sheer number of
programs to modify/test.

The user index DQ suggestions cause different problems.

Let me qualify the requirements a bit further. Amazing how you don't
realize how many criteria are in play until you try to explain your
problems!

1) "My" software currently uses the LDA.

5) Those batch jobs require the data that is currently stored in the LDA

6) Only one program uses/changes the LDA - but happens on a simple
call/return. In other words storing the LDA and trying to restore it is not
really an option since I would only know when to store it - I have no way
of knowing when the content needs to be restored.

7) I am trying to minimize the number of programs needing changes/testing.
The SBMJOB environment variable solution, for example, would require over
120 programs to be modified/tested. Changing the parameter list to the
program that changes the LDA would mean 140 programs. etc. etc. Yes - I
know the app should never have been built this way - sadly I had no control
over that.

Don't see how you can avoid changing programs that use a variable populated
from the LDA. If the LDA is contaminated, you've got to find another
mechanism to populate those variables anyway. So you need a mechanism that
will store "your" current variables, and retrieve exactly that set of
values back into "your" programs at program initialization for the
submitted job independent of the LDA.

Sticking point for me seems to how to associate the saved values with the
submitted job- while system copies the current LDA automatically, you're
going to have to work a bit. Environment variables seem to the most direct
solution- at least the system is doing the copying automatically if
properly configured.

Keyed data queue would be my second choice. I'd build a procedure to
generate a unique 10 character job name for each submitted job, one to save
the current values to the data queue using the job name as the key, and and
one to retrieve the values from the DQ using the job name.