×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Wed, Aug 9, 2017 at 10:49 AM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:
Note, since you mention it, LR doesn't have any effect in a *SRVPGM.
Also, you always have to manually close module level files.
If you define the file in the subprocedure, it would be automatically
opened and closed.
Good information. Now that I think about it, LR makes no sense in a
*SRVPGM.
I hesitate to move the WORKSTN file to each of the procedures because of
all the SFILE keywords for all of the different prompt windows. If time
permits, I may try moving the WORKSTN file to each of the procedures and
defining the SFILE keyword for the only window used by that procedure.
(Not sure if the compiler will require every subfile in the display file to
have an SFILE keyword defined for it, even if the procedure doesn't use a
given subfile.) I burned a lot of time just getting this to work, and the
project is due in a few days.
- Dan
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.
midrange.com
