Question on parameter passing to ExecSH
Posted: Fri Oct 20, 2006 2:14 pm
Hi-
In building our data warehouse I have decided to use the ExecSH functionality for the Before-job and After-job subroutine.
As I will be adding this code to all of the jobs, I would like to be able to pass a variable to the script with the name of the job to simplify maintenance, for example: /call/some/script.sh JOB_NAME.
The closest I have gotten is this: /call/some/script.sh %JOBNAME% where %JOBNAME% is defined as a parameter with the text string of DSGetJobInfo(DSJ.ME,DSJ.JOBNAME).
Obviously, the text string is just that, a text string, and does not get evaluated to the value I want to pass to the script.
So, is there some built-in variable within the job that I can use or is there some way to force the evaluation of the parameter to get the result I want?
Thanks
Sam Hillaire
In building our data warehouse I have decided to use the ExecSH functionality for the Before-job and After-job subroutine.
As I will be adding this code to all of the jobs, I would like to be able to pass a variable to the script with the name of the job to simplify maintenance, for example: /call/some/script.sh JOB_NAME.
The closest I have gotten is this: /call/some/script.sh %JOBNAME% where %JOBNAME% is defined as a parameter with the text string of DSGetJobInfo(DSJ.ME,DSJ.JOBNAME).
Obviously, the text string is just that, a text string, and does not get evaluated to the value I want to pass to the script.
So, is there some built-in variable within the job that I can use or is there some way to force the evaluation of the parameter to get the result I want?
Thanks
Sam Hillaire