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



ReadC will read the next changed subfile record in the subfile (as indicated
by Modified Data Tags).  I don't usually like to use this opcode, since ANY
other I/O operation to the subfile will screw up the MDT's and ReadC won't
work "as expected".  Most changes (IMO) shouldn't be done on the subfile
anyway, since you normally need an exclusive lock on the record you're
changing.

IE., if you change some records (which you expect ReadC to pick up), then
hit a cmdkey on the screen, all bets are off on the MDT's staying put.

Most of the subfile programs I write have stuff like: F1-Help, F4-Prompt,
F5-Edit, etc.  I/O to the subfile will often screw up the MDT's and the next
ReadC will not pick up all the records you'd have expected it to.  And then
there's maintenance, often by another programmer, who may change something
which makes your old ReadC logic not work anymore.

This is just based on my experiences and may/may not be accurate in your
situation.

You wrote:
Dear Guys,=0D
         What's the difference between CHAIN and READC for controlling subf=
ile record? As I usually use ReadC to read the next change subfile record n=
umber, But I found some guys use 'Chain' to read the subfile record. any re=
ponsonse?

AS/Resources, Inc.
William A.(Tony) Corbett
IBM Certified Specialist - AS/400 Developer
http://www.asresources.com
corbett@asresources.com
770-587-4812 (no answer forwards to mobile)
fax:  404-663-4737




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.