|
On 2012/10/18 2:28 PM, Gqcy wrote:
...
some of us are remembering problems with not setting ALL KEY VALUES,
because you may have problems with the remaining key fields not being
set to *LOVAL...
However, I seem to think that was only when you were using a KLIST or
something like that...
I think it's not about whether you're using a KLIST, it's about whether
you're using an externally described file.
With an externally described file, you can use a subset of the keys, and
the other keys will not be considered. There's lots of ways to use a
subset of the keys. A KLIST with only some keys, %KDS, a list of keys in
free-form, or a single key as you've coded.
With a program described file, they didn't have the option of using a
subset of the keys, so they had to put meaningful values for all the
keys. I assume they would have defined the key as alpha, and used a data
structure for the key values, setting the unwanted keys to loval or
hival depending on the operation.
As an Amazon Associate we earn from qualifying purchases.
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.