RE: CHAIN + DS as result field

Brian,

I'm not following. I'm trying to think about what kind of changes could
happen and how it would impact the program.

The only thing I can think of is if someone rearranges a file's key - if
you use %kds, you're ok, if not, you need to change all your keyed I/O.
However, I've been in four shops now and so far so good - no one
rearranges file keys.

Other than that, I can't think of a situation where a change to the file
key would result in a change to a non-%kds key method vs. a %kds key
method. If it's an added field that you need to key by, if you're using
%kds you'll still have to load the field.

I'm also not quite sure what change would happen that you'd have to
modify the D-spec for the %kds data structure.

-Kurt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian Parkins
Sent: Wednesday, February 18, 2009 4:36 AM
To: RPG programming on the IBM i / System i
Subject: RE: CHAIN + DS as result field

For the record I also see no value in using %kds.

Just a thought. What if the key were to change at some point in the
future? Only one change to make, (on the D-spaces, where everything
else
is defined) vs. many in-line changes on the C-specs.

If the following were also used:

D KeyDS E Ds ExtName(FileX:*Key)

Chain %KDs(KeyDs) FileX;

Then code changes might be avoided altogether - just a recompile
required.

Brian Parkins





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number

741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU