1 of 1 people found this helpful
Yes, the ctmvar utility can be used for this or you can set variables within the job def or as part of post-processing.
E.g. for ctmvar -
ctmvar -action set -var "%%\MY_JOB_START" -varexpr %%TIME
be aware that the time variable "%%MY_JOB_START" will be set to when you are running this command, so some experimentation may be required. Maybe use the prev field to run this first or use conditional processing if you are executing commands (to get the variable setting in up front).
Are planning on having lots of global variables? BMC have a general guideline that anything over 100 global variables can impact Control-M Server performance. As with all guidelines, you might find that this figure varies from site to site.