DSXchange

DataStage uses up to five classes of shared memory structure. These offsets are the starting locations for the disk shared memory segment (where lock tables and other structures associated with disk I/O are kept), the printer shared memory segment (per-user shared memory), the BASIC catalog shared m...

There isn't one. Write your own, or get a "UNIX on Windows" (such as MKS Toolkit or CygWin) and use the UNIX commands.

You can do all you like. The Lookup File Set stage has a property where you can elect to allow or disallow duplicate values. If you disallow, it supports another property that lets you specify how to handle "rejected rows".

Quoted? dsjob -run -param fred='Frederick, actually' project jobname

No changes required for this transition.

Ultimately, Batch (from Director), Job Control (from Designer in server job) and job sequences are all ways to create job control code. Job sequences, being a graphical interface, ought to be the easiest to maintain but really lacked enough flexibility until version 7.5.

I didn't answer because I was asleep (different time zone from yours). The others' answers have covered any ground I would have covered. That's the way of things at an all volunteer site.

If you go back to the very early days of this forum you will find a complaint that it couldn't make lunch. But we solved that one.

You need a mechanism for determining these numbers. The DSGetLinkInfo() function can report the number of rows passed by DataStage, but - when there are errors - this may not be the same number as were processed successfully by Oracle. To differentiate Insert from Update your original job design wil...

Isn't that the old name for parallel jobs?

Distributed hashed files have never been cache supported (definitely) and never will be.

Your customer is out of luck because of that choice. Details of the Repository are not in the public domain. You may get some ideas from searching here, but there's nothing official. DataStage is metadata-driven. You really must have good metadata management practices. Chuck Smith will post here abo...

Welcome aboard. :D This error is occurring on the client side, which may indicate a bad installation of the DataStage client(s). Can you see the job names in Director and/or Manager? Does it work from a different PC? The easiest "solution" may be to uninstall then re-install the DataStage clients on...

You would spend far more than this to engage one of the premium posters to answer just one question.

Yes. The rest of the answer is "how long is a piece of string?". Maybe if you implement the slow jobs first you can get some kudos by implementing the faster jobs later!