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



Im having problems with my message subfile, this is the DDS:

A          R SFLMSG                    SFL
A                                      SFLMSGRCD(23)
A            @SFLMSGKEY                SFLMSGKEY
A            @SFLPGMQ                  SFLPGMQ

A          R SFLMSGC                   SFLCTL(SFLMSG)
A                                      SFLSIZ(0002)
A                                      SFLPAG(0002)
A                                      SFLDSP
A  57                                  SFLINZ
A N57                                  SFLCLR
A  58                                  SFLEND
A            @SFLPGMQ                  SFLPGMQ

Im setting @SFLMSGKEY with the ID of the first message that i want to show
in the subfile, *in57 = *on (SFLINZ) and then write the subfile control.
This doesn't seem to work, 'cos im seeing in the subfile some previuos
messages not related with the ones I just sent.
Note that this is a page-at-a-time subfile (SFLSIZ=SFLPAG), one solution
that i've found is to delete my previuos messages from the program queue
with the Receive Message API, but this doesn't work completly becouse i
can't be completely aware of the previuos messages, such as "record locked"
and other internal messages of the running program.

Making SFLSIZ greater that SFLPAG wouldn't fit this scenario, so please,
restraint making that suggestion.

Thanks in advance,

Carlos K.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.