|
You are right, as far as you go. I'd done that. Where the issue existed for me is this: On a full screen if the user has generated 5 error messages s/he can put the cursor on the message on line 24 and page through all 5 messages. (You'd notice the "+" sign on the bottom right of the screen.) The same scenario, but done on a window, displays only the first error message. --------------------------------- Booth Martin http://www.martinvt.com --------------------------------- -------Original Message------- From: Midrange Systems Technical Discussion Date: 03/31/05 11:11:39 To: Midrange Systems Technical Discussion Subject: RE: ERRSFL keyword, and WINDOW Booth, Have you tried leaving two lines at the bottom of the window for messages? Try the following. 1. As you normally would add the ERRSFL keyword at the file level. 2. Make your window 1 line larger than it is now and make your subfile message line the equivalent of line 23 for a full display. So for a window with 11 lines you make line 10 the SFLMSGRCD line. This does assume the message subfile's size is 2 and the message subfile's page is 1. My experience has been that messages you send to the program message queue show up in the SFLMSGRCD line and job messages show up in the last line (equivalent of line 24 on a full display). Gary Monnier -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin Sent: Wednesday, March 30, 2005 10:00 AM To: Midrange Systems Technical Discussion Subject: ERRSFL keyword, and WINDOW ERRSFL keyword, and WINDOW What am I misunderstanding? I used ERRSFL for error messages on full screens, and the error(s) are accumulated and I can roll through them on the bottom of the screen. Identical code, but in a window, shows only the first error message. I've looked carefully for a typo, and am beginning to wonder if ERRSFL works differently in a window than on a screen? --------------------------------- Booth Martin http://www.martinvt.com --------------------------------- -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. .
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.