|
|
|
|
|
A user exit is a user-defined procedure that can be used to modify certain information before it is processed. At certain points in processing, a flat text file is produced describing information that is passed to the next step in a procedure. This text file can be modified by a user-defined exit script before it is passed on for processing.
Control-M/Server user exits can be used to enforce site standards (for example, file naming conventions or valid date formats), and to apply security definitions to limit certain user’s actions. Exits can also be used to trigger other actions prior or subsequent to execution of a Control-M job.
EXAMPLE: A flat text file is produced containing parameters to be processed by Control-M. The name of the text file is passed as a parameter to the user exit script. The user exit script runs, and is often used to modify the contents of the text file. However, it can also be used to perform any other action (for example, to copy information from the text file to another location). Control-M then continues processing using the modified text file.
User exits are implemented only if they have been enabled by setting the appropriate configuration parameters.
To implement user exits, see Implementing User Exits in Control-M/Server.
To view available user exits, see Control-M general user exits.