Here is how AUTOEDIT variables are resolved.
a. For each Job that Control-M/Server submits, it is sending to the Control-M/Agent the parameters and variables.
b. What type of variables to be sent to Control-M/Agent is controlled by the "VARIABLE_INC_SEC" parameter from Control-M/Server.
Valid values(Default value is LOCAL):
- SYSTEM - All the AUTOEDIT variables for each submitted Job are sent to the Agent. These include System, Global, Group, and Local variables.
- GLOBAL - Global, Group, and Local AUTOEDIT variables are sent to the Agent for each submitted Job. System AUTOEDIT variables are not sent.
- GROUP - Group and Local AUTOEDIT variables are sent to the Agent for each submitted Job. System and Global variables are not sent.
- LOCAL - Only Local AUTOEDIT variables are sent to the Agent.
If the Global Variables are in use(ie, setting "VARIABLE_INC_SEC" parameter to GLOBAL or SYSTEM), then for each Job that is being submitted to the Agent, all the Global AUTOEDIT variables will be resolved at the Control-M/Server side (on the SL_SB) and then will be sent to the Agent. As a result, that would consume more time than usual. However, determining the overhead of this depends on the Control-M/Server machine, the disk performance, the database performance, etc.
If each AUTOEDIT variable is taking 2 ms to be resolved, that means the Control-M/Server will take 1.5 seconds delay on resolving each Job; if there are about 1500 AUTOEDIT variables defined.
This makes overhead, a matter of machine specification(ie, available resources) and a matter of what is acceptable for environment and operation.
Please check the needs and set the relevant values based on needs and then check the performance of jobs processing and overall operation.
Usually, there are many environments having something like 100 global AUTOEDIT variables but not much more.
It is not recommended to use a lot of Global Variables if the local variables and group variables could satisfy the needs.