Change a default value by script
Moderators: chulett, rschirm, roy
Change a default value by script
Hi all,
I'm exporting my project using ISX tool.
In this project, there is some jobs that need to have a default value to run because the job that execute them doesn't fill it and is in another project and doesn't know the parameter value.
Can i change a default value directly in the job or change it in the isx or build a routine to change it using a script shell ?
Don't find anything in the forum.
thanks.
Carlos.
I'm exporting my project using ISX tool.
In this project, there is some jobs that need to have a default value to run because the job that execute them doesn't fill it and is in another project and doesn't know the parameter value.
Can i change a default value directly in the job or change it in the isx or build a routine to change it using a script shell ?
Don't find anything in the forum.
thanks.
Carlos.
Re: Change a default value by script
The first two are 'yes' but what do you have in mind for this script?CLOPES wrote:Can i change a default value directly in the job or change it in the isx or build a routine to change it using a script shell ?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Better answer would be to not be reliant on default values, sounds like a switch to leveraging parameter value files may be in order.
There's nothing inherently different about editing a dsx vs. an isx, both are doable and carry the same level of risk. You keep saying 'routine' which has a very specific meaning in DataStage, I'm thinking you just mean 'script' as in a scripted way to do the find/replace before the job is imported, yes? If so then that should be perfectly feasible as well.
There's nothing inherently different about editing a dsx vs. an isx, both are doable and carry the same level of risk. You keep saying 'routine' which has a very specific meaning in DataStage, I'm thinking you just mean 'script' as in a scripted way to do the find/replace before the job is imported, yes? If so then that should be perfectly feasible as well.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
I'm totally agree with you about best practice (not to be reliant) but i just retrieve this project and i can't change it for the moment.
I know too that isx file is just a zip file with jsb files encapsulated in xml code.
My question was :
can i change those values using a script shell ?
if not
can i change those values using a Datastage Routine or job ?
I think that shell is easier but if i can't do it....
I know too that isx file is just a zip file with jsb files encapsulated in xml code.
My question was :
can i change those values using a script shell ?
if not
can i change those values using a Datastage Routine or job ?
I think that shell is easier but if i can't do it....
You can edit / change a job export through whatever mechanism you have skills in and are comfortable with. As to the compile question - yes but only on the client side.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers