[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

3081.0. "Filebridge send error!" by HITOPS::MAYNARD () Wed Apr 02 1997 02:02

    We have a "Filebridge Send" error that suddenly stopped 
    working on our production 2.1C EDI Server (AXPEDI).  The system 
    manager was unable to find the symbol- "REPROCESS" -  within the 
    system or login  tables and suggested that it was a 
    filebridge related error or setup problem.  
    
    I would appreciate a knowledgable Filebridge person 
    that could help me figure this one out...(i've never
    seen it in my years of using the product).
    
    I used a dummy x.fbo and x.dat files to show that it doesn't 
    seem to matter what the parameters are....
    
    	filebridge send x.fbo x.dat 
    	%CLI-F-SYNTAX, error parsing 'REPROCESS'
    	-CLI-E-ENTNF, specified entity not found in command tables
    
    Normally, this would come back with a FB-F-error FBO not found. 
    
    The real command is:
    $FILEBRIDGE SEND DECEDI$MAPS:ECGEDI_832_O_0_AN.FBO
    USR01:[MAP$SUPPORT]ECGEDI_832_CENTAURI_970324.DAT_00000001/ -
    application = ECGEDI/PARTNER = CENTAURI/doc=3020832/ -
    test_ind=live
    %CLI-F-SYNTAX, error parsing 'REPROCESS'
    -CLI-E-ENTNF, specified entity not found in command tables
    $ERROR_MESSAGE:
     
    
    This of course has a customer impact and their outbound 832 has
    not been able to be processed for over a week!
    
    I can be reached at dtn 227-3375 or 508-952-3375 or MS exchange mail. 
    
    p.s.  I already tried renaming the data file and putting everything
          in the same directory etc.

T.R	Title	User	Personal Name	Date	Lines
3081.1		EDIBUS::newdial_9.reo.dec.com::JOHNSON	Richard Johnson , http://samedi.reo.dec.com	`Wed Apr 02 1997 09:54`	19
	This error can only have been caused by an image on your system from V2.1D. The /reprocess command was introduced in V2.1D. Have any patch images been installed recently? The image in question is fbr$ui.exe The following command will tell you what version fbr$ui was built against. $ anal/image fbr$exe:fbr$ui.exe /out=temp.txt $ search temp.txt decedi If it is V2.1D I suggest reverting back to the V2.1C image. Richard
3081.2	its 2.1C?	HITOPS::MAYNARD		`Wed Apr 02 1997 17:53`	19
	The image looks like 2.1C but has been changed recently.... AXPEDI>anal/image fbr$exe:fbr$ui.exe /out=temp.txt %ANALYZE-I-ERRORS, SYS$COMMON:[SYSEXE]FBR$UI.EXE;10 0 err ors AXPEDI>search temp.txt decedi image file identification: "DECEDI V2.1C" AXPEDI> AXPEDI>dir sys$system:fbrui*/date/sizew Directory SYS$COMMON:[SYSEXE] FBR$UI.EXE;10 3162 21-MAR-1997 22:02:50.69 FBR$UI.EXE_AXP;1 3160 21-FEB-1996 13:10:33.00 Total of 2 files, 6322 blocks.
3081.3		EDIBUS::newdial_6.reo.dec.com::JOHNSON	Richard Johnson , http://samedi.reo.dec.com	`Wed Apr 02 1997 19:43`	7
	take a copy of: edieng""::user2:[decedi_v21c_patches]fbr$ui.exe_axp it is a more recently built v2.1c patch. Richard
3081.4		EDIBUS::newdial_2.reo.dec.com::JOHNSON	Richard Johnson , http://samedi.reo.dec.com	`Thu Apr 03 1997 00:47`	11
	I meant to say fbr$runtime.exe If fbr$exe:fbr$runtime has an image file ID of V2.1D then you need to copy the correct patch image onto your system. Howerver if the image file id is V2.1C then there may be a problem with the patch image. Please place here results of: $ anal/image fbr$exe:fbr$runtime /out=temp.txt $ search temp.txt decedi
3081.5	2.1D runtime?	HITOPS::MAYNARD		`Thu Apr 03 1997 02:38`	28
	okay, this is 2.1D anal/image fbr$exe:fbr$runtime /out=temp.txt %ANALYZE-I-ERRORS, SYS$COMMON:[SYSEXE]FBR$RUNTIME.EXE;7 0 err ors AXPEDI>search temp.txt 2.1 image file identification: "FBR V2.1D " AXPEDI>search temp.txt 2.1/wind=10 Image Identification Information image name: "FBR$RUNTIME" image file identification: "FBR V2.1D " image file build identification: "" link date/time: 5-FEB-1997 10:39:58.10 linker identification: "A11-14" Patch Information Directory SYS$COMMON:[SYSEXE] FBR$RUNTIME.EXE;7 875 21-MAR-1997 22:02:49.41 Total of 1 file, 875 blocks. p.s thanks for your quick response!