DSXchange

If you understand SQL then you will understand how DataStage would conduct an update. You could pull the rows out of the source table into a file and manipulate them. Then, update the rows in the target using the appropriate SQL in the target stage. Your question smacks of lack of training on DataSt...

Everything within DataStage Server is handled as a string. If you do an equality (an "=" sign) between two variables, it is done as a string comparison. If you do > or < or >= or <= then it is done as a lexicographic string compare. That's why dates should always be put into the form YYYY-MM-DD (ISO...

The importexport facilities of DS objects within DataStage still remains one of, shall we say, anemic capabilities of the client side software. It is a constant source of disappointment for people who wish to pluck a couple of modified objects from the repository and export them. While not graceful,...

You can't. That's the way DS works. One option you may consider is to write a file named "fred" and then use an after-job routine to rename it "barney" if it's not empty.

Yeah, your job is not i/o, network, or disk bound. It's probably not doing any ODBC/OCI lookups, so therefore you don't see the lag a job suffers waiting on a database to return a row. What you have is the beginnings of seeing a job run at the best boundary condition you can get: cpu bound. Once a p...

Another option is to hook the MS-Access mdb file into a SQL-Server instance, then use the unix --> ODBC SQL-Server driver --> SQL-Server --> MS-Access route to get at the data.

Your premise would be soooo poorly performing you shouldn't even think about doing it. It sounds like all you are doing is assigning a surrogate key. You should search this forum for techniques for doing surrogate key assignment. Basically, get the max value assigned in the table. Maybe use a stage ...

Make sure the reject link is the last output link in the output order in the transformer.

Read everything from Ascential for the last two years - it's all about a scalable framework to handle huge volumes. The Torrent acquisition was for the parallel technology product Orchestrate, on which Ascential has stated is the future path for the products to take. Everything is riding on that fra...

Why not just use a stage variable as I suggest and forgo the function?

glug glug

You can't do what you're doing. By quoting the names of the links, you're turning the entire right side of the expression into a literal. I don't think you realize what you're trying to do doesn't work. If you have a function that you are passing arguments into, you must define the function to have ...

Okay, you're saying you setup a stage variable called StageVar, and the derivation is DSLink4.PATIENT_FIRST_NM : DSLink4.PATIENT_LAST_NM : DSLink4.PATIENT_ID : DSLink4.PATIENT_KEY In the derivation of an output column, you put: checksum(StageVar) Have you tried to just output a column holdin...

I can't give you performance specifics, but there has been a lot of work done to the Orchestrate framework to expand its capabilities for performance, metadata, and to prepare it to be the foundation for the entire product suite (QualityStage, etc). So, there's a lot different between osh and PX job...

When Orchestrate was acquired by Ascential, the new GUI was replaced with the DataStage GUI. If you developed osh scripts by hand, then you must recode them to take advantage of the GUI. The GUI has access to features that have been added to the Orchestrate framework, as well as the support for the ...