DSXchange

Or just use the proper trigger conditions as posted earlier - Finished OK for the 0 link and Otherwise for the 1 link. It will then know that you are handling any errors and stop doing it itself. I tried what Craig had suggested by changing the Expression Type to "OK (Conditional)" - I co...

Thanks Gentlmen. I did as suggested and the warning message still persists. I am not sure what I am missing. The shell script that I use returns a value $returnVal. $returnVal can be one of two values: 0 or 1. In the Execute Command activity, I have two two branches: one with ReturnValue (Conditiona...

In one of the job sequences I use the "Execute Command" activity which is used to invoke a shell script. The shell script returns two values depending upon the logic: 0 or 1. In the job sequence I use triggers to branch the flow depending upon the return value. When the shell script return...

OK. I did not realize that the comment was specific to FP 8.1 as I took it as a general response to my posting. Sorry.

I found that the "Edit Column Metadata" dialog box contains the option to set "Null Field Value" when the column is defined as NULLABLE. I set the NULLable property to Yes and set a value of '' for the column in question. In the subsequent stage, I set the NULLable property to No...

chulett wrote:Hmmm... very interesting. Anyone know for certain?

Not to sound too complacent, but more to be of help to other visiting this post.

This stuff really works and the code is in Production :D

Take a look at the Null Field Value property (there may not be one) and the Default Value property (which I'm guessing is set to ""). Thanks Ray. There is no Null Field Value property in "Edit Column Metadata" dialog box. I set the value in the "Format--Field Defaults"...

Hello All, (Disclaimer: I have searched the forums but could not find a similar issue.) I am trying to import a record using the Column Import stage. The record has an empty value for a VARCHAR field for a given column. The column is defined as VARCHAR with the NULLABLE property set to NO. When impo...

Using the {FILE}/pathname.sql works for Before/After tab as well.

I am not sure if this has anything to do with Fix Patch 1 for Version 8.1 that we applied recently.

But it works!!!

I realize that this post is somewhat dated. I faced a similar issue in the recent past. The job schematic (pertaining to the issue) is as below Modify Stage -------- Join Stage ------- Output Aggregator Stage -------- The job used "Same" partitioning on both input links for the JOIN stage....

Hi Ray, I removed the "Unicode" extension put automatically by the Peek stage. The warning did not go away. Instead, I added the "Unicode" extension to the target column (although it was not needed). Then I removed the "Unicode" extension in the transformer stage. The w...

Hi, I have created a simple job with the following stages. Sequential File -----> Peek -------> Transformer -------> DataSet The sequential file stage has one column (raw) that is unbounded VARCHAR. The Peek stage takes this column as input and produces an output that contains 100 records per partit...

Yes. Interestingly the problem disappeared once I used the ODBC Enterprise stage. I used the same scale and precision values as it was when the job failed with DRS. I will leave this thread open as the question is still open. It would be really good if there is a way to get the rejected records. Not...

Hi, I have created a parallel job that reads data from SQL Server using a SELECT statement. I am currently using "Dynamic RDBMS" stage for this purpose. The data is passed through a transformer and written to a sequential file. There are four values with DOUBLE as the data type in the outp...

Thanks Ray. I agree. I did not think about it.