Duplicate detection properties
The following table shows the properties that are used to control duplicate detection in Gateway Server.
| Keyword | Values or example | Description |
|---|---|---|
| fileDupCheck | true, false | This property controls whether duplicate file checking is done and whether it uses
transmission validation rules. Valid values for this property are shown in the following list.
|
| rejectDupFiles | true, false | Controls whether duplicate transmissions are rejected or accepted. When set to true, duplicate transmissions are rejected (not processed) and moved to the error directory. When set to false, a transmission detected as a probable duplicate is processed successfully and a message is logged to indicate a probable duplicate transmission was detected. To process a transmission identified as a probable duplicate, use the resume command with the forceDup option specified. |
| onDupCashLetter | off, warn, rejectFile | Controls whether batch (ICL) duplicate detection is performed and what action is taken
when a probable duplicate batch (ICL) is detected. When set to rejectFile, a batch (ICL) identified as a
probable duplicate causes the containing transmission to be rejected (not processed) and moved to the error
directory. When set to warn, the transmission containing the probable duplicate batch (ICL) is processed
successfully and a message is logged to indicate a probable duplicate batch (ICL) was detected. When set to
off, duplicate batch (ICL) detection is not performed. Note: In order for duplicate batch (ICL) detection to
be performed, the dupFileCheck must be set to useCounts.
|
| onDupBundle | off, warn, rejectFile | Controls whether bundle duplicate detection is performed and what action is taken when a
probable duplicate bundle is detected. When set to rejectFile, a bundle identified as a probable duplicate
causes the containing transmission to be rejected (not processed) and moved to the error directory. When set
to warn, the transmission containing the probable duplicate bundle is processed successfully and a message is
logged to indicate a probable duplicate bundle was detected. When set to off, duplicate bundle detection is
not performed. Note: In order for duplicate bundle detection to be performed, the onDupCashLetter must be set
to warn or rejectFile.
|
| dupKeepDays |
10,
10 busDays |
Controls the number of days the duplicate transmission, batch (ICL), and bundled data is
kept in the duplicate detection database tables. The time interval is specified in either calendar days or
business days (busDays). The business days option excludes the weekends and holidays. This parameter enforces the removal of duplicate data from the database tables for transmissions that have successfully completed the EOD process and have become older than the number of keep days specified. |
| rejectOldFiles | true, false | Controls whether old transmissions are rejected or processed. When set to true, transmissions whose create date is older than the duplicate detection data stored in the database tables are rejected. This is treated as a duplicate and can be forced through using the forceDup option on the resume command. When set to false, transmissions whose create date is older than the duplicate detection data stored in the database tables are processed. |