DSXchange

300 stage variables.

Enjoy.

At least you only have to do it once.

Try it. Let us know.

My guess - and it's only that - is that all the nulls will be on one partition.

But the job may abort if an attempt is made to use a key-based partitioning algorithm on a field in which nulls occur.

Interested to see your results.

The order in which they occur is important. One MUST occur before the other. The answer is to be found in the DataStage manuals.

Ordinarily DBMSCODE. Check with your support provider as advised - the Sybase OC stage may be different.

Chuck Smith (http://www.anotheritco.com) has a utility that can probably be adapted to your purpose.

Welcome aboard.

With Log view open in Director, right-click in the background area and choose Filter from the menu. You can also press Ctrl-T to invoke the filter.

This message can also be generated if your C++ compiler license has expired or your C++ compiler/linker is not configured correctly.

You could try this trick (you may need a different string): The tilde character is ASCII 126.

Use 191 (not Alt-191), ideally when importing the table definition from the Sequential File.

OK you've proved that it's happening. What's different between the times when it succeeds and the times when it does not succeed? Where does the script get values from? Is that guaranteed to be available at all times?

No idea. It's your server, not ours. You can use the Administrator client to find out - even if you are not the administrator; when you have a project selected the pathname of that project directory is displayed at the bottom of the window.

Welcome aboard. I'm going to assume that this is not a WTX question, even though you marked the job type as TX. For starters there's no dslog command - your desires were, I suspect, driving your fingers for that one. The dsjob command can only list the log of one job. So you would need to create a s...

On that same link define three more columns and populate them with link variables (pertinent to the link that goes to the database) SQLSTATE, DBMSCODE and LASTERR.

gssr wrote:The tables are from different database!! "

You did not state that earlier.

Use a range lookup.