DSXchange

That is quite database-specific, it's not a general solution A general solution could employ similar code within a DataStage routine. But a calendar table not only solves the weekend question, it also provides a solution to the holiday question. And it offers the flexibility to handle things like Is...

Identify which dates don't match the format.

Use a Lookup stage and a calendar table (perhaps a time dimension table) to ascertain day name, then count them conditionally.

Yes, it makes sense to me. You had logging set to perform logging into the metadata repository. Something went wrong with that - it seems to have been being accessed via (an internal) Connector. The change that Support recommended switches job logging to the engine tier, using the old style of loggi...

Check that you have a non-zero, non-blank value actually in the Precision part of the decimal declaration. DataStage is finding one of these.

Why necessarily "from command line"? You can use the Sequential File stage.

You would have to write your own routine that invoked the "UniVerse" C API functions for invoking hashed files.

To pre-empt your next question, there is no other way if you insist upon using SDKSequences from a parallel Transformer stage.

vijaykumarpj wrote:This might be because of two below issues:
1) The sequential file may be empty.
2) The metadata mismatch.

"Skipped 3" rules out empty file.

It means your metadata do not accurately describe what's actually there.

Welcome aboard. A Search here for "recursive" should find you a few examples.

Use a Lookup stage and a calendar table (perhaps a time dimension table) to ascertain day name, then count them conditionally.

Use a Lookup stage and a calendar table (perhaps a time dimension table) to ascertain day name, then count them conditionally.

Only you can diagnose this. For example, at what point does the first job abort, and does it have clear/delete hashed file within it? Is it really NULL or is it "" that is being returned?

pandeesh wrote:Is there any relation between the no of nodes specified in the configuration file and the number of instances we can run a multi instance job?

No.