DSXchange

Is it only that that job with job no xxx, or for all the jobs that exist in project? It it confined to one, you can try to create a copy of the job and delete the old one and rename the existing one, which will create a new set of interfile hashed file and hence solves the problem. If you have probl...

Sort the records based on the key with KeyChangeCol enabled. Now sort in Descending and using transformer, filter those rows whose previous records has KeyChangeCol = 0 (No duplicates).

How are you triggering the job, by JobSequence or from script?
If its script, you can fram the loop easily. If its through JobSequence, maintain a log table to extract dates/tablename and update the same table after each extract. And you can schedule the same for n times.

Ok so, you need to run Loadn for SYSDATE-1 or SYSDATE as Initial load by looping it. And schedule the jobs from tomorrow or whatever.

us1aslam1us wrote:But if you specify the 'Scale' you won't get that zeros.

There you go... Removing the scale produces the result. So it does a string manipulation first and does a implicit conversion later.

Does your Historic table have data from 2000 to 2007?
Do you need 1/1/2000 data for current comparison or manipulation?

Ok 7.5.1A (Server Edition) seems to be good enough to handle.
As Kim use to say 7.0 sucks.

My bad... Dont konw how I assumed it as Oracle.
SYSCAT.TABLES can be used for DB2.

Hi, Is it consistent for all the jobs? Just try to create a simple routine which have nothing but CALL DSLogInfo("Hello World",""); TEST the Routine and check if you get any warning? Call it in a Jobsequence and see it the same happens. If the same warning appears, check the generated Job Control fo...

Check if you have columns been mapped to the second link.

Dose this error prompts for all the Job you run or some specific job which handles huge volume data? Or when you run many job parallely?

Try to maintain the Unicode from source.

Hi Narasimha,
Are you sure? I just ran a quick test, in Version 7.0. Though I pass leading 0'a as input, the sequential file truncates the zero.

As specified, Null can be defaulted from the source during extraction and if the Business rule compels the key to remain Null, the same can be reverted using DefaultNullValues and NullFieldValue can be used.

Good to see a doubt got clarified after 3 years.