Re: Error Indicator on Write

Hello David,

No one on this list need apologise to me for criticism.  As those who've been 
hanging around here for a while 
can atest I hit pretty hard and I don't mind being hit in return!  Besides, 
constructive criticism is a very 
useful thing.  Even I learn things from the discussions on this list.  I also 
have a very thick skin and am 
not easily offended (and I don't expect apologies for that either.  If I am 
offended by something someone else 
says that is my problem not theirs.)

I am in complete agreement with your first paragraph although I do expect 
programmers to think about the 
op-code choices they make while writing code, which was the message I was 
attempting to get across.  That is a 
topic worthy of discussion in itself.

I'd be interested in knowing the results of your explorations with the C 
routines.

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.                      «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
//--- forwarded letter -------------------------------------------------------
> X-Mailer: Novell GroupWise 5.5
> MIME-Version: 1.0
> Date: Tue, 16 Mar 99 09:35:28 -0700
> From: "David Morris" <dmorris@plumcreek.com>
> To: MIDRANGE-L@midrange.com
> Reply-To: MIDRANGE-L@midrange.com
> Subject: Re: Error Indicator on Write

> 
> Simon,
> 
> Please don't take my comments as any kind of criticism, that would be like 
>biting the hand that feeds 
> you.  I saw the SETLL/READ sans (E) and was trying to rib you because of the 
>"definitive" statement.  
> I used to worry about whether one opcode was faster than another and have 
>come to believe that it 
> doesn't matter much, because I/O almost always sets the pace.  About the only 
>optimization that seems 
> to help is to avoid moving or comparing large amounts of data.
> 
> The I/O routines I wrote sit between an application and database server.  
>These routines support things 
> like GetRcd *NEXT, *FIRST, *EQUAL... you get the idea.  I have found this 
>extra layer adds a negligible 
> amount of overhead, which is offset somewhat by the ability to really 
>optimize I/O. Yes, I replaced the 
> routine that used to trigger a READE which was a *NEXT w/key with a READ and 
>key comparison.  I 
> am now exploring using the C library I/O routines and dumping the generated 
>RPG I/O modules.
> 
> David Morris

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