Mapped LDA - ILE common variables

["James W. Kilgore" <qappdsn@xxxxxxx>]

John Carr wrote:

> RE:     Re:Problems with QCMDEXC parameter
>
>
> Hi
>
> <snip>
>
> This is why I really really like the LDA for inter-program communication.
> Put the parm in the LDA
> CHGDTAARA *LDA  'BLAH BLAH SHORT BLAH'
>

We also use a mapped LDA.  It was a design leftover from our S/36 apps and
couldn't find a valid reason for changing it.

It was one of those habits we didn't brag about because we thought we would be
laughed at..like we were from the sticks or something.  The read/write overhead
didn't seem to impact performance, so what the heck...let it ride.

Just curious if any others are using this for interprogram information.  BTW the
users seem to like the computer remembering the last
customer/vendor/employee/item/etc they were working with.

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?  Basically we use that old data dictionary that every file
references to pull them all in.  The CHAIN functions are in service programs and
they pass back the data and a Y/N on successful hit.

Which brings up another point.  We are finding that we are putting a lot of 
stuff
into service programs, basically all the stuff that used to be made into /COPY
subroutines because they were used by more than one progam.  Our thought is that
if code is used in multiple programs it belongs in a service program. Is this
common?  What is your planning for service program useage.



+---
| 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
+---