[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference rocks::dec_edi

Title:	DEC/EDI
Notice:	DEC/EDI V2.1 - see note 2002
Moderator:	METSYS::BABER

Created:	Wed Jun 06 1990
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3150
Total number of notes:	13466

3090.0. "FBR compile not working" by EDITEX::16.81.112.46::Stoddart (EDI Expertise Center) Tue Apr 08 1997 20:18

Hi all,

	I have a FIleBrideg table that is having problems compiling.  It's 
rather large but doing weird things:

IT107 = IF $PARTNER = "3M" THEN                                             
              IF IT107 = "6009"                                             
                  THEN GLOBSHIPVAL = LI_UNIT_PRICE                          
                      ENDIF                                                 
                       ENDIF;                                               
IT107 = IF $PARTNER = "3M" THEN  "6009";  

I get the following error:
Parsing the table...

           ENDIF
        ENDIF;
 IT107 = IF $PARTNER = "3M" THEN  "6009";
 Line Number 5329
%FBR-E-P_INV_EXP, Invalid expression operand 
Compile Aborted

I changed the line to IT107 = "6009";
and got the same error.
I deleted the line, and then got the same error on the line above it.

Any ideas on what it REALLY going on?

Confused and frustrated (as always when I post a note)
Lorey

T.R	Title	User	Personal Name	Date	Lines
3090.1		EDIBUS::newdial_p9.reo.dec.com::JOHNSON	Richard Johnson , http://samedi.reo.dec.com	`Tue Apr 08 1997 21:28`	10
	What version of DEC/EDI? Are you using the latest fbr$ui.exe patch from edieng""::user2:[decedi_<version>_patches]? There was a problem with large tables not compiling. That restiction has been fixed in the recent patches. Richard
3090.2	Have the latest pathces - still have problems	EDITEX::16.81.112.46::Stoddart	EDI Expertise Center	`Tue Apr 08 1997 23:22`	5
	Richard, I just loaded them down, and I still have the same problem. Lorey
3090.3		EDIBUS::newdial_p8.reo.dec.com::JOHNSON	Richard Johnson , http://samedi.reo.dec.com	`Wed Apr 09 1997 13:00`	11
	Please raise an IPMT against it. In the mean time could I copy the FBO from somewhere? Or perhaps you could uuencode or zip it and mail it to me? Thanks Richard edieng::johnson richard.a.johsnon@rkg.mts.dec.com
3090.4	810_out.fbo to edieng::	EDITEX::16.81.112.30::Stoddart	EDI Expertise Center	`Wed Apr 09 1997 17:49`	7
	Richard, I copied 810_out.fbo to edieng:: Thanks, Lorey
3090.5	Found problem - error not reported correctly	EDITEX::16.81.112.24::Stoddart	EDI Expertise Center	`Thu Apr 10 1997 01:57`	19
	Richard, CSC totk a look and found a problem a few lines above: pos = $STRCHR(LI_STOCK_NO,"0123456789); <- missing quote pos = IF pos <= 0 then 1; IT109 = IF $PARTNER = "TVA" THEN $SUBSTR(pos,6,LI_STOCK_NO); IT109 = IF $PARTNER = "3M" THEN I_LINE_CNT; IT107 = IF $PARTNER = "3M" THEN IF IT107 = "6009" THEN GLOBSHIPVAL = LI_UNIT_PRICE ENDIF ENDIF; IT107 = IF $PARTNER = "3M" THEN "6009"; but I still don't understand why it generated the error that I got. Should we still IMPT this as it is not reporting errors correctly? Lorey
3090.6		EDIBUS::newdial_p8.reo.dec.com::JOHNSON	Richard Johnson , http://samedi.reo.dec.com	`Thu Apr 10 1997 15:20`	16
	Lorey A missing quote is difficult to spot. The Parser cannot know what should be enclosed within the quote. A quote can be split across multiple lines and include most characters. As for the actual message it may be possible to make it clearer. I will log this error in our internal EDI bug system. I would only IPMT it if a customer requires a patch fix. Thanks Richard
3090.7	Just put it on the bugs list!	EDITEX::16.81.112.27::Stoddart	EDI Expertise Center	`Thu Apr 10 1997 18:37`	5
	Richard, Thanks - don't need to IMPT, but do want it to make it to the bugs list. Lorey