ICRE Configuration Parameters
Table 1 shows the configuration parameters
required by the ICRE task.
| Parameter | Required | Default | Description |
|---|---|---|---|
| Target directory | Yes | None | The path of the Gateway outgoing directory. After the ICRE file set is created, the file set is saved at the specified path. If Gateway is installed, this path must be the Gateway outbound source directory. An example of the path is install_directory\check\v409\Gateway\outgoing\source |
| Working directory | Yes | None | The path of the working directory. This directory is used as a temporary repository while the extract file is created. An example of the path is install_directory\check\v409\ITS\ICRE\working |
| Transmission definition | Yes | None | The name of the transmission definition, Sample01_FILE for example. For more information about creating the transmission definition, see Manage Transmission Definitions Page. |
| Minimum buffer size for ICRE record. | Yes | 51 | The buffer size for each ICRE record used while creating the ICRE file |
| States | Yes | BALANCED | The valid states an entry must be in before it is included in an ICRE data file. Multiple states may be provided using the state name separated by commas. |
| Categories | No | All | Provide the business day categories to include in the data file. The All value extracts
all categories for the current business day. Multiple categories may be provided by separating the categories
with commas. For example, 1, 2, 3. |
| Bank number | No | All | The bank numbers to include in the data file. A value of All extracts all banks. Insert commas to separate specific banks. All bank numbers specified must exist in the bank table of the FTM database. |
| Sort pattern | No | All | The sort patterns to include in or exclude from the data file. A value of All extracts
all sort patterns. Multiple sort patterns may be provided by separating the sort patterns with commas. Use Not
to indicate if the list of sort patterns is to be excluded from the data file. For example, specifying
1,2,3 includes sort patterns 1, 2, and 3 in the data file and specifying Not
1,2,3 excludes them from the data file. |
| Include Control Documents | No | true | Indicates whether the control documents are included in the data file |
| User exit class name | No | None | The name of the user exit used during data file creation. For example, com.ibm.paydir.izg.icre.userexit.SampleUserExit |
| Repost if critical mass exceeded | No | false | Indicate whether to re-run the task when the data file reaches the maximum limit of its file size and a few records are still pending. Set this parameter to true to run the task again and extract the information for the remaining adjustment records. Set this parameter to false to not run the task again. |
| Data file extension | No | .dat | The file extension used to create the data file. After running the ICRE task, a data file is created with the specified extension. |
| Route file extension | No | .rte | The file extension used to create the route file. After running the ICRE task, a route file is created with the specified extension. |
| Trigger file extension | No | .eof | The file extension used to create the end-of-file file. After the ICRE task completes running, the end-of-file file is created to trigger Gateway and indicates the file set is completed. |
| ICRE end of Day file extension | No | .eod | The file extension used to create the end-of-day file. At the end of the day, the ICRE task creates a file with a list of all extracted ICRE files for the business day. |
| Trackable interval Timeout | No | 5 | The interval, in minutes, used when creating a file expected event entry for the extracted data file. A value of zero (0) is used to disable the file tracking process. |
| Small file maximum | No | 300 | The maximum number of bytes for a small file size |
| Medium file maximum | No | 20000 | The maximum number of bytes for a medium file size |
| Include Adjusted Items | No | false | Indicate if adjusted items are to be included in the data file |