DSXchange

So... did this job compile properly? Do you have other jobs running successfully with a Transformer stage and only have an issue with this one? If just this one, have you tried a Forced Compile?

"compressed character fields"? :? OK, so they're not COMP-3 but what exactly are they? Never heard of them and the only occurrance of that particular string that Google returns an exact match on is your post here. Can you get a more "official" name / description for what is in th...

How exactly did you define those two fields in the job? We got the "varchar, nullable" part but it looks like you may not have specified a size for them.

To quote a line from a movie: "You have chosen... poorly". Seriously, rethink what hardware you will need for your stated goal of supporting 30 users on the 8.1 release of this product - an XP system (an unsupported O/S for this tool, btw) with 2GB of memory is well below what your minimum...

No, you found "a" bogus warning issue, don't assume that means any invalid characters message must therefor be bogus. I would wager they meant that specific message, with those characters and integer metadata in play.

We'll be here when you come back.

Make sure you've actually specified that property in the Email Notification stage and that you are using the same value as the other stages that do work for you.

All those things you've been trying are (on their own) only valid for versions before the 8.x release. Things are changed now. Involve your official support provider.

Since that's an O/S limit rather than a DataStage one, the answer would be yes. And it's not a generic UNIX O/S issue, just a couple of specific ones from what I've heard here - AIX in particular.

There are all kinds of "text editors" out there, as noted on the UNIX side things like "vi", "vim", "emacs", etc. I personally use UltraEdit on the client side.

Probably not the Funnel. Have you dumped the score for this? The Remove Duplicates stage requires sorted data from what I recall, so there may be a tsort operator in there it added that is holding up the show.

Not sure where the "float" part comes in as that's just decimal but how about dividing it by 100? And perhaps the DecimalToDecimal() function may come into the picture as well.

Ah... perhaps so, Mr Holmes, perhaps so.

As does -wait, it's just that the status returned is more... traditional. Agreed, however, that without either it's all about if it was able to start the job or not.

Exactly.

Hmmm... inserting records fails and the error message starts with "DELETE failed because". Odd.