DSXchange

The biggest difference for you will be getting your head around the fact that hashed files play no part in reference lookups in parallel jobs. Instead, you have a choice of three stage types (Lookup, Join and Merge) depending on exactly what you need to do; each refers to an in-memory dataset when i...

It's the folder for the client tools, so there's no likelihood of crashing the server.
On the other hand, it does allow for mischief (for example changing the stage bitmaps!).

If you are in a before/after subroutine, the "recommended" way to stop the job is to set the ErrorCode argument to a value other than zero. This has the effect of stopping the job when the subroutine returns. While DSLogFatal can be invoked from either a before/after subroutine or a transform functi...

Having produced the file it is technically easy to use FTP to send it to the mainframe. The politics of doing so, however, may prove daunting!

It may be better to produce the file on your UNIX server, and have the mainframe folks initiate an FTP session to get it from there.

The Pivot stage manual is called pivot.pdf. It is in the Packages folder on your DataStage CD. Because you are on 7.x, it should have been installed in your DataStage clients' documentation folder (by default this is C:\Program Files\Ascential\DataStage\Docs).

That's cool.

However, there's no real need for a ".DAT" extension. This is what confused me.

A simple explanation of pipeline parallelism is the ability for a downstream stage to begin processing a row as soon as an upstream stage has finished processing that row (rather than processing one row completely through the job before beginning the next row). Pipeline parallelism is managed in par...

Why do you think this would make any difference?

Reset the job. (NOT re-compile, reset)

Then, in the job log, find an event whose subject is "from previous run...".

This will contain additional diagnostic information.

You can (at version 7.x) create a job template from this job. Unfortunately, the job template is on your client machine, so you would need some means to propagate it to the machines of other developers. Since it's a text file, this isn't difficult. Then you need some mechanism to have the developers...

Two output links, with separate table names, identical column metadata and identical output constraint expressions. :D

That they can't be found on the reference link must be detected in your Transformer stage, probably in a constraint expression on an output link. You have two choices. You can test the value of the link variable oletgtPostalCdIn.NOTFOUND You can test whether oletgtPostalCdIn.postalcd_wid is null (me...

Is it on the drop down list of SQL data types in DataStage? No. You are answered.

There is no mechanism for deleting hashed file stages , which is a question you asked. Just think of the implications if there were: mainly incomplete job designs. Search the Forum for advice on deleting hashed files; there are three methods, and the right method to use depends upon how the hashed f...

You can verify by selecting oasasv.exe (which isn't a DataStage executable), right click, choose Properties from the menu, then read the Description on the General tab and, perhaps, the information on the Version (or Summary, depending on the O/S) tab.