Using the "-local" flag in runcp scripts

The "-local" flag is an optional flag within Assure's runcp script. This flag controls the location that input sources are captured from during the control execution. By adding the flag, the processing of input sources will occur on the Assure client, and the extracted data will be sent to the Assure server for the remainder of processing. 

This setup is commonly used in the following scenarios:

1. Mainframe input sources
2. Databases that are inaccessible from the Assure server

By using the Assure client with "-local" flag, the client will effectively serve as a proxy to locations that the Assure server wouldn't be able to reach directly. 

A comparison of the runcp processing behavior with and without the "-local" flag is below:

Without -local flag

If "-local" is not set in the runcp call, then the Assure client will spin up a local JVM and will notify the Assure server that the server needs to process the requested control. The Assure client will wait for a response from the server. Once the server finishes processing, it will notify the Assure client instance and the JVM and script on the client side finishes. 

With -local flag

If "-local" is set in the runcp call, then the Assure client will spin up a local JVM and will ask the server to send the layout definitions back to the Assure client. The Assure client will then process the input files per the layout definitions and send the extracted data back to the Assure server for the remainder of processing. The Assure client will wait for a response from the server. Once the server finishes processing, it will notify the Assure client instance and the JVM and script on the client side finishes.