DSXchange

What makes them special?

And did you do what was suggested?

Arrgh, that's ten months and four clients ago. I did not keep it. It ought not to be a difficult operation, though.

You can't remove zeroes if the data type is Decimal. DataStage puts them in to guarantee that the precision and scale are correct. You don't need to remove zeroes if the data type is Decimal. It's the same value with and without them. You can remove zeroes if you're converting to a string data type ...

Welcome aboard.

You're wrong. It can be done in the one sequence, precisely as datisaq outlined.

Just change it in DataStage, not in the database. See what happens. DataStage tends to size things in bytes, rather than in characters.

But, within the job design, it can be both. I do keep the column description, but add any description of the derivation and any business metadata that ought to be referred to. This does not invalidate the relationship between the link metadata and the table definition in the repository.

This is maintained in a table called DS_AUDIT in the local repository.

A Search for DS_AUDIT will reveal all you need to know and more.

This is not possible, as a Search would have revealed.

You can not avoid having the file created.

In an after-job subroutine you can check for zero size or one line (headings only) and delete the file, but you can not avoid having the file created.

Are you running on Windows XP sp2 and the others on sp1 or some other Windows operating system?

Not correct.

Try doubling or even trebling the size of the VarChar definition.

I particularly like the inbuilt small lookup table (integer to string or string to integer) capability.

You can (should) document stage variables on the initialization grid.

You can document column derivations in the Description column of the Columns grid, which is a multi-line control (use Ctrl-Enter to move to extra lines).

No, the folder is always there. Is there anything in the folder and, if so, is it enabled or greyed out?