Re: Error Indicator on Write

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

Mello David,

I agree with you.  Using SETLL and READ(E) in place of CHAIN is just dumb -- 
although common enough.  Proper 
use of blocking is generally the best single performance improvement that can 
be made to an application.  It 
does rely on sequential processing and may need a sort of some sort.

My original comments were specifically regarding the proper way to handle 
WRITEs and whether duplicate record 
checking should be performed before the WRITE.

Regarding your I/O routines:  Are you replacing an incoming request for 
read-equal-key with your own 
sequential table scan and a large blocking factor?

Regards,
Simon Coulter.

«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software         AS/400 Technical Specialists       «»
«» Eclipse the competition - run your business on an IBM AS/400.  «»
«»                                                                «»
«» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
«» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
«»                                                                «»
«» Windoze should not be open at Warp speed.                      «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
+---
| 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
+---