|
<snip> I guess I'm having a difficult time understanding why the data area needs to be created with a different name for each user. If the data area were to be called LOCATION and placed in QTEMP, the problem with the data area name being variable does not exist. </snip> I can see why the data area could need a different name for each user - if it needs to exist after the user signs off, for example. However, if he's having a difficult time reading the data area into his program then I would either use it to populate the LDA as has been suggested or use a system API as has also been suggested. Jonathan
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.