Is it the Julian Date? I don't see any date function which will convert an Integer representation to date format using DATE function.I am not sure but might be you can do something like this:
14347 could well be a DataStage internal format (12 Apr 2007). Try applying an appropriate Oconv() function to get it into the format required in the SQL.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
it doesnt accept oconv in SQLs. i have worked it out and made them as a parameter to the jobs. now i need to capture current date and date of a week before in the job parameters.
Since sysdate - 5 is before sysdate - 1 try reversing the order in the BETWEEN constraint.
Also I'm not sure that sysdate is a function. But I'm not in a position to check right now. If it's not, you need to lose the parentheses from it - that is, use SYSDATE rather than SYSDATE().
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I avoid using sysdate in a source query since I am likely to have to reload data for a specific date in the past. I use a job control job to calculate the date then pass it to the real job using DSSetParam. The job control job has a parameter which is normally left blank. This causes the job control code to calculate yesterday's date. When this parameter contains a date (like 20070411) that date is used.
ds_developer wrote:I avoid using sysdate in a source query since I am likely to have to reload data for a specific date in the past. I use a job control job to calculate the date then pass it to the real job using DSSetParam. The job control job has a parameter which is normally left blank. This causes the job control code to calculate yesterday's date. When this parameter contains a date (like 20070411) that date is used.
Just an idea.
John
Joihn, can you please elaborate? i dont know what the job control parameter should be.