DSXchange

You can, of course, do anything in job control (batch) code that a job sequence can do - a job sequence is nothing more than a job control code generator. Therefore, in your batch code, use DSExecute() to execute your command, script, BAT file, whatever and to capture its output, then use that to pr...

AND he's got a job as a short order cook, frying stuff on the CPU !

String value "2005-12-14", complained of in the error message, does NOT look like MM-DD-YYYY format to me.

Welcome to DSXchange. You will find that the people here are usually helpful, but the use of "urgent" in the question usually has the opposite effect since we are all volunteers here - it might be urgent for you but not for anyone else. Your use of urgent in the subject line makes things even worse...

Buy the Siebel PACK that goes with DataStage.

You should be designing your parameters well before you take up any ETL tool.
In DataStage I recommend adding the job parameters as early as possible in the job design process - maybe even before the first save, if there aren't too many of them.

ORCHESTRATE is the name of the structure that delivers the rows generated by the job. It is a structure in the same sense that SQLCA is a structure - you can recover elements from it by referring to them by name. (In another sense it's an object: peeking at the methods is not permitted.)

Mark col2 and col3 on the output as Key, and let DataStage generate the UPDATE statement. Choose "update existing rows only" as the update strategy.

Even if you think you have a good backup, export the entire project first. This will aid whoever has to come in to clean up the mess if you try doing it from the command line.

vinod wrote:Now in my current project i have to do performance tuning ,in how many ways can i increase performance ....

Throw bigger hardware at it.

Identify less efficient practices and replace them with more efficient practices.

Vague question, vague answers.

It's related to DB2 client software or to ODBC driver - they are very similar.

You assertion is incorrect: the incoming date is NOT in YYYYMMDD format. The error message informs you that it is in YYYY-MM-DD format. Be more general with your specification to the Iconv() function - just specify "DYMD", which will handle both formats.

The ark had come to dry land and Noah exhorted all the animals to go forth and multiply. He came upon two snakes who seemed to be unwilling to move. "Didn't you hear me tell all the animals to go forth and multiply," Noah asked them. "We can't," they said, "we're adders".

Of course you can tweak your jobs by tuning buffering. This includes tweak in both directions! Ask "this guy from IBM" to amplify the comment. Ask why buffering is tunable if it's not supposed to be tuned. Information about how to tune buffers and transport blocks is given in IBM's Advanced DataStag...

What are the SQL data types of the two input columns? Are you using Data Elements? Have you used the Debugger or active stage tracing to ensure that the incoming values are what you believe them to be? Please execute the following query from the Command window in Administrator: SELECT EVAL "8.0...