Re: LDA Usage in Homegrown Apps and System21

Roshan,

You could create a generic CLP program to run all your
home grown programs.  Have the CLP save the LDA into
a Variable before calling the program, then restore the
LDA from the variable before exiting the program and
returning to the JBA environment.

--Jack
_________________________________________________


> Hi List,
>
> We've just bought System21 for it's Workflow functionality. With this, we
> also bought the System Manager suite of programs. We are hoping to migrate
> our home grown applications to Application Manager menus and tasks.
>
> However one our biggest problems in doing this is that our applications use
> the LDA extensively, and I know for a fact that we can't simply use our
> programs within System21 as the LDA would get corrupted.
>
> At present, the only option we see is changes in all our existing programs
> if we are use the System21 menus... We've got the following suggestions so
> far, but would like to hear from others out there who have been through a
> similar experience.
> 1. Move the usage of LDA to start from position 257 onwards.
> 2. Store the session values in a file - simulate the LDA, but using a file,
> not the LDA.
> 3. Parameterise the programs and not use the LDA at all.
>
> Has anyone been through a similar situation before and if so, what options
> did you'll have and what was the solution taken? In my previous life with
> with JBA & Geac, I've never come across any site that had an issue like
> this...
>
>
> Thanks in advance,
>
>
> Roshan Joseph
>
> Patrick Autocare,
> Melbourne,
> Australia
>
>
> _______________________________________________
> This is the System 21 Users (SYSTEM21) mailing list
> To post a message email: SYSTEM21@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/system21
> or email: SYSTEM21-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/system21.
>
>