× 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.



This is my scenario

Procedure in M1 does EXFMT DSPF1

Function key provokes CALLP to procedure in M2 which does EXFMT DSPF2, which is a subfile in a window, and returns to the procedure in M1.

The window has a border that gets corrupted when DSPF2 is displayed a second time ( after calling the procedure in M2 ). We've got round this problem up to now by putting RSTDSP(*YES) when the DSPF is compiled.

However this seems to be responsable for my problem : the information on the WINDOW has the same name as that on the DSPF record displayed underneath it. When the WINDOW is shown, the record information underneath with the same name changes to match that of the WINDOW.

I can get round the problem with RSTDSP(*NO), then closing and reopening DSPF2 each time the function key is pressed, but that makes the screen flash.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.