This problem happened a couple of years ago. The code is from FOCUS 7.6.2. I am just coming onto the team to address it. The error message appears right after the DEFINE statement: LINKED FILE DOES NOT HAVE A MATCHING KEY FIELD OR SEGMENT: J1XCHG_KEY. Does anyone have an idea of what may have happened?

JOIN O_EXCH IN REGULTR2 TO XCHG_KEY IN NPANXX AS J1
JOIN T_EXCH IN REGULTR2 TO XCHG_KEY IN NPANXX AS J2
-RUN

DEFINE FILE REGULTR2
CONTIG_KEY/A26 = J1XCHG_KEY | J2XCHG_KEY ;
GET_PERIOD/A4YM= PERIOD ;
CYM/A4 = EDIT('&YMD', '9999$') ;
XCG_KEY/A19 = J1XCHG_KEY | GET_DATE | RES_BUS | CENCELL_IND ;
JURIND/A2 = J1NPA_JDC ;
OSTATE/A2 = J1NPA_JDC ;
TSTATE/A2 = J2NPA_JDC ;
MILEJOIN/A5= JURIND | MILE_BAND | LATA_IND;
TIEXCH/A1 = IF J2ITC_FLAG EQ 'Y' THEN 'I' ELSE ' ' ;
DREVENUE/P12 = REVENUE2 ;
DMINUTES/P12 = MINUTES ;
T_NPA/A3 = EDIT(T_EXCH,'999');
T_NPANXX_A/A6 = EDIT(T_EXCH,'$$$999999');
T_NPANXX_I/I6 = EDIT(T_NPANXX_A);
T_EXCH2/A13 = IF T_NPANXX_I IS-FROM 0 TO 999999
THEN T_NPA | J2XCHG_AREA ELSE T_EXCH ;
J1XCHG_KEY/A13 = J1XCHG_KEY ;
J2XCHG_KEY/A13 = J2XCHG_KEY ;
END

TABLE FILE REGULTR2
SUM FST.CONTIG_KEY
FST.J1XCHG_KEY
FST.J2XCHG_KEY
FST.TIEXCH
FST.XCG_KEY
DMINUTES
DREVENUE
ALINE_CALL
NUM_MSGS
BY O_EXCH
BY T_EXCH2
BY OSTATE
BY TSTATE
BY MILEJOIN
BY JURIND
BY RES_BUS
ON TABLE HOLD
END


On the belief that the REGULTR2 file now had more instances of the cross reference key field than the NPANXX file, I reversed the JOIN syntax and added the ALL keyword, making NPANXX the host file and REGULTR2 the cross reference file. In that case, even though ? JOIN showed the join to be active, the field CONTIG_KEY was not recognized. That stumped me.

Need an index on J1XCHG_KEY ?

Thanks for the input, the XCHG_KEY is indexed in MFD NPANXX.

quote:

NPANXX

Do you have a different master file with the same name located somewhere in your APP path that precedes the one you are intending to use?

This message has been edited. Last edited by: Dan Satchell,

It was mentioned in a post a couple of days ago.

Use the WHENCE command to find you where the master is coming from.

Also, is the file a FOCUS file, SUFFIX=FOC or XFOCUS. Has someone rebuilt the file with out the index ?

The DEFINE FILE REGULTR2 unables the previous JOIN's with the FILE REGULTR2, by this reason all reference to NPANXX's field is an error.

It is the JOIN that will negate the DEFINE virtual fields, not the other way around:

quote:

Note that if you are creating a virtual field in a DEFINE command, you must issue the DEFINE after the JOIN command, but before the TABLE request since a JOIN command clears all fields created by DEFINE commands for the host file and the joined structure. Virtual fields defined in Master Files are not cleared.

Tip: If a DEFINE command precedes the JOIN command, you can set KEEPDEFINES ON to reinstate virtual fields during the parsing of a subsequent JOIN command. For more information, see Preserving Virtual Fields Using KEEPDEFINES.

JOIN O_EXCH IN REGULTR2 TO XCHG_KEY IN NPANXX AS J1
JOIN T_EXCH IN REGULTR2 TO XCHG_KEY IN NPANXX AS J2
-RUN

DEFINE FILE REGULTR2
CONTIG_KEY/A26 = J1XCHG_KEY | J2XCHG_KEY ; 
...

When joining to the same table twice, I always use the TAG clause:

JOIN O_EXCH IN REGULTR2 TO XCHG_KEY IN NPANXX TAG T1 AS J1
JOIN T_EXCH IN REGULTR2 TO XCHG_KEY IN NPANXX TAG T2 AS J2
-RUN

DEFINE FILE REGULTR2
CONTIG_KEY/A26 = T1.XCHG_KEY | T2.XCHG_KEY ; 
...

quote:

J1XCHG_KEY/A13 = J1XCHG_KEY ;
J2XCHG_KEY/A13 = J2XCHG_KEY ;

Could this perhaps be the problem? Try commenting these two lines out and see what happens...

quote:

Originally posted by Dan Satchell:

quote:

NPANXX

Do you have a different master file with the same name located somewhere in your APP path that precedes the one you are intending to use?

No, this is no other MFD with the same name.

quote:

Originally posted by Juan Romero:
The DEFINE FILE REGULTR2 unables the previous JOIN's with the FILE REGULTR2, by this reason all reference to NPANXX's field is an error.

Mr. Mariani is right, it is the other way around. I appreciate the input.

[QUOTE]Originally posted by Francis Mariani:

When joining to the same table twice, I always use the TAG clause:

QUOTE]

In my troubleshooting tests I have added the TAG parameters and and continue to use them because they add more clarity. No effect on the outcome though.

Are you using the tag prefix (T1.) in your join or the join prefix (J1)? You should use the tag prefix.

Try adding

? JOIN

just after the JOIN to view the structure. Try adding

?FF REGULTR2

to view the column names.

quote:

Originally posted by GamP:

quote:

J1XCHG_KEY/A13 = J1XCHG_KEY ;
J2XCHG_KEY/A13 = J2XCHG_KEY ;

Could this perhaps be the problem? Try commenting these two lines out and see what happens...

I thought that was strange too (I didn't write it). Commenting those lines made no difference.

Does XCHG_KEY exist in NPANXX?

Why not just post the two master files being used. That would make life a lot easier for all of us...

I would like to offer my thanks and apologies to everyone who offered an attempt on this one. The apology is for my lack of followup on this board recently. I tried some of the proposed solutions without success, then decided to go in a different direction.

I rewrote the beginning of the FEX to eliminate the simultaneous joins by doing the first join, writing to a hold file & then doing the second join on the result. Basically, I got the result with less complexity.

Thanks to all for your help.