DSXchange

Manager client, not Designer.

What's your expected output in the above example?

There are no nulls in sequential files. Sequential files don't have data types, just text, so there are no nulls.

That said, it is often useful to specify how nulls are represented in sequential files. This can be done as a column property or as a global Format property.

In Manager client click on table definition to select it then click on the Usage Analysis took (it looks like a beaker) in the toolbar.

Your explanation is incomplete. G1 has three distinct values in Col3, as does G2. Am I understanding that correctly?

If you can identify the ASCII code points used you can generate these using the Char() function, and use that value to perform the lookup.

QualityStage using an xxADDR rule set will standardize these nicely.

It won't work, because the log is either a hashed file or a table within XMETA.

Pretty much any SQL, subject to the usual caveats you'd have from any other client utility - privileges for the connected user and so on.

Don't worry about what View Data shows you - it converts your spaces to "NULL" specifically because you've specified that NULL is represented as spaces. Look in the file itself - all will be well.

Welcome aboard.

The technique you outline is valid. It might also be worthwhile performing a Usage (Where Used) Analysis on the table definition before modifying it, so you can be aware which other jobs touch it.

My guess is permissions on the hashed file or one or more of its components.

There is currently no role that prohibits running a job.

You could always use system() and UVwrite!

(This (writing to log from a Build stage) is not something I've done.)

What a strange requirement (to do this with DataStage)! You should really do this with operating system commands and redirection operators. To embed those in DataStage is really a waste of resources.