DSXchange

Keep in mind it may not be ade as the signature's first three hex characters. In earlier releases than 6.0 it was ace, and a different key can be specified in uvconfig; I have seen dae used, for example.

If you're on 7.5 you can use Kim's solution, because MKS toolkit is shipped with DataStage. So most UNIX commands are available. You may need to specify ExecSH rather than ExecDOS as the before-job subroutine or "UNIX" as the Shell argument for DSExecute. In each project the SH verb now points to th...

NEVER delete the RT_... objects. Or the DS_... objects. These are tables in the Repository database that store the run-time (and design time) information for the job. They are created when the job is created, and no mechanism exists for creating them subsequently (apart from manual intervention). Yo...

Sort on ALL grouping columns, and tell the Aggregator stage that you have done so (on the Inputs properties). There's no point sorting otherwise. This allows the Aggregator stage to free up memory as soon as any change occurs in a grouping column. At a pinch, you can tune the memory consumption of t...

Note the different location of the "/" and "." characters in

COMPVIEW/DEV2LIB.INVDPT (which failed)
and
DEV2LIB/INVDPT (which worked)

The solution should now be clear.

As Administrator, use Administrator client to execute


You may also need to grant table privileges to any extant UV tables.

Which stage type are you using? Oracle_7_Load, Oracle_Express_Load or Oracle_OCI_Load? In the Oracle_7_Load stage, the Loading Mode property can be set to TRUNCATE. In the Oracle_Express_Load stage the Load Action property can be set to "Clear Data and Load". However, this does not appear in the Ora...

That's why, in the Best Practices class, the recommendation is to create totally separate jobs to populate hashed files. The reason for this is obvious when you accept that more than one job at once can be using the hashed file for reference lookups (and, indeed, that the cache of this can be shared...

You're doing a lookup against a hashed file and the total number of bytes in all the key columns, as generated in the Transformer stage reference key expression(s), is more than 768 - which is the maximum permitted by the MAXKEYSIZE configuration parameter in your uvconfig file. I suspect - since th...

It might be -1 being reported as an unsigned TinyInt. But you really should be asking this question of the vendor through your support provider. We don't have the source code (though much of the source code for dsjob can be found in Server Job Developer's Guide and Parallel Job Developer's Guide man...

Your job number is 330 (from the error message). In the project directory on the server is a subdirectory called RT_BP330 which contains the code generated by compiling Transformer stages and job control routine for this job. Within that directory is a file called JOB.403394601.DT.1369463998.TRANS2 ...

Do NOT use a user DSN. DataStage does not read them. This is deliberate and documented.

There are six help files. The first three are the most useful.

HELP

HELP BASIC

HELP SQL

HELP CONV

HELP PICK

HELP BCI

The requirement to increment the date for each of the five sets of 500 rows makes this really ugly to do in a Transformer stage. A Routine will be much cleaner and easier to maintain. One extra step if you are using the Routine to write to the text file would be to position to end-of-file after open...

The job may be locked for any of the following reasons (and the list is not exhaustive). job is open in another Designer window, by you or another developer job properties open in Manager, by you or another developer job being monitored, by you or another developer job was locked by a process that w...