Page 1 of 1

Posted: Wed Oct 24, 2007 10:14 am
by DSguru2B
How is this job called, from a controlling prospective?
The controlling job, whether it be a shell script or a job sequence, you can do this while passing the parameter to this job.
In a shell you can use the commands like date and pass month mask for one and year mask for another. In a sequence job you can use OCONV with the right format for month and year.

Posted: Wed Oct 24, 2007 10:22 am
by ds_debasis
DSguru2B wrote:How is this job called, from a controlling prospective?
The controlling job, whether it be a shell script or a job sequence, you can do this while passing the parameter to this job.
In a shell you can use the commands like date and pass month mask for one and year mask for another. In a sequence job you can use OCONV with the right format for month and year.
As it is in job level parameter, I cannot initialize it ( It does not support any function) .. Can I do it in before job subroutine shell script ? if so how I'll initialize the parameter in the datastage job.

Posted: Wed Oct 24, 2007 1:44 pm
by sri1dhar
ds_debasis wrote:
DSguru2B wrote:How is this job called, from a controlling prospective?
The controlling job, whether it be a shell script or a job sequence, you can do this while passing the parameter to this job.
In a shell you can use the commands like date and pass month mask for one and year mask for another. In a sequence job you can use OCONV with the right format for month and year.
As it is in job level parameter, I cannot initialize it ( It does not support any function) .. Can I do it in before job subroutine shell script ? if so how I'll initialize the parameter in the datastage job.
Deb,

Read DSguru's response again. How are you running your job? Do you have a Job sequence that's calling your job or calling from a shell script or running from Director?

If you are using a controlling job such as a Job Sequence or shell script you can programatically derive current month & date and pass them as parameter values. If you are running manually from the Director then you may have to manually enter as you are doing now.

Hope this helps.

Posted: Wed Oct 24, 2007 2:49 pm
by ray.wurlod
Instead of using job parameters you could use stage variables. Initialize them, and do not derive them further - that is, leave the derivation field empty.