Re: CPF5123 - 3 key fields not valid.

[rob@xxxxxxxxx]

An issue with DSPJOB OPTION(*FILOVR) perhaps?


Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Rich Dotson" <rich_dotson@xxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
12/16/2004 12:43 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
rpg400-l@xxxxxxxxxxxx
cc

Subject
CPF5123 - 3 key fields not valid.






I am receiving the following CPF message when I am trying to Chain to a 
file:

Message ID . . . . . . :   CPF5123
Message . . . . :   3 key fields not valid.
Cause . . . . . :   The number of key fields specified for member TAP930 
file
  TAP930 in library OSBDATA is greater than 1, which is the maximum number
  allowed.

The file (TAP930) has three key fields defined.  There is only 1 copy of 
this file on the system.   I checked the open files and it had the file in 

the library OSBDATA open.  Here is the DSPFD output:

Number of key fields  . . . . . . . . . . . :              3
Record format . . . . . . . . . . . . . . . :            TA930R
  Key field . . . . . . . . . . . . . . . . :            TFBANK
    Sequence  . . . . . . . . . . . . . . . :            Ascending
    Sign specified  . . . . . . . . . . . . :            SIGNED
    Zone/digit specified  . . . . . . . . . :            *NONE
    Alternative collating sequence  . . . . :            No
  Key field . . . . . . . . . . . . . . . . :            TFREGION
    Sequence  . . . . . . . . . . . . . . . :            Ascending
    Sign specified  . . . . . . . . . . . . :            SIGNED
    Zone/digit specified  . . . . . . . . . :            *NONE
  Key field . . . . . . . . . . . . . . . . :            TFPRODTYP
    Sequence  . . . . . . . . . . . . . . . :            Ascending

Here is the 'F' spec:

FTAP930    IF   E           K Disk

Here is the /Free code where the error is occuring:

Chain (DMBK : CFBRGN : DMType) TAP930;

I checked the fields I am using to chain with (DMBK, CFBRGN and DMType) 
and 
they have the same attributes as the fields in TAP930.    I did an EVAL on 

each of the fields while in debug and they all contained valid data that 
matched a record that exists in TAP930.  There are no overrides in the 
job.

What else would cause the CPF5123 error?

Thanks,
Rich...

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 

http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.