RE: CHAIN Versus SETLL and READ When Data Needed

This has been an interesting thread. But "Father Time" (me) says lets return
to the basics of basics. Instruction fetching generates overhead and slows
down performance.  The Set.., Read requires two fetches. The Chain one. The
conclusion should be obvious but in RISC machine the Chain operation may
well be implemented by an "under the covers" use of Set.., Read which would
make my conclusion mote. I guess the best way would be to set a timing test
case and run it both ways.

Jack Derham
Direct Systems, Inc.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Jerry Adams
Sent: Thursday, March 01, 2007 12:14 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: CHAIN Versus SETLL and READ When Data Needed

Just by me.  Put your name on the session handout, though, and uploaded 
your addendum for 'em to download.

I should have put your email address on the handout and told them, "If 
you have any questions later, just contact Tommy."


        * Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.995.7024
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Holden Tommy wrote:

LOL did I get slammed?? 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Thursday, March 01, 2007 10:38 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: CHAIN Versus SETLL and READ When Data Needed

Holden Tommy wrote:
  

Guess I should read the whole thread before replying LOL...that's what
    

I
  

get for being away from the list for 2 days... 


Thanks,
Tommy Holden
  
  
    

And we appreciated it, Tommy. .-)  BTW, you should have been at the 
meeting last week; to defend yourself if for no other reason.



      * Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
      615.995.7024
fax
      615.995.1201
email
      jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>