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



David,

Hopefully I've understood your predicament...

Move the AID-byte value from the INFDS to a work field immediately after
most EXFMT's or READ's from your display file (you choose which ones).
Then do your AID-byte comparisons against the work field (NOT the INFDS
field).  If you wish to force a value into the AID-byte, move the new
valued into the work field (NOT the INFDS field).

Regards,
Jerry 

jerry.jewel@nissan-usa.com
Better living through fine code and hot coffee!

> ----------
> From:         David Prowak[SMTP:prowakd@emi.com]
> 
> I have a data structure that I use to map the pertinent fields from
> the
> INFDS
> when I use a WORKSTATION file.  I have the AID byte defined as KEY.
> I also have the hex values of the function keys defined so that I can
> write
>       DOU     KEY = EXIT
> or            
>       IF      KEY = PAGEDOWN
> etc...
        ........It seems like the AID byte in the file's buffer (or
wherever INFDS is maintained), keeps its last value.  How can I get
around this......

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

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.