Name of the output file containing valid EDI.
(Command line option -ov)

Example (asterisk stands for the EDI filename):

ValidEdiOutputPathName=C:\out\*_good.txt

Name of the output file containing invalid EDI.
(Command line option -oi)

Example  (asterisk stands for the EDI filename):

InValidEdiOutputPathName=C:\out\*_bad.txt

Logging level for Docsplitter report file.
(Command line option -l)

0     =    debug

1    =    no debug

Example:

LogLevel=0

Report format
(Command line option -f)

x     =     xml

d     =     Delimited

xp    =     Generic XML

Example:

ReportFormat=d

Report file path and filename. Directory must already exist.
(Command line option -r)

Example (asterisk stands for the EDI filename):

ReportFilePathName=C:\out\*_Report.xml

Controls whether swapping will take place (For details, refer Displaying Tree Information during Splitting). Setting can be:

v    Swap data in valid file
i    Swap data in invalid file
b    Swap data in both

This is equivalent to Docsplitter’s -wv, wi, and -wb command line parameters.

Example:

PerformDataSwapping=b

Specifies the valid swap audit file. Do not use wildcards in the filename.

This is equivalent to Docsplitter’s -av command line parameter.

Example:

ValidSwapAuditFile=c:\output\auditv.txt

Specifies the invalid swap audit file. Do not use wildcards in the filename.

This is equivalent to Docsplitter’s -a1 command line parameter.

Example:

InvalidSwapAuditFile=c:\output\auditi.txt

Specifies the DataSwapper.ini file.

This is equivalent to Docsplitter’s -z command line parameter.

Example:

InvalidSwapAuditFile=c:\setupDswap.ini

Do you want to add the first ST02 (Transaction Set Control Number) value encountered in the file to the output filename? This is useful if you wish to identify good/bad files by their associated ST02.

0     =    no (default)

1    =    yes

Example 1:

AddST02ToFilename =0
results in a file named TestFile.good

Example 2:

AddST02ToFilename =1
results in a file named TestFile_0001.good

Where “_0001” refers to the first ST02 value encountered in the file.

Do you want to add the CR/LF after the segment terminator?

0   =    no

1    =    yes (default)

Example 1:

AddCRLFToDocumentEnd= 1
results in adding a line terminator after the X12/EDIFACT IEA/UNZ.

(820s and 835s only). Do you want to recalculate the value in the BPR02 after splitting? These two options let you recalculate the valid file and/or the invalid file.

0     =    no

1    =    yes (default)

If you split your 835s below the ST, you should consider recalculating the valid file’s BPR02 to create a valid 835.

If you split at the ST or above, you should consider not recalculating the invalid file’s BPR02.

Do you want multiple valid and/or invalid files to be concatenated?

0     =    no (default)

1    =    yes

This option lets you reduce resource use on the Docsplitter machine.

Docsplitter knows how many files its split will generate before it actually does the split.  FilesPerRun determines how many of them will be open at once while it actually generates the files. 

A maximum of n valid and invalid files can be opened at once. After that, they are processed and closed and then the next n valid and invalid files are processed. 

If you're doing large numbers of files per split, bigger numbers will be a little faster, but use more resources.

FilesPerRun also lets you limit the number of open files per pass if your system will only let you open a relatively small number of files (which can happen on Unix).  The end result will be the same regardless of the number you specify.

If FilesPerRun is omitted, 100 is assumed.

This affects content-based splitting and split-point grouping. It does not affect standard error-based splitting, which generates just one valid and one invalid file.

Do you want a CR/LF to follow each segment terminator?

0     =    no (wrap the output data)

1    =    yes (default)

See Input and Output on page Input and Output.

Do you want Docsplitter to recalculate the SE01 in the valid or invalid output file?

0     =    no

1    =    yes (default: recalculate)

Do you want Docsplitter to recalculate the GE01 in the valid or invalid output file?

0     =    no

1    =    yes (default: recalculate)

Do you want Docsplitter to recalculate the IEA01 in the valid or invalid output file?

0     =    no

1    =    yes (default: recalculate)

Do you want Docsplitter to recalculate the HL element values in the valid or invalid output file?

0     =    no

1    =    yes (default: recalculate)

Do you want Docsplitter to recalculate the TS2 element values in the valid or invalid output file?

0     =    no

1    =    yes (default: recalculate)

Do you want Docsplitter to recalculate the TS3 element values in the valid or invalid output file?

0     =    no

1    =    yes (default: recalculate)

Do you want to remove all empty files created by Docsplitter:

0     =    no (default; leave empty files)

1    =    yes

Do you want to include information about errors (from the detail file’s DTL records) in the XML or delimited report? If this flag is on, Docsplitter's report file will contain error messages as well as values encountered. 

0     =    no (saves memory)

1    =    yes (default)

(TIBCO Foresight® Transaction Insight® internal use only)

Do you want to include EDI data (from the detail file’s SVALU records) in the XML or delimited report?

0     =    no (saves significant memory)

1    =    yes (default)

If this option appears in the setup file, Docsplitter uses split-point grouping, which sets a maximum number of split units per file. For details, refer Debugging your Content-Based Splitting

n is the maximum number of units per file.

This option cannot be used with [Content Splitting Map].

Do you want to redirect output to the file specified with the -b command line parameter? 

0     =    no (default)

1    =    yes

Do you want to display splitting details in a hierarchical format? 

0     =    no (default)

1    =    yes

Do not set this to 1 when executing Docsplitter in a workflow run by Automator.

For details, refer Split-Point Grouping Examples

Do you want to display EDI values used for content-based splitting?

0    =    no (default)

1    =    yes

For details, refer Split-Point Grouping Examples

Do you want to display which data is splitting to each file for your variable split points?

0    =    no (default)

1    =    yes

Do you want to display loop levels as they are processed?

0 = no (default)

1 = yes

Do you want to display detailed file record IDs as they are processed?

0 = no (default)

1 = yes

Do you want to display checkpoint messages as they are processed?

0 = no (default)

1 = yes

For details, refer Sample Setup File

Docsplitter finds the most specific match in the list, and splits other transactions at the location designated with ALL. The order in which these entries appear does not matter.

Split points are listed on page Delimited report files.

Do you want to rebalance any of these in the split files:

  CalcValidSE01

  CalcInValidSE01

  CalcValidGE01

  CalcInValidGE01

  CalcValidIEA01

  CalcInValidIEA01

  CalcValidHL 

  CalcInValidHL

  CalcValidBPR02
  CalcInValidBPR02
  CalcValidTS2
  CalcInValidTS2

0 = no

1 = yes (default) – This causes Docsplitter to check the individual Calc settings.

There is no corresponding command-line parameter.

Specifies the split point for XML data.

See XMLatForesight.pdf.

For an example, see DocSplitter_XML.ini in the DemoData directory of Instream.

This section is processed when you use either -s or -TPA command line options

Specifies the split summary element for XML data. See XMLatForesight.pdf

Do you want Docsplitter to automatically create split files when ZCBS records are found?

0     =    no – use the Content Splitting Map to decide how to split.

1    =    yes

This eliminates the need to specify particular values.

For details, refer How Docsplitter uses the 997 or 999

This option cannot be used with [Content Splitting Map].

When using content-based splitting, do you want all valid EDI data to go to one file?

0     =    no – use content-based splitting on valid data too.

1    =    yes

When using content-based splitting, do you want all invalid EDI data to go to one file?

0     =    no – use content-based splitting on invalid data too.

1    =    yes

When using content-based splitting, do you want to split valid from invalid data also?

0     =    no – just split based on content.

1    =    yes

This section is processed when you use either -s or -TPA command line options

Determine which data is split when using content-based splitting, and names its output file. See page How Docsplitter uses the 997 or 999.

Similar to the AK3_Allow section.

This section is processed when you use either -s or -TPA command line options

Specify which error codes in the AK905-AK909 are considered warnings when doing 997-based splitting.