DSXchange

you set your ErrorCode to that value somewhere in your after-job routine.

What is the contents in the log if you ?
Also, what is your ErrorCode value?

So, by posting this 3 times you think that you will get an answer 3x faster? Not from me.

You cannot call this from a PX transform stage, but you can create a DS/BASIC After-Job subroutine to set this value.

I'm still assuming that you changed the output Oracle stage column attributes somewhere and added a 0 length or "" value on a CHAR column or something similar. Could you click on a column in the Oracle stage, right-mouse click and "edit row" and go through all the columns for a setting? This is most...

Ahh, then perhaps you edited the column settings and specified a null length of 0 for one or more of the columns? Could you check that as well.

Does "#HdrFileName#:'.':#RejFileName#:'.':#SourceDate#" not work for you?

What length did you specify for the INPUT and OUTPUT VarChar column lengths?

What datatype and length is your source String column defined as? Option (2) and (4) won't work as your output is a decimal column. Option (3) is my preferred one, although (1) might work. What is a "partially quoted" file? Can you write just your original string and Decimal converted columns to a P...

Prabhakar - but he stated in his original post that he had a VarChar() column.

As Ray has already pointed out, since DS uses the loader you could ensure that the DS and handwritten loads are identical; meaning there wouldn't be a speed difference. The point is that DataStage will use a quick load by default, whereas the handwritten one needs to be manually tuned. I'd go for th...

I think sharing a DataSet across projects is valid; it is pretty much the same (in my mind) as sharing a table or sequential file across projects. There is no builtin method of discovering which DataSets are used in which jobs; but if you have the actual DataSet name hardcoded in the jobs you can ex...

Normally you use the "fix_zero" keyword on conversions to allow this, or "allow zero" on the type default. I don't know which environment parameter might globally affect this, though.

Shawn - I remember now, I had to write a short DS/BASIC program that goes into the log and cleanses "orphaned" information. I think that might be fixed at V8 and can check that next week. I might also have the code on my PC which cleans up the log and can post it here.

IBM Support has unraveled the mystery. In DS 7.5.2, the following tr command is being called: /usr/bin/tr In DS 8.0.1, the following tr command is being called: /usr/ucb/tr It seems that the /usr/ucb directory is being prepended and the tr command in that directory acts differently from the default ...