I dont think this is possible at the moment. Do you have a specific list of possible variable names for all your jobs?
If the idea is to make sure LIBMEMSYMs are defined on all jobs, you can just add LIBMEMSYM on the parent SMART folder - as long as the LIBMEMSYM is common for all the jobs in it. This way, any new jobs added to the SMART folder will automatically inherit the LIBMEMSYMs from the parent.
Thanks for your update. In this case, if no smart table being used any alternate way?
1 of 1 people found this helpful
If you are using Workload Change Manager to 'Promote' your code from one environment to another environment, you may be able to use a promotion rule that adds LIBMEMSYM variable to all the jobs. But, you cant check if LIBMEMSYM already exists which means LIBMEMSYMs are loaded twice. This wont cause any issues. But if you want to avoid it, you can just not have LIBMEMSYMs defined on any job & let the promotion rule add it to all the jobs during 'Promotion'.
It will not enforce anything but you could always do a direct query on the DB to show jobs that don-t have the variable defined.