|
Donald, We have printers though out the plant. When a tech prints a tag we want it to print at a printer near him. The tech can move around to different areas, but keep the same handheld with him. The tech could even sign off, so I do not want them to have to select the location each time they sign on. I will give them a menu to select their location and then set the printer ID that is closest to them in their data area. It would then update his data area with the printer id. In the print CL, I would read this data area and load the printer id into a declare statement which would set the printer outq in the print override. If he moves, he could select the menu option to set a new printer id. I have used the *LDA in other programs, but never tried to select a data area. This seamed so simple at first. But with little experience in RPGLE I am have some problems. Thanks for all the help you are giving me. Willie 805-489-5144 -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Jonathan Mason Sent: Friday, December 16, 2005 5:34 AM To: 'RPG programming on the AS400 / iSeries' Subject: RE: Help with data area in RPG <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-2024 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.