Single Startup API

The Single Startup Application Programming Interface (API) enables a user program to make multiple calls to a Control-M/Analyzer rule after performing a single startup of the Control-M/Analyzer Runtime environment.

The Control-M/Analyzer Runtime environment can be invoked by a call from a user program. Further details can be found in the Control-M/Analyzer User Guide. When not using the Single Startup API, each invocation of a Control-M/Analyzer rule from a user program normally causes the following actions:

1. Load SAS/C modules, Control-M/Analyzer modules and the invoked rule.
2. Initiate the Control-M/Analyzer Runtime environment and the invoked rule.
3. Compile the invoked rule.
4. Execute the invoked rule.
5. Delete loaded modules from memory.
6. Terminate the invoked rule and the Control-M/Analyzer Runtime environment.

When using the Single Startup API, the startup and termination phases are performed only once. For example, a program that sends each record of a file to a Control-M/Analyzer validation rule in a loop does not perform Steps 1, 2, 3, 5 and 6 (above) for each rule invocation. Instead, Steps 1, 2 and 3 are performed only on first invocation and Steps 5 and 6 are performed only on the last invocation.