Understanding Batch Versions Submitted Locally from the Microsoft Windows Client

Sometimes processing batch versions locally is not only beneficial but necessary. If you are processing batch versions where the data selection limits the number of records fetched, processing locally is not a performance concern. Processing locally might be necessary to help narrow down issues that you encounter during processing. When batch versions process locally but do not process successfully on the server, this might indicate that the issue is specific to the server. Processing batch versions locally places the logs on the workstation for ease in reviewing processing concerns.

Since the typical system configuration defines batch versions to process on an enterprise server, you need to override the processing location to process batch versions locally.

When you process batch versions locally, you can select these methods of output:

On Screen
To Printer
Export to CSV
OSA Interface Name