Archive for the ‘EDI / EAI Vendors’ Category

Maps with XML files that have empty tags fail with a post delimiter error

Saturday, April 12th, 2008

When an xml file is run through an XML map without using otxmlcanon pre-processor, the map fails if the xml file has empty tags, so it is very important to use the XML pre-processor.

FILE_STAT function has some useful information about files

Tuesday, November 13th, 2007

FILE_STAT function can be useful at times for debugging: VAR->OTType which is usually a "file" VAR->OTInputFileSize: which has the file size

Error when the square brackets are missed at the start of an element or a group

Friday, November 2nd, 2007

When the square brackets are missing or commented out at the start of an element or a group as shown below, one gets an error 'Access obj "VAR" for dm "DUMMYGROUP" not found' ;[] VAR->OTTargetSuccessful = "Yes" PERFORM("OTTrgEnd") }*0 .. 1 ;; |-- end DUMMYGROUP --|

Tips for Searching Trace Logs

Friday, September 7th, 2007

Application data: Start at the bottom. Search up for "| DM:" Outbound EDI: Search down from the top for "errcode (number)" Inbound EDI: Start at the top. Search down for "Error# " Other trace log items to look for: Map Component filename or data model name "ARRAY VAL" "get_source" "put_target" "VALUE STACK" or "vstk" Last error ...

Look for VAR->OTTmpErr or OTCodeErr in the trace to find out if there are any errors

Wednesday, September 5th, 2007

Look for VAR->OTTmpErr or ARRAY->OTCodeErr in the trace log to find out if there are any errors during the translations when the get_source and put_target doesn't find the maps that should be called and doesn't produce the output. For example when the trading partner doesn't exist in the Trade Partner ...

The environment variable GC_LOCALEDIR is important for AI3.2 control server to run

Friday, January 26th, 2007

The environment variable GC_LOCALEDIR is important for AI3.2 control server to run. If this environment variable is missing, then AI3.2 will not start.

AI Error – 184

Tuesday, September 19th, 2006

One might get a 184 Error when PERFORM("OTTrgInit", "", "") is not put in a flat file translation on the target or the environment variable OUTPUT_FILE is not defined either in the attachment or in the models.

Debugging the problem with EXECR function or others resulting in system signal errors

Wednesday, June 28th, 2006

This Post has been posted by a third-party in a discussion group and the same has been posted here since it is useful in the context of AI and debugging: You can try running a "strace" on the translation on each differing system. Strace is a system call trace, i.e. a debugging ...

TAI Segment on 997

Tuesday, April 11th, 2006

AI generates a TA1 on the outbound 997 when your trading partner sends a 1 in ISA14. Have your partners send a 0 in the ISA14 and AI will not generate a TA1 segment on the outbound 997. Or one could go into TradeGuide at the GS level of the partner and Select "None" ...

Time Conversion Tip

Tuesday, April 11th, 2006

This post has been published in a discussion group by a third-party and has been published here since it is relevant to the mapping techniques in AI: Requirements: While working on a global implementation (Application Integrator centrally located on a US machine) we had requirements to convert AI generated date/time to local date/time. There ...