DSXchange

It is possible to expose a sequence as a web service. The tricky part is then consuming the call and delivering the response, which can only be done in job(s). Do you really need so many jobs?!!

Uniqueness, against the next time you export the same object.

"s" had already been taken. "q" was the next available consonant in the word "sequence".

Assuming the first line is column names, I guess you could (a) validate that all the column names are valid and (b) establish the expected order of fields in the data records when processing that first line. The expected number of fields is also established from the first line, but counting the comm...

Read each line as a single VarChar column, and effect your parsing in a Transformer stage. Use stage variables to track where you're up to in each logical record.

Add a reject link to the Sequential File stage to capture any row that does not comply with the defined metadata.

The dsexport.exe command is available on the client tier.

What's wrong with what you're doing? Have you tried encapsulating it in a command like start ?

pjb = parallel job
sjb = server job
qjb = sequence job

There are lots of other tags (suffixes) for the other kinds of repository objects. I won't bother to list them all here.

But they're not "weird".

A question first. What method of authentication are you using for Information Server (internal IIS user registry, operating system or LDAP)?

My guess is that your connection had timed out before you attempted to perform the task. Can you perform it soon after establishing a connection using the Administrator client?

This is managed using environment variable APT_ORAUPSERT_COMMIT_ROW_INTERVAL

You need to prevent DataStage from inserting tsort operators, since there is no information in the job design to indicate that the data are sorted (presumably via ORDER BY clauses in the Oracle SELECT queries). You can achieve this in one of two ways: an explicit Sort stage set to "Don't sort (...

Are your data partitioned by the primary key prior to sending to DB2? If not you may be attempting to update the same key from more than one node.

Will it "cause performance issues"? No. "Performance issues" are in the brain of the beholder - the job will work, but your expectations as to throughput may be awry. It will always help if all data are local but that's not always logistically possible (e.g. lack of space on the ...

Welcome aboard. Click on the message - it will take you to the stage from which the property value was removed.