I'm still at a loss as to why you can't use your own LDA or job named
specific LDA...create on in QTEMP for the submitting job, assign it to a
perm/temp LDA on the disk, submit job, retrieve it from disk, and delete
when you're done...
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Jon Paris
Sent: Monday, July 30, 2012 12:46 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Seeking inspiration ...
On 2012-07-30, at 11:47 AM, rpg400-l-request@xxxxxxxxxxxx wrote:
Someone remind me what's so hateable about the *LDA, especially as in
this case, if it were possible, it would be perfect!
With pleasure - the problem is that it lends itself to the exact
circumstances I am being forced to deal with - in-house and multiple 3rd
party packages all blithely assuming they "own" it and can do whatever they
want. In one case the product is set to require a specific program be run
during sign on. That product stores information in the LDA. But it allows
the command line to be used to access other applications - since they also
assume they "own" it the data gets corrupted and ... Neither of the 3rd
party apps knows of the others existence and ...
It would be perfect - if it wasn't causing the trouble in the first place
<grin>
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
midrange.com
