Re: CHAIN vs. SETLL (was Re: DOW vs DOU)

Kahn, David wrote:
> 
> On Jun 02 1997 mark wrote:
> 
> > Nice theory, but it's incorrect.  RPG II also sets the file cursor for a
> >succcessful CHAIN.
> 
> Mark,
> 
> You are right. I wasn't certain before because I couldn't find any
> confirmation in the System/36-Compatible RPG II manual. However, I just went
> back for a really good look and found:
> 
>      If a READE operation is not successful, you must reposition
>      the file by using either a SETLL or a CHAIN operation.  If the
>      file is not repositioned, all following READ, READE, and READP
>      operations will fail.
> 
> So was Greg Thielen wrong when he wrote the following?
> 
> >>There was also a time (pre-AS/400 and even S/38 I think)
> >>when CHAIN didn't set the file pointer as it does now.  You _had_ to
> >>use SETLL/READ.
> 
> RPG historians?
> 

SETLL always sets the file pointer even in S/34 ! The problem was when
the pointer would be beyond the end of file, in which case SETLL will
fail and the pointer will remain where it was before the SETLL.  Now we
have the hi indicator available to signify this condition.  

Also, From ILE RPG manual 

    SETLL does not cause the system to access a data record.  If you
are only interested in verifying that a key 
    actually exists, SETLL with an equal indicator (positions 75-76) is
a better performing solution than the CHAIN 
    operation in most cases.  Under special cases of a multiple format
logical file with sparse keys, CHAIN can be a 
    faster solution than SETLL.
 


Thank You.

Regards

Dave Mahadevan.. mailto:mahadevan@fuse.net
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *