DSXchange

You shouldn't need TRIM on the numerics. This may help. An even more efficient way to handle this is to perform any arithmetic - for example add zero to the number. DataStage always returns the shortest possible string from an arithmetic calculation. And it's definitely quicker, if the item is alrea...

Hmm. If the association exists in another UV table (which the query would have found) you would need DROP TABLE rather than DELETE. An association may also be defined in a file dictionary, and can be created without a custom SQL statement. What you have to do is to find out where the association is ...

The first thing I'd do is search this Forum with a topic of "mutex".

UPCASE on a numeric field will return the numeric field unchanged, so this will not cause you a problem. TRIM with a single argument trims white space, which also should not be a problem, unless your "numeric" contains multiple internal white space characters. Obviously a TRIM function that specifie...

Okay, well this happens when your job control is trying to attach to a job that does not exist. I suspect the job name is spelled wrong in your job list or has been renamed. This error occurs because the DSAttach API doesn't have a graceful return code for invalid job name. Your choices are BLOW UP...

This message indicates that there is an internal corruption in the log file (RT_LOGnn) for your job. The log file is actually a hashed file. You have a number of options. (1) Purge the log file of all entries. (2) Use the command RESIZE RT_LOGnn * * * to re-build the log file. (3) Use the command UV...

I've seen this before, many years ago, and it's a real gotcha - and one of the areas where different variants of UNIX handle things differently. Some require that things are done using only your primary group, while others give you the union of all permissions from all your groups. Yuk.

This has been answered in the past.
When you search specify "parameters" and "notification" and select "search for all".

What this message is telling you is that the name you have chosen for your UV table already exists as an association name (nested-table name) in another UV table. To find out which other UV table this is, execute a command something like this: SELECT TABLE_SCHEMA AS PROJECT, TABLE_NAME AS ASSOC_NAME...

What Ken's trying to say, in his own inimitable style, is that this Forum has a perfectly good Search capability, and he is exhorting you (and everyone else) to use it before posting questions that may already have been answered. There's a limit to the number of times even the most helpful of people...

I'm not at all sure that tmp nnnnn files are created by DataStage (unless it's your own routines that is creating them). According to a message posted July 2003 on the u2-users@oliver.com list, UVTEMP gets used for: - temporary files when compiling sica constraints ('compconXXXX') - temporary files ...

IIRC it IS there in 5.2. Once you check the "create" check box, a command button "Options" becomes enabled. This opens a window wherein you can specify all the tuning parameters of the hashed file that you wish to create. Type 30 is dynamic, anything else is static. On the DataStage CD you will find...

I think what you're seeing here is a perfectly reasonable restriction. If you think about it in SQL terms, what you're trying to do is SELECT keycol, othercol1, othercol2 FROM dataset WHERE keycol = ? This is why the key column ( keycol in my SELECT clause) must be the same name as the lookup column...

They differ by 129 Rows, It's not possible to see the input data as we are having million of records to be processed at any point of time. this Difference also is not constant, In some Job, there is not any difference at all while in other Jobs it somewhere around 1000 records. Do these differences...

At your release there is no copy capability from Aggregator stage input to output links. The only mechanism available to you is to Save the column definitions from the input link into your Repository, switch to the output link and Load them from where you saved them (by default this is under the Sav...