TIBCO Foresight Transaction Insight

TIBCO Foresight Transaction Insight Using Importer Software Release 5.1.0 December 2015 Updated: January 2017 Two-second advantage

Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO, Two-Second Advantage, TIBCO Foresight Archive and Retrieval System, TIBCO Foresight Instream, and TIBCO Foresight Transaction Insight are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright 2010-2015 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information General Contact Information TIBCO Software Inc. 3303 Hillview Avenue Palo Alto, CA 94304 USA Tel: +1 650 846 1000 Fax: +1 650 846 1005 Technical Support E-mail: support@tibco.com Web: https://support.tibco.com (Note: Entry to this site requires a username and password. If you do not have one, you can request one. You must have a valid maintenance or support contract to use this site.)

Contents Document Purpose... 1 System Requirements and Installation... 1 Audience... 1 Capabilities... 1 Input and Output... 1 Preparing the Guidelines... 2 Using Importer... 2 Validation Notes... 2 Command Format... 2 Commit Options for Shared Data... 13 Document Level Z -records... 14 ZXTID = Submitter ID... 14 ZXTIA = Monetary Amount... 14 Extended Fields... 14 Database Information Security... 15 Command Line Examples... 15 Importer.ini... 16 Importer Interruptions... 16 Importer Problems... 17 Return Codes... 17 Using Importer Page i 1/17/2017

Document Purpose This document describes how to use Importer.exe with TIBCO Foresight Transaction Insight. System Requirements and Installation Please see TIB_transactioninsight_nn_readme.txt for information about system requirements. Importer is installed by the Transaction Insight installation. For installation instructions, see TIB_transactioninsight_nn_installation.pdf where nn is the Transaction Insight version number. Audience This guide is for technical staff who manage document flow into Transaction Insight. Basic EDI knowledge is assumed. Capabilities Importer imports a single validation detail results file into the TI database. It can also import the corresponding EDI file. Importer is a command line program. It can also be started with Automator, which can repeatedly invoke Importer to process multiple files. Input and Output This typical configuration supplies a validation detail results file and an EDI file as input into Importer. TIBCO Foresight Instream Validation EDI Validation Detail Results Importer Oracle or SQL Server DB Using Importer Page 1 1/17/2017

Preparing the Guidelines For a file to be imported into TI, it must be X12, HIPAA X12, or EDIFACT data. Each has slightly different requirements, as explained in Data_Types_and_TI.pdf. Using Importer Importer.exe is in the Foresight\TransactionInsight\version\ Environments\environment\ bin directory. Validation Notes To get the most recent error messages in Transaction Insight, edit Instream s $Dir.ini or fsdir.ini file, uncomment the ShowVersion line and set it to 1: ShowVersion=1 This also adds the Instream validation version information into the TI database so that it can be displayed on the Transmission Summary page and is available for future enhancements. Command Format Importer -r <InStream filename> [-e <EDI filename>] [-i[nbound] -o[utbound]] [-savegooddata] [-savegooddatatypes <list>] [-skipisaonerror] [-l <log filename>] [-v <log level>] [-a] [-m <n>] [-t] [-cf n] [-cs <connect string>] [-ca n] [-autocommit] [-autonomous] [-savewarnings] [-n <name>] [-ini <ini filename>] [-sender_location <i[nternal] e[xternal]>] [-receiver_location <i[nternal] e[xternal]>] [-ini <ini filename>] [-version] [-nohipaa] [-encryptini <ini>] Use double quotes around values containing spaces or special characters. Command line settings take precedence over those in Importer.ini. Using Importer Page 2 1/17/2017

Importer Arguments Command line option Corresponding INI file option Explanation and Examples -r -r <InStream filename> Required. Specifies the path and name of a detail results file produced by Instream. The file must contain STRUS and SVALU records. Importer can only import result files that were created with a guidelineplus or a guideline that was merged with a guidelineplus. See ForesightHIPAAGuidelineList.pdf for a list of guidelineplus guidelines. Examples: -r "c:\inbound837s\ K837_5532.dtl" -r "\\FCEDI\in\K837_5532.dtl" -e -e <EDI filename>] Specifies the path and name of the EDI file that corresponds to the detail results file. If this option is used, the file s individual application documents (claims, etc.) are stored in the TI database. If this option is not used, TI users cannot use forms to view or correct the EDI. Examples: -e "c:\inbound837s\ K837_5532.edi" -e "\\FCEDI\in\K837_5532.edi" -i[nbound] or -o[utbound] Required. Marks the transmission as inbound and o marks it as outbound. -o -a in section: appendtolog=1 -a Causes logging information to be appended to the existing log, rather than overwriting it. See also v and -l. -a -archiver Do not use this argument. It is for TIBCO Foresight internal use when moving archived documents into the TIBCO Foresight Archive and Retrieval System TI Portal. Using Importer Page 3 1/17/2017

Importer Arguments Command line option Corresponding INI file option Explanation and Examples -autocommit n [Database] section: autocommit=1 When shared data is encountered, Importer commits all uncommitted data, reducing the chance of deadlocks or blocking when multiple Importers are running. See Commit Options for Shared Data on page 13. -autocommit -autonomous in [Database] section: autonomous=1 When shared data is encountered, Importer commits the shared data, reducing the chance of deadlocks or blocking when multiple Importers are running. See Commit Options for Shared Data on page 13. -autonomous -ca in [Database] section: maxconnectattempts=n -ca n Sets the number of times for Importer to attempt to connect to the database. This can be helpful if you get occasional timeouts while attempting to connect to your database. The default is 3. -ca 10 Using Importer Page 4 1/17/2017

Importer Arguments Command line option Corresponding INI file option Explanation and Examples -cf in [Database] section: commitfrequency=n -cf n Specifies how many SQL statements should be executed before issuing a commit. The default is 0, which means a commit occurs when a transmission is completely processed. This lets partial transmissions be rolled back if an importing error occurs. However, this can cause a large roll-back if the input file is large or has many errors. Committing more often allows you to reduce the size of rollbacks. However, if there is a problem during the import, a partial transmission appears in the database. Testing may be needed to determine a good balance. Fewer commits mean faster importing but larger roll-backs. See also Commit Options for Shared Data on page 13. -cf 10000 (commits every 10,000 statements) -cs in [Database] section: connectstring=string -cs "<connect string>" Provides the database connection string in the format described in Importer.ini. -cs "DRIVER={SQL Server}; SERVER=(local);DATABASE= TI42DEMO;UID=sa;PWD=sa" -encryptini -encryptini ini Encrypts database information by modifying the ini file. ini specifies the location of your ini file. Please see Database Information Security on page 15. -encryptini C:\example\Importer.ini -h Optional Prints help for Importer arguments to the console. -h Using Importer Page 5 1/17/2017

Importer Arguments Command line option Corresponding INI file option Explanation and Examples -ini -ini <ini filename> Optional Path and filename of the Importer configuration file. Overrides the default value of Importer.ini found in the bin directory. -ini "C:\TIBCO\TransactionInsight\5.0.0\Environmen ts\ti500dev\bin\myimporterconfig.ini" -l -l <log filename> Specifies the path and name of the log file. By default, information is logged to Importer.log in the directory containing Importer.exe. -l c:\tilogs\my837.log -m in section: edimemlimit=n -m n This sets the maximum file size (in kilobytes) to be loaded into memory. -m 0 (the default) prevents loading into memory. Loading the input EDI file into memory can speed up the import, especially if the -savegoodata option is used. -m 1000 (loads files up 1 MB in size into memory for processing) -n in section: name=instancename -n <name> Assigns a unique name (1 to 50 characters) to this Importer instance. -n machine2 Using Importer Page 6 1/17/2017

Importer Arguments Command line option Corresponding INI file option Explanation and Examples -nohipaa in section: hipaa_mode=0 Turns off "HIPAA mode". In HIPAA mode, all 40xx HIPAA transactions plus 997 and U227 are identified as 4010A for purposes of summarizing and viewing. When HIPAA mode is off, these transactions are identified as 4010. By default HIPAA mode is on. -nohipaa -receiver_location i or -receiver_location e A new partner is automatically created if the receiver is not defined in the database. By default Importer determines if it should be considered internal or external. With receiver_location, you can force the new partner to be internal (receiver_location i) or external (receiver_location e). receiver_location i -savegooddata in section: savegooddata=1 Causes good EDI documents to be saved, as well as bad. -e must also be used. When -savegooddata is used, the default is to save good data for all transaction types. You can specify specific transactions with savegooddatatypes. Without -savegooddata, only EDI for documents with errors of severity 2 or greater are saved to the database. -savegooddata -savegooddatatypes in section: savegooddatatypes= set1, set2, setn -savegooddatatypes <list> Lists the transactions for which good data should be saved. It only applies when you also use -savegooddata. For 837s, the I, P, and D are capitalized as shown in the example. -savegooddatatypes 837P,837I Using Importer Page 7 1/17/2017

Importer Arguments Command line option Corresponding INI file option Explanation and Examples -savewarnings in section: savewarnings=1 Store validation warnings in the database, as well as errors. Default is to not save warnings. Note: Using this option for Importer, the sw option for TIUtilities, and setting IsTop10ErrorTypeSearchOn to true in Web.config allows you to view the top 10 errors by count and filter them by type or severity via the TI Errors page in TI. -savewarnings -sender_location i or -sender_location e A new partner is automatically created if the sender is not defined in the database. By default Importer determines if it should be considered internal or external. With sender_location, you can force the new partner to be internal (sender_location i) or external (sender_location e). -sender_location i -skipisaonerror Prevents interchanges from being imported if their ISA has an error. -skipisaonerror -t in section: forcetest=1 Causes data to be treated as test data regardless of the value in ISA15. -t -v in section: loglevel=n -v <log level> Determines how much information is written to the log file: 1 Errors only 2 Warnings and Errors (default) 3 Info, Warnings and Errors 4 Debug, Info, Warnings and Errors Debug information is only output with a debug build of Importer. -v 3 Using Importer Page 8 1/17/2017

Importer Arguments Command line option Corresponding INI file option Explanation and Examples -version Optional Prints version information to the console. -version -h (or no arguments) Running Importer with the h or no arguments displays help text. in [InStream] section: n.n.n=path This identifies the ErrMsgTrans.txt file used by Instream version n.n.n. When a new version of Instream ships, the ErrMsgTrans.txt file and a database script are made available for TI: The script updates error messages in the TI database. The ErrMsgTrans.txt file is used by Importer to create the non-technical, HCFA, UB92, NSF, and ADA error messages from the original EDI error message in the Instream results file. By default, Importer looks for the ErrMsgTrans file in the same directory as Importer.exe. If the result file contains information for version 5.6.0, Importer looks there for ErrMsgTrans_5.6.0.txt. 7.2.0=C:\Errormsgs\ ErrMsgTrans.txt in [InStream] section: user_n.n.n=path or user=path If your company has a custom error message file used by Instream, this identifies it. The setting can be specific to Instream version n.n.n or it can apply to all versions. Examples: user_7.2.0=c:\errmsgs\ OurErrMsgTrans.txt or: user=c:\errmsgs\ OurErrMsgTrans.txt Using Importer Page 9 1/17/2017

Importer Arguments Command line option Corresponding INI file option Explanation and Examples Useinputfileas original=1 Note: We recommend that you no longer use the Importer argument useinputfileasoriginal. In pre-release 5.0.0 versions of TI this argument was used to allow for searching for transmissions using file information such as file name. This is now accomplished using the Transmission Search page. If set to 1, this sets the original file information from the validation Detail Results file s STRT record instead of the value supplied in the Instream m argument: Original File Name Original File Date Original File Path Original File Size It can be seen on the Transmission Search, Transmission Summary, and Document Summary pages in TI. Setting this to 1 takes up space in the database. This argument is ignored if Instream is run with the m argument. useinputfileasoriginal=1 useridzrec= <z-record name> Name of a z-record that contains a unique user identifier for each document in the file. This record must exist at the same loop level as the TIBCO Foresight Unique ID (FSUID) found in the IDENT record. For details about the FSUID and the looping levels where the FSUID is output, see ApplicationDocTables.pdf. useridzrec=zb1 ZXTID= <z-record name> Name of a z-record that contains a submitter identifier for an application document in the file. Default = ZXTID ZXTID=ZZT01 Using Importer Page 10 1/17/2017

Importer Arguments Command line option Corresponding INI file option Explanation and Examples ZXTIA= <z-record name> Name of a z-record that contains a dollar amount for an application document in the file. Default = ZXTIA ZXTIA=ZZT02 ZXTDT= <z-record name> Name of a z-record that contains a date/time for an application document in the file. Default = ZXTDT ZXTDT=ZZT03 overridedocumentinfo= <0 1> Override submitter ID, $ amount and date/time in "known" transaction types with values from ZXTID, ZXTIA and ZXTDT records. For generic X12 these values are always used. However, this allows you to supply alternate values for the "built-in" types. overridedocumentinfo=1 ZXD=<z-record name> First 3 letters of the Z-record name used for extended fields of type date/time. These Z-records must end with the values 00-99. For example ZXD00, ZXD01,... ZXD99. Default = ZXD ZXD=ZDT ZXF=<z-record name> First 3 letters of the Z-record name used for extended fields of type floating point. These Z-records must end with the values 00-99. For example ZXF00, ZXF01,... ZXF99. Default = ZXF ZXF=ZFP Using Importer Page 11 1/17/2017

Importer Arguments Command line option Corresponding INI file option Explanation and Examples ZXM=<z-record name> First 3 letters of the Z-record name used for extended fields of type $ amount (money). These Z-records must end with the values 00-99. For example ZXM00, ZXM01,... ZXM99. Default = ZXM ZXM=ZMY ZXN=<z-record name> First 3 letters of the Z-record name used for extended fields of integer (number). These Z-records must end with the values 00-99. For example ZXN00, ZXN01,... ZXN99. Default = ZXN ZXN=ZNM ZXS=<z-record name> First 3 letters of the Z-record name used for extended fields of type string. These Z-records must end with the values 00-99. For example ZXS00, ZXS01,... ZXS99. Default = ZXS ZXS=ZST In [Database] section: NLS_LANG=<LANGUAGE_TER RITORY.CHARACTER_SET> Indicates the language, territory and character set when connecting to an Oracle database. This value overrides the value of "NLS_LANG" set in the parent environment or Windows registry. If nothing is set in the environment or registry (as is typical with Oracle Instant Client), the driver assumes US7ASCII which does not permit character values greater than decimal 127. In order to handle characters outside the legal range for ASCII (> 127), NLS_LANG should be set to use the WE8MSWIN1252 character set, which allows these characters. See the Oracle Database Globalization Support Guide (available at docs.oracle.com) for details of the NLS_LANG environment variable. [Database] NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252 Using Importer Page 12 1/17/2017

Commit Options for Shared Data These options are designed to prevent blocking and deadlocks when multiple instances of Importer are running. Blocking and deadlocks can occur when two or more Importers are trying to update the same shared value such as a Z-record unique ID, and one has to wait too long for the other to commit the ID. Both options cause shared data to commit immediately after Importer processes it, although they use different methods to do this. autocommit When shared data is encountered, Importer commits all uncommitted data. This can cause commits to occur at what appears to be random intervals, although they are not actually random. Commits occur when shared data is encountered, or when the normal commit frequency is used. Autocommit can cause a slight reduction in importing performance. It can increase the chance of partial files being committed if there is an error running importer, a consideration if you are using document level FSUIDs. autonomous Note: Use of this option is not recommended. When shared data is encountered, Importer commits the shared data. It does this by creating two database connections when it starts. When it encounters shared data, it uses the second database connection to insert the data and then immediately commits it. Other data is not committed until the normal commit frequency is reached. Autonomous can cause slower importing but the chance of partial file commits is lessened. These options go in the [Database] section of Importer.ini, like this: Example 1 - Blocking Importer 1 finds the value APPLE in a Z record and adds the value APPLE to a table that assigns IDs to Z record values. Importer 2 finds the value APPLE in a Z record waits for Importer 1 to commit. Importer 2 blocks until Importer 1 is finished, slowing down the import. Either of the commit options will cause Importer 1 to commit immediately after discovering the value APPLE in a Z record. Using Importer Page 13 1/17/2017

Example 2 - Deadlock Importer 1 finds the value APPLE in a Z record and adds the value APPLE to a table that assigns IDs to Z record values. Importer 2 finds the value PEAR in a Z record adds the value PEAR to a table that assigns IDs to Z record values. Importer 1 finds the value PEAR in a Z record and attempts to add the value to the table but because Importer 2 already has a lock on the table to insert that value, Importer 1 waits for Importer 2 to finish and release the lock. Importer 2 finds the value APPLE in a Z record and attempts to add the value to the table but because Importer 1 already has a lock on the table to insert that value, Importer 2 waits for Importer 1 to finish and release the lock. Now Importer 1 is waiting for Importer 2 and Importer 2 is waiting for Importer 1. They are deadlocked. Either of the commit options will cause Importer 1 to commit immediately after discovering the value APPLE and Importer 2 to commit immediately after discovering the value PEAR so no deadlocks occur. Document Level Z -records Z-records are needed for pre-named Submitter ID, monetary amount, and extended field values. These Z-records have default names as specified below. The names may be overridden in the section of the Importer.ini file. ZXTID = Submitter ID A Z-record with the name ZXTID should be present within the ST/SE loop and should contain the unique submitter identifier for the document. The name may be overridden by specifying ZXTID=<z-record name> in the section of Importer.ini. ZXTIA = Monetary Amount A Z-record with the name ZXTIA should be present within the ST/SE loop and contain the monetary amount for the document. The name may be overridden by specifying ZXTIA=<z-record name> in the section of Importer.ini. Extended Fields Extended fields have the form ZXt00-99 where t is the first character of one of the allowed data types: Date/time, Float, Money, Number, and String. Using Importer Page 14 1/17/2017

ZXD00-99 = Date/time Date/Time values must follow the pattern CCYYMMDDhhmm[ss[d[d]]]. For example: ZDD03 indicates a Date/Time value and might contain 201112011304 to indicate 1:04 PM on December 1, 2011. ZXF00-99 = Floating point ZXM00-99 = Monetary ZXN00-99 = Number (integer) ZXS00-99 = String Database Information Security To enhance database security, Importer no longer writes database information to log files. For additional security, you may choose to encrypt database information. To do this, run Importer with the -encryptini ini option and specify the location of your ini file. For example: Importer -encryptini C:\example\Importer.ini This causes Importer to access the specified ini file, change the line beginning with "db=" to "db_enc=", and encrypt the remainder of the line. IMPORTANT: After this change connection information is machine readable only. Ensure your database connection information is accurate before encrypting it. Command Line Examples Example 1: Typical command line This is a typical command that imports my837.edi and my837.results. Errors go into my837.log. Importer.exe -e C:\testdata\my837.edi -r C:\testdata\my837_results.txt -l C:\testdata\my837.log Example 2: Saving good data for 837I only This command is like Example 1 except that good data is imported for 837i transactions. Importer.exe -e C:\testdata\my837i.edi -r C:\testdata\my837i_results.txt -l C:\testdata\my837.log -savegooddata -savegooddatatypes 837I Using Importer Page 15 1/17/2017

Example 3: Debugging This is a typical command line when debugging. It sets the logging level to 4 (the maximum). Importer.exe -i -e C:\testdata\my837.edi -r C:\testdata\my837.results -l C:\testdata\my837.log -v 4 Importer.ini Importer s default configuration file is Importer.ini, and it is always located in the same directory as Importer.exe: Foresight\TransactionInsight\version\Environments\environment\bin Among other things, this file determines which TI database Importer should use. It contains many other settings that can be overridden with command line arguments. Importer.ini contains comments that are designed to make it self-explanatory. You can override the default ini file name and location using the ini argument. Please see the Using Importer section on page 2 for details. Editing Importer.ini Uncomment the settings that you want to use by removing the semi-colon at the beginning of the line, and adjust the setting as needed. Example. To change the logging level to the maximum, remove the semi-colon and change the number to 4: loglevel=4 Importer Interruptions If Importer is interrupted while importing a document, it attempts to roll back the transaction. In some cases a file may be partially imported but does not appear in the UI or affect statistical information. If you are using a workflow, place the file that was interrupted while being imported into the start of the workflow. You can find it in Importer s Error directory under the workflow. If Importer loses connection with the database, files that were not imported will be stored in this directory. Because unique identifiers (FSUIDs) are used to identify documents in TI you may be unable to import a file that failed previously. In this case, use the TIPurge program to remove the partially imported file information from the database. See TIPurge.pdf for details. Using Importer Page 16 1/17/2017

Importer Problems AIX If Importer dies unexpectedly on a file that is larger than you normally import, check with your UNIX administrator about adjusting the LDR_CNTRL environment variable. This gives Importer access to more memory on 32-bit AIX machines. It should be set before attempting to import the file. Contact TIBCO Foresight Support before attempting to import a file larger than 50 MB on 32-bit AIX. Return Codes Return Code Meaning 0 Importer ran successfully. 1 Problems with the command line parameters. 2 Could not find the input file. 3 Error parsing INI file. 5 Error processing transaction filter. 10 SQL error. 20 Could not find standard name in result file. 21 Unknown standard found in result file. 25 Guideline not based on guidelineplus. 30 Error parsing EDI. 35 Could not read error message translation file. 40 Could not load the Oracle library. 45 User pressed <Ctrl>-C or <Ctrl>-<break>. 50 Unknown error. Contact Foresight Technical Support. Troubleshooting information log Notes Specified with -l command-line parameter or logfilename setting in Importer.ini. Default: Importer.log in the directory containing Importer.exe. Using Importer Page 17 1/17/2017