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


  • Subject: Re: Screen behavior with subfile
  • From: "James W. Kilgore" <eMail@xxxxxxxxxxxxxxxxxxx>
  • Date: Fri, 22 Dec 2000 17:50:41 -0800
  • Organization: Progressive Data Systems, Inc.

William,

I will check those things out.  Thanks.

Typically the headings are line 1 & 2 and the SFLCTL starts out on line
4, but in this case line 3.

RSTDSP(*NO) developed as a shop standard as our typical model for a WRK
command includes calls to separate programs to EDT/ADD.  If you have a
subfile on the screen and change entries, one would want to refresh the
subfile upon completion.  Therefore the system overhead to store/restore
the 'old' information is a waste of resources.

William Corbett wrote:
> 
> That shop standard should be discussed, I'd think. 
<<snip>>
> 
> But, my guess is it's an overlay thing. 
<<snip>>
> Oh, yeah, make sure the records are not overlapping on the attribute byte.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.