RE: RPG400-L Digest, Vol 11, Issue 449

Jon

Perhaps a little more info may help. After reading the threads, the problems
needs clarification. I understand the issue with the LDA.

Of the approximately 120 programs, how many will need change? Some or all?

Darryl Freinkel | Assignment 400 Group, Inc.
Tel: 770.321.8562 ext 111 | Fax 770.321.8562


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.

2) Multiple users can be connected at any time via 5250.

3) A single user can be connected at any time via a web interface. (The
single user restriction was enforced earlier when it was believed that the
LDA problem only affected the GUI interface.)

4) Both interfaces may submit batch jobs.

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.


Jon Paris
*************************************