• Subject: Re: new display file features; was "4 - subfiles"
  • From: "Dan Bale" <dbale@xxxxxxxxxxx>
  • Date: Wed, 10 Nov 1999 16:57:29 -0500



Booth,

Comments inline:

> On the other hand, filling a field automagically is becoming
> another solution.   Is it easier for us to implement
> "automagic fill" from cursor-top or from a reload of the page?

I presume that what you mean by this is something that many Windoze apps
utilize:  As a user types the search word, character by character, the
application zeros in on the record in the "subfile" while each character is
typed.  This would be the holy grail of AS/400 display file techniques (hokay,
maybe not!) but requires the 5250 protocol to handle character-at-a-time I/O
which, from my understanding, is not currently possible.

> So far as files changing,  I was hoping for discussion in
> this area.  A 2,500 subfile reloads in 4 or 5 seconds.  If
> there was a way to easily tell if a file had changed then we
> could reload the subfile fairly easily.

Have you tried the Retrieve Member Description (QUSRMBRD) API?  The MBRD0200
format has the "Change date and time" of the file you're looking up.  I believe
this value is the timestamp associated with any record change, add, or delete
transaction on the file (member).  If it's fast enough, you might check it every
time control returns to the program from the display file.

- Dan Bale





+---
| 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
+---

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-2019 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].