Re: Mapped LDA - ILE common variables

[Jon Paris <paris@xxxxxxxxxx>]

>> "Now that we are going to ILE where we can have common/local variables, we
are
thinking of having the users signon to a shell menu program which basically
declares EVERY variable from EVERY application file as common variables.  Any
thoughts on that one?" <<

Seems like overkill to me, not to mention hazardous to your health.  I don't
know the exact "cost" of doing this but there is some performance hit due to
the fact that every program except the EXPORTer is referencing every variable
indirectly.  Comp-Sci purists will also have fits over the fact that any
variable can be changed anywhere _without_ being passed as a parameter etc.
The potential for unwanted side-effects is truly horrible.

I'd go for a scheme where you define in this manner only those fields that you
really need to be "instantly" available throughout the application.  You might
also consider using a User Space and BASED storage to retain the information,
that way it can be persistent between sign-ons and certain areas can be common
to all users if you wish.

The major benefit to either approach is that you get away from the LDA.  My
personal view is that that is simply an accident waiting to happen.  You may
have good standards and control over it now, but the simple step of introducing
a software package, or a piece of shareware could wreck your system in a
hurry.

Jon Paris - AS/400 AD Market Support - paris@ca.ibm.com
Phone: (416) 448-4019   -   Fax: (416) 448-4414
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---