DSXchange

What is the largest number that will appear in column #3?
What should happen if column #2 is not precisely divisible by column #3?

Please post full detail of any exact error from the job log. "Validation failed" is a status that suggests you ran the job in validation mode. But this is only a guess, because I can not see the exact error.

Introduced in version 8.1, Preserve Type property is mutually exclusive with Sum Output Column property at the field level. This should be picked up by the stage GUI or the precompiler. (This is my enhancement request.) It isn't picked up, and that that leads to a rapid job abort at run time with a ...

I completely missed noticing the DBA !

Care to include a price comparison?

As has been explained numerous times in the past (a Search would have found them), DataStage always adds leading and trailing nonsignificant zeroes and a decimal placeholder when the data type is Decimal, to prove that precision and scale are being handled properly. If you don't want them, convert t...

"Am I right?" will almost always be answered with "maybe, maybe not".

The essence of your thought processes should revolve around the capacity of your database server to accept connections.

Of course the goal is not always to saturate it just because you can.

Assuming that XMETA was backed up properly (with the database quiesced or shut down and using database utilities) then you can restore objects in the database as at the time the backup was taken. If there have been objects created or amended in the interim, their status may be undetermined. It depen...

Multi-select is available in version 8 (it does a Quick Find under the covers) but not in version 7.

0xFD is a "value mark" (@VM). But that's completely unrelated to the original question which is about data type conversion. Please start a new thread for 0xFD question.

Might there be duplicates in the source data? In that case there's more to do. Are all columns Type 2 changes, or do you need to consider only some columns' changes? Map out the logic in a specification/flowchart and the rest will follow quite simply. For detecting changes where there may be duplica...

Welcome aboard. You're going to have problems preventing this alert message, since it comes from a component you did not include in the design. Range lookups are compiled into transform operators, and it's from one of these that the alert is being generated. Your best approach is to demote this aler...

You can use PAL but, as you note, it will be quite cumbersome. You'll need to have the first PrimaryName already copied, then do a condtional pattern to handle the second PrimaryName. The condition, of course, will be an equality test; if it is satisfied reclassify the second PrimaryName to the Null...

Did you change anything between the two runs, or must we assume that you encountered a transient error?

SQL functions are not permitted in the WHERE clause of a Filter stage. Refer to the Parallel Job Developer's Guide for full information about what is permitted.