× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. August 2021

RE: DS argument list for i/o vs. listing the arguments at the i/o statement

I prefer the clarity of the individual fields.

That being said, I used %kds() extensively in a program that had about 10 level breaks. It made the code pretty easy to setup and follow.



-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of David Gibbs via RPG400-L
Sent: Wednesday, August 18, 2021 8:52 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Cc: David Gibbs <david@xxxxxxxxxxxx>
Subject: Re: DS argument list for i/o vs. listing the arguments at the i/o statement

On 8/18/21 8:24 AM, Alan Cassidy wrote:
(1) chain %kds( CustkeysDS )  Custfile ;

--versus-

(2) chain ( CustType : CustNbr )  Custfile ;

IMO, it depends on how complex the files key fields are.

If there a lot of keys, a data structure makes sense.

If it's less than 3, individual fields are good.

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.