DSXchange

A reference input link is effectively a left outer join - it returns NULL in all columns if the lookup does not succeed. You can use a constraint on the output link to prevent these rows from being further processed, turning it into an inner join. Any right outer join can be turned into a left outer...

That's an intriguing question. The DS_AUDIT table can tell you which objects were changed, and when, and by whom, but does not preserve details of the change. Version Control can help only if you've taken before and after copies of the component in question. The same is true of export/import. The sa...

There seem to be a lot of folks called "someone" at your place! There are basically two approaches to "implementing" PL/SQL in DataStage. One is to execute the PL/SQL unchanged from a shell script via a call to DSExecute. Capture the output directly from the call or by redirection of the shell scrip...

First, your server must have been installed with NLS. If this was done your uvconfig file will have a list of configuration parameters whose names begin with "NLS". NLSMODE is the "master switch" - if NLS is installed but not enabled, then NLSMODE is set to 0. If NLS is not installed, you need to re...

Errors in DSR_SELECT often indicate that the indexing in the Repository is not up-to-date. It may be time to re-index your Repository. You can do this from the DS.TOOLS menu on the server, or from the Administrator client (Command window) using the command DS.REINDEX ALL To use this command you must...

Is there a way we can delete the hash files that are created temporarily during the project? Yes, it's called designing your job streams so that the hashed files are deleted. Probably the easiest method is to use the Administrator client (Command window) to execute the commands to delete the hashed...

Like so many of these undocumented routines, you have to figure out from the context what they're intended to do. What are the arguments? Where in the processing do they occur? What kind of Activity can you put into - or remove from - a job sequence that affects whether the call is generated?

The ODBC drivers that ship with DataStage are licensed only for use from DataStage stages. They are not licensed for use from code. However, they do work for 30 days (a "trial period"?) after which attempts to connect using them fail, generating a message indicating the need to purchase a licence. W...

If you're prepared to write a Routine, you can use the STATUS statement to retrieve lots of information about a file.

You can find sample code here for retrieving some attributes. Read about the STATUS statement in the DataStage BASIC manual.

The choices in server jobs are much more limited, and boil down to two; either perform the join within the passive stage that is extracting the data, or use reference lookups. The latter is necessary if the data being joined are from disparate databases. A reference lookup can be fed from any "datab...

To add to what Ken said, ODBC (and, later, OLEDB) are standards devised by Microsoft. These are the only ways for getting at Microsoft-hosted data (for example Excel, Access, SQL Server).

Beware that your ODBC connection will only work for 30 days using BCI functions then you will need to purchase a licence for the ODBC driver from DataDirect Technologies.

You can find the BCI manual here

The fastest solution is Convert(",", "", TheNumber) - to which rasi alluded. This function is available in both server and enterprise (parallel) editions. For mainframe (390) jobs the CONVERT function is not available; you would need to manufacture something using POSITION, SUBSTRING and CHARACTER_L...

Space within a dynamic hashed file can also be reclaimed using the RESIZE command (but not below the number of groups specified by the MINIMUM.MODULUS parameter).
The three asterisks mean "do not change any of the tuning parameters".

You do not need to have the log view open in Director to clear a job's log file. You can clear the log with the job selected in status view. Of course it still takes a while, because it is a selective deletion, but you don't have to wear the overhead of opening log view.