Testing Performance

The amount of time EngageOne™ Enrichment requires for processing depends on the functions performed, the system used, and other system activities concurrent with the run. You should test EngageOne™ Enrichment to ensure that it completes processing in a time frame compatible with your print processing window. In some cases, EngageOne™ Enrichment may actually save time by eliminating steps in your current process.

On mainframe systems, you should also consider whether your test jobs are getting the same priority as production jobs. In many cases, test jobs run slower because they are given lower system priority than production jobs. You should also check the level of your run-time library (IBM C/370 Runtime Library, SAA AD/Cycle Language Environment, or Open Edition AD/Cycle C/370 Language Support Feature). Fixes or newer versions of the run-time library may be available that would enhance your application’s performance.