DSXchange

Where are you trying to get this information? With the Job Handle you can get information on the job invocation ids.

DataStage does not have a capacity for recursive lookups the way you explained. It is possible to have several consecutive lookups to the same source located after each other in order to emulate this functionality but you would need to put sufficient lookups to guarantee that you would find the &quo...

I the error you are referring to the "<cr><lf>" one? If you exported a XML document then did you also try to import it as XML or as a DSX file? If you look at the file in your favorite editor, does the XML have line breaks between tags as expected?

In this case if you give the path to the existing project it will detect that during installation and perform an "update". I have done this before at versions 7 and below and see no reason that this won't work at version 8 but it would be best to make a copy of the directory prior to makin...

More information is required before anyone can assist. What type of a job, is the problem sporadic, does "reset" bring more information in the log file, has this job run without problems before - just to name a few.

type in "dsjob -ljobs" and you'll get the syntax described to you in the help.

If the job parameter is "REPORT_DATE" then how is the value of "ReportDate" being derived?

swerajan - most of the participants on this forum are not native English speakers, so using "text-speak" or "chatspeak" with lots of cryptic abbreviations is not good and certainly not professional. Likewise, this is a volunteer forum and thus the response to your request for imm...

I see - you mean the NLS settings for the output from the database. Makes sense.

I...When binding output interface field "REC_DATE" to field "REC_DATE": Implicit conversion from source type "decimal[8,0]"to result type "string". Are you certain that it is declared as "date"? DataStage cannot convert a number to date implicitly. ...

I'll let Sainath assist you further on this thread, now that the two of you have hit it off so well.

Sainath beat me to it.... But I'll add some information - You can declare the whole line as one VarChar() field and parse out what you need instead of entering a lot of column metadata.

Important is also your table definition, I would think that if your table definition as well as ODBC definition is VarChar(4000) that should go through without a problem.

DataStage can use much larger strings. Oracle and DB2, for instance, have limits on VarChar() sizes and I am fairly certain that the ODBC definition also limits strings.

Specifically, which database and version are you interested in?

How about defining your transform stage to execute "sequential"?