DSXchange

The only obvious thing is that, having enabled them, you're not using quoted identifiers.

You have not told us what error message(s), if any, you're getting to support your contention that the ODBC Connector stage is not working properly.

If that doesn't work, and you know a fairly unique fragment of one of the SQL statements, try these commands in the Command window:
Post your results.

There may be other OLETYPE values. Try

I need to run 5 sequencers No you don't. You need to run five sequences . A Sequencer is something you use within a Sequence to bring flows of logic together - it has the big blue arrow and three "lights" as its icon. Indeed, a Sequencer may hold your solution. In your master sequence, wh...

They will be in the link properties, and therefore in those entries in DS_JOBOBJECTS for which the OLETYPE suggests a link (for example contains the word "Input" or "Output", such as "CCustomInput").

Or you could use Oconv(@DATE, "DWA") to get the day name, or Oconv(@DATE, "DWB") to get the abbreviated day name. Then the numeric value does not really come into play.

... which is why I like the original typo - "Enterprice" licence.

That is, the value of APT_CHECKPOINT_DIR needs to be the pathname of that other directory in which you want running jobs to store checkpoint (restart) information.

The Hashed File Calculator, which is on the installation media in the unsupported utilities, will help you to calculate the size that the hashed file needs to be.

Ordinarily OAG messages travel as XML documents, so the XML stage should be able to handle them if you have the schema available. You could, of course, create your own custom stage type. You might find this developerWorks article on the OAG Integration Specification interesting, even though it does ...

You CAN use Aggregator stage. If you precede it by a Sort stage, the Aggregator stage will be fast.

You could perform the counts in a Transformer stage, but that would involve setting up stage variables for each which you may regard as tedious.

If it's a source use custom (user-defined) SELECT statement to CAST the column(s) as TIMESTAMP. Or use the appropriate SQL function to achieve that conversion.

Similarly, when addressing the target, use the appropriate conversion function in user-defined INSERT or UPDATE statements.

No. There's not need to convert. The IsValid() test will intercept any invalid values.

HemaV wrote:when i tried with AsInteger(lnk.col1) then it removed decimal point and decimal part values.

Isn't that what you wanted?

Just put calls to your timing before and after DSWaitForJob(). $OPTIONS TIME.MILLISECOND * Time before wait StartTime = System(12) * Wait Call DSWaitForJob(handlesList) * Time after wait FinishTime = System(12) Duration = FinishTime - StartTime Call DSLogInfo("Seconds spent waiting = " : D...