× 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.



The second level text on compiler message RNF7705 says:

Cause . . . . . :   The second parameter for %KDS must be a numeric value with
  zero decimal positions known at compile-time. In addition, the value must
  not be greater than the number of subfields in the data structure specified
  as the first parameter for %KDS. The operation is ignored.
Recovery  . . . :   Omit the second parameter for %KDS, or specify a valid
  numeric value that is known at compile-time. Compile again.

The key words are "numeric value with zero decimal positions known at compiled time." I think this means a literal or named constant with no decimal positions, not a variable.

I agree that the manual should be more specific about what is expected in %KDS 
factor 2.

Mel Rothman


Andy Hautamaki wrote:
I'm trying to do a chain using a %kds qualifying the key fields to use with a numeric variable but am getting compile errors.

D g_keyfields     s              1  0

g_KeyFields = 2;

chain %kds(ky_fb : g_KeyFields) fhrec;

The compile errors on the chain I'm getting are;

RNF7071 30 1 Number of KFLDs in KLIST is greater than number of key field in file
RNF7705 30      2 The second parameter for %KDS is not valid.

I'm not seeing anything in the manual that would say I can't use a variable for the number of keys to use for %KDS. Or is this one of these things that you just can't use a variable for. I'm at V5R3.

Thanks;

Andy



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.