Hi,

We recently did a fresh install for Webfocus 8105 version and we copied over the reports and application under ibi/apps.

We are having problems with two programs. The following programs run fine in old Dev.

1. In new Dev, we get an error for the highlighted field (J1.SEG01.TITLEX):

JOIN

LEFT_OUTER EXTR_EMPL_BONUS.TITLE_CD IN EXTR_EMPL_BONUS

TO UNIQUE XREFTITLE.SEG01.TITLE_CD IN XREFTITLE TAG J1 AS J1

END

DEFINE FILE EXTR_EMPL_BONUS

TITLEX/A70=EXTR_EMPL_BONUS.EXTR_EMPL_BONUS_VIEW.TITLE_CD || ' - ' || J1.SEG01.TITL_LONG_DD;

END
APP HOLD ceo1

TABLE FILE EXTR_EMPL_BONUS

PRINT

J1.SEG01.TITL_SHORT_DD

J1.SEG01.TITLEX

WHERE RECORDLIMIT EQ 10

END

Here’s the error:

0 ERROR AT OR NEAR LINE 13 IN PROCEDURE ADHOCRQ FOCEXEC *

(FOC003) THE FIELDNAME IS NOT RECOGNIZED: J1.SEG01.TITLEX

BYPASSING TO END OF COMMAND

(FOC009) INCOMPLETE REQUEST STATEMENT

The program runs in old Dev, and also runs in new Dev if we remove the qualifier (i.e. TITLEX).

2. For the second program when we run it pops out "Error Parsing MASTER FILE XXXXXXXXXX (IBFS1206)"
which we have no problem to run in the old Dev.

thank you so much for reading my post and I really appreciate of your help

This message has been edited. Last edited by: <Emily McAllister>,

Before the TABLE FILE, add this and see what you find out:

CHECK FILE EXTR_EMPL_BONUS
CHECK FILE XREFTITLE 
? JOIN
? DEFINE

Dear BabakNYC,

You meant something like below. thanks.

JOIN

LEFT_OUTER EXTR_EMPL_BONUS.TITLE_CD IN EXTR_EMPL_BONUS

TO UNIQUE XREFTITLE.SEG01.TITLE_CD IN XREFTITLE TAG J1 AS J1

END

DEFINE FILE EXTR_EMPL_BONUS

TITLEX/A70=EXTR_EMPL_BONUS.EXTR_EMPL_BONUS_VIEW.TITLE_CD || ' - ' || J1.SEG01.TITL_LONG_DD;

END
APP HOLD ceo1

CHECK FILE EXTR_EMPL_BONUS
CHECK FILE XREFTITLE

TABLE FILE EXTR_EMPL_BONUS

PRINT

J1.SEG01.TITL_SHORT_DD

J1.SEG01.TITLEX

WHERE RECORDLIMIT EQ 10

END

Yes, and add:
? JOIN
? DEFINE
-EXIT

Then show us the output of the above queries.

it returned the message below. what should I do now? thank you

0 NUMBER OF ERRORS= 0
NUMBER OF SEGMENTS= 5 ( REAL= 1 VIRTUAL= 4 )
NUMBER OF FIELDS= 95 INDEXES= 0 FILES= 5
NUMBER OF DEFINES= 1
TOTAL LENGTH OF ALL FIELDS= 2777
0 NUMBER OF ERRORS= 0
NUMBER OF SEGMENTS= 1 ( REAL= 1 VIRTUAL= 0 )
NUMBER OF FIELDS= 13 INDEXES= 1 FILES= 1
TOTAL LENGTH OF ALL FIELDS= 203
JOINS CURRENTLY ACTIVE
HOST CROSSREFERENCE
FIELD FILE TAG FIELD FILE TAG AS ALL WH
----- ---- --- ----- ---- --- -- --- --
EXTR_EMPL_B> EXTR_EMP XREFTITLE.S> XREFTITL J1 J1 N N
EXTR_EMPL_B> EXTR_EMP R_DEPT.R_DE> R_DEPT J2 J2 N N
EXTR_EMPL_B> EXTR_EMP XREFEVNTTYP> XREFEVNT J3 J3 N N
EXTR_EMPL_B> EXTR_EMP XREFEVNTCAT> XREFEVNT J4 J4 N N
0FILE NAME FIELD NAME FORMAT SEGMENT TYPE
EXTR_EMPL_BONUS DEPTPLUSDESC A202 3 MASTER
EXTR_EMPL_BONUS DEPTX A70 3
EXTR_EMPL_BONUS TITLEX A70 2
EXTR_EMPL_BONUS EVENTX A70 4
EXTR_EMPL_BONUS EVENTCATX A70 5
EXTR_EMPL_BONUS PERM A15 1
0 ERROR AT OR NEAR LINE 69 IN PROCEDURE etl_ceobonusx
(FOC003) THE FIELDNAME IS NOT RECOGNIZED: J1.SEG01.TITLEX
BYPASSING TO END OF COMMAND
(FOC009) INCOMPLETE REQUEST STATEMENT

It looks like there's a problem with your DEFINE because WF can see both tables and the join is there. Take a look at the metadata and find out the size of TITLE_CD and TITL_LONG_DD (+1 for - between them) and make sure they aren't longer than 70 character field. One test you could try is to make that really long (try A500) field and see if the problem goes away. If it does, then you have to find out the right size.

Also try getting rid of the qualifiers in the TABLE request for TITLEX.

TABLE FILE EXTR_EMPL_BONUS
PRINT
J1.SEG01.TITL_SHORT_DD
TITLEX
WHERE RECORDLIMIT EQ 10
END

Thank you So much BakakNYC.

do you have any idea about my second question? thank you

Error Parsing MASTER FILE XXXXXXXXXX is telling you there's something in your metadata that it didn't like. You will most likely get a little more detail if you issue a CHECK FILE XXXXXXXX.

Create a simple procedure using the Text Editor or in App Studio that issues CHECK FILE FILENAME. See if you get a specific explanation of what the error is. You could also try to open the master file using App Studio or from the Reporting Server.

Is this a synonym you created using the Create Synonym or is it a Cluster master file referencing other master files? If it's the former, then try recreating the synonym with a different name and compare the old one with the new in the text editor to see if you can find a difference.

Sometimes the code is "tightened" in the next release and syntax that was not so legitimate, starts to give you errors. That'll require more diagnostics.