When you export a job, import it at a new location, but there runs show the old behavior...
Happend to me, really, this is possible because DataStage allows to export different flavours of the "same". Glossary Design: This is represents what you "code" the designer. Executable: This is the result of a design after compilation. You can export: Design only Executable only Design and Executable Default is "Design and Executable". So if you make a change to the design, do NOT compile, export it and import at a new location the state there is: You see the change. It shows the old behavior on run (as DS executes the old version)! Let's face it. This is setup just asking for trouble. You can alleviate it by have a deployment mechanism where ever imported job gets compiled afterwards automatically. Well, if you always compile before export, you do not need got this length but for me, I surely will forget to compile from time to time when I am in a haste and I am really extra sure I have done it well. You see, sticking to proper d...