DSXchange

kumar66 wrote:Data string '2009-12-13 08:57:45' does not match format '%dd-%mm-%yyyy %hh:%nn:%ss'

That is precisely correct.

Just look at it!

Then proceed as Arnd advised.

gphukan wrote: The following task should be done in single DS job.

Why?

To system tables? Connect to db2 as the user name under which jobs execute and execute the query

Please try the following experiment. In the Administrator client's Command window execute the following query and let us know the result.

Look carefully at the times. An attempt was made to start the job when it was already running.

You lack SELECT privilege to SYSIBM.SYSTABLES, which DataStage requires to verify that your table name exists in the target database.

Either get that privilege granted or execute as a user that has appropriate privileges to the system tables.

9:59:59 is not matched by %hh:%nn:%ss format.

Same way. Filter on the row number (@INROWNUM). Force the parallel Transformer stage to execute sequentially - for only 1000 rows it's not worth doing otherwise.

This advice from kejuste can and should be ignored. We're talking blocks in QualityStage Match here - nothing whatsoever to do with any database! That you're getting block overflow suggests that you're not discriminating particularly well with your choice of blocking fields. Try adding one or two mo...

Simplistic and, quite possibly, wrong. After all, it was not RT_LOG60 that could not be opened.

Can you post the code for CompareFiles if it's changed from since you posted it, and include some DSLogInfo() calls to log what actual pathnames the routine receives? Presumably the -1 codes are caused by OpenSeq failing. If it seems fruitful can you please add all the pertinent clauses to each Open...

OK, without explicit triggers a job sequence will interpret a Routine activity as having failed if its return value is anything other than zero. Add an explicit Failure trigger so that "failures" are handled, even though the trigger goes to exactly the same place as the Success trigger (th...

I was under the impression that what you really wanted was a success/otherwise result from the routine.

On that basis I have been recommending returning any other information by other means, so that Ans contains only the success/otherwise value.

Or you could Search DSXchange - I am sure this question has been answered in the past.

Then use DSLogInfo() to put the result into a log entry, rather than returning it through Ans. If you must return the result, use one of the user system variables (@USER0 through @USER4) rather than Ans.