1,565 pts.
 result of CHAIN with a bad key
Rather than proving it out myself, it's so much easier to ask if anyone has run into this before. While researching a bug, I found a program that chains to a file using a 3-field key list. BUT - the 2nd and 3rd fields are "wrong" (defined as alpha in the key list but numeric in the file). Seems like the result is as tho CHAIN was done using only the 1st field. Is that what actually happens ? Just because I want it to be true doesn't mean it is.

Software/Hardware used:
as400
ASKED: October 19, 2012  7:08 PM
  Help
 Approved Answer - Chosen by aceofdelts (Question Asker)

It would seem top me that you would get a compile error because the key fields do not match.

ANSWERED:  Oct 19, 2012  7:21 PM (GMT)  by aceofdelts

 
Other Answers:
Last Wiki Answer Submitted:  October 19, 2012  7:08 pm  by  aceofdelts   1,565 pts.
Latest Answer Wiki Contributors:  aceofdelts   1,565 pts.
To see other answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

good thought – so I compiled the source to a test library and it does compile OK

 1,565 pts.

 

Numeric — as in signed???
Cause then they are the same number of bytes.
It will use all three.
Remember a positive signed number is the same in signed and alpha. 

 44,160 pts.

 

Drat – A more precise test does NOT compile. Thanks for the replies.

 1,565 pts.

 

We would need to see the program data definitions, the program CHAIN statement and the file key definitions (of the one that compiled). A specific combination must be involved somewhere. I take it that you’re otherwise satisfied all is well? — Tom

 108,055 pts.