DSXchange

The IsNull() function works in all scenarios. Did you check the nullability in the DESCRIBE of "colname" in both environments? It would seem to be a nullable field and this generating your error message.

I learned the answer to this question the hard way last week. It is a serious deficiency in the tool and should be that difficult to implement as the backup file contains all the jobs in discrete files which sould be simple to restore singly. The documentation is also weak in that it doesn't clearly...

Change the Data type to NVARCHAR followed by unique. It will work. No, it won't work using those suggestions. NVarChar and VarChar aren't relevant when it comes to sequential file quoting. And what "unique" has to do with this query is beyond me. Perhaps I have missed something and you co...

In that case, the reject link is probably not going to help much, and I can't think of a reason for a rollback during a read operation. Can you try to execute the SQL manually from your database tool of choice to see if there might be some problem with the query or the table?

It could be that your XMETA is filling up an getting slower over time. Ask your DBA to check if general performance can be improved, i.e. through "runstats" on DB2. At version 8.1 the DataStage log files go into XMETA by default. This can be switched back to the original repository storage...

That is odd - I wonder why it is trying to execute a "rollback", which would indicate that some error or errors have occurred. Can you add a reject link to a peek stage and see if any rows might be erroring?

To which database you connecting and what sort of stage functionality are you using - i.e. just straight generated SQL or your own?

Whether UNIX or Windows, the uvsh executable is in the same relative location.

"DDL" Data Definition Language. Do a "DESCRIBE <table>" in both environments and check the nullability in both environments for the column in question.

The variable name in my version is $OSH_PRINT_SCHEMAS as well, I just can't type very well....

Most likely the DDL are not the same with respect to nullability between the two environments.

You may not be able to change the default value, but you can change the runtime value. Declare the parameter in your job and at runtime specify "true" rather than the default "false".

The Golem has most certainly acquired new ownership.

How do the COMP-3 fields relate to the "<column name>" error message?

You win the top prize in the category "Worst subject line" and are in the rankings for "Question most likely to receive silly responses". I hope you didn't mean the question the way it sounds. Imagine logging into the Oracle support forum and asking "What is Oracle". I'...