Hello all,
I found out how to give the right value to my environment variables, with Basic code. I now have a problem with the use of these variables.
It's OK if I want to use them in a file name : #$Variable#
But there's something I don't understand inside a transformer : to fill an output...
An idea would be to have my variables in a sequential or hashed file. Every other job would refer to this file to get the value of the variables.
But how could it work if I need my variables to define a path or a file name (e.g. #path#FileName#SiteCode#.txt, in the input or output tab for a...
I'm sorry, but what do you mean by "build a batch" ?
If it is a Unix shell or DOS script, I'm looking for another solution : my job will have to run either on Unix or NT servers, so I try to be independant of the OS. All my code has to be inside DS.
If "batch" is a DS object, I don't know it...
I don't understand the environment variables in DataStage...
I am developping DS jobs for a multi-site company. The same job will have to run on each site. So I need a variable or a parameter, that I shall set once for each site, to have all my jobs using the same site code.
To my mind, this...
Hello every body,
I am beginning with DataStage. I need to develop a job that generates a file, and the name of the file must include the current date (e.g. FileName_2005-07-03.txt).
-1) I know how to load the current date into a variable, inside a job. But is it possible to use such a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.