Re: CHAIN versus SETLL

[CVWD@xxxxxxx]

In a message dated 97-05-22 20:44:05 EDT, you write:

> IMO, in todays world of big iron, the answer is simple - code it the way
>  that will make it the most readable.
>  
>  C    KEY    CHAINFILE            90
>   *
>  C    *IN90  IFEQ *ON
>  .......etc.
>  
>  this makes it pretty obvious that the programmer has a complete key, and
>  wants to know if "a particular" record exists or not.
>  
>  C    PRTKEY  SETLLFILE
>  C    PRTKEY  READEFILE                90
>   *
>  C    *IN90   DOWEQ*OFF
>  C............etc.
>  
>  This makes it obvious that the intent is to read a set of records, not
>  just one.

Good point.  And:
   C    PRTKEY  SETLLFILE                90
    *
   C    *IN90   DOWEQ*OFF
   C............etc.
makes it obvious that the intent is to see if a 'particular' record exists
without locking it or bringing the contents of the input buffer into the
program, wiping out the current values.  Different access methods for
different needs, and one should use the appropriate one, as you said.

Lance
 


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