Kourier executes schedules and services as phantom processes on your U2 server. The output generated by a phantom process is automatically captured by the RDBMS in the &PH& (UniVerse) or _PH_ (UniData) directory. A unique file is created for each run of a schedule or service. Over time, this can generate a large number of files. For example, if you had a schedule which runs every 5 minutes between 6:00am and 6:00pm which runs 5 services, a total of 864 files would be created each day. These files should be deleted on a periodic basis.
In some cases, when Kourier executes a command, the output is written to the &COMO& (UniVerse) or _PH_ (UniData) directory. These files should be deleted on a periodic basis.
Kourier uses the KT_IOTEMP file as temporary storage for a number of processes. In most cases, the items that are written to this file are automatically deleted from this file as schedules and services are run. However, when a process fails or aborts, a few items may remain in this file. On a periodic basis, you can clear this file provide that all messages queues are empty. Clearing this file when all messages queues are not empty may cause data integrity problems between your U2 server and the integrated application.
If you are using the Kourier SQL Accelerator, the log file used by the SSIS packages created by Kourier should be purged on a periodic basis. There are three types of files written into the LOG directory: 1) .OK files indicated that the process completed successfully, 2) .SKIP files indicate that a file was skipped because a more recent file was found, and 3) .ERR files indicate that the process completed but has some number of processing errors. A sample SSIS package to purge .OK files is provide with the Kourier software. Generally, .ERR and .SKIP files are dealt with manually.
Kourier Integrator Setup and Administration Guide