DSXchange

You can not read them with a schema file; you can only describe them with a schema file. I presume you are using a Sequential File stage. Is the format fixed-width fields (which you don't actually have) or delimited? Or is there only one field. Try reading the field as a VarChar data type (string[ma...

I use conditional compilation (that is, $DEFINE, $IFDEF and $ENDIF) in routines to allow me to include DSLogInfo() calls and also to test things that can't be done ordinarily, such as whether null is properly handled.

Weight overrides supersede the agreement/disagreement weights calculated using m-prob and u-prob. (That's why they're called overrides.) "Not coming as expected" is singularly unhelpful to diagnosis. You will need to be much more specific, particularly in regard to precisely how you set th...

That's a really tough one to do generically. Sure you can cover what's available in the toolset, but actual examples have this horrible characteristic of being highly specific.

Even so, it's a good suggestion.
Would you like to volunteer to script it?

Not easily. You could do it with a routine, or a shell script. You need to read the control record \\NLS from the DS_JOBS hashed file in each project. Field #6 contains the default NLS map settings (server then parallel), field #7 contains the five default locale settings (server then parallel for e...

Format the cells in the worksheet so that leading zeroes are displayed.

Then maybe webmaster@dsxchange.com is who you should contact. That the logo is there suggests that membershipdirector believes that you have a valid premium membership.

What's the bug, and what's the fix?

Can you please replace the Quote tags in your earlier post with Code tags?

There is no problem - they are the same. In server jobs there are no data types. So a comparison tests each operand to determine whether or not they are numeric. If they are, a numeric comparison is performed - if not, a string comparison is performed. To force a string (or numeric) comparison use t...

Like any other activity, the properties of a User Variables activity are available only downstream of that activity.

I would prefer small routines, one for each test, maybe in a category called Test. More modular. Transforms can not be called from DataStage BASIC. SDK and supplied routines are not cataloged with a "DSU." prefix - they are cataloged with "DSX." prefix and wholly upper-case names.

Looks like it's fixed already - the Premium Member logo appears beside your post.

Just read about it here - the 800lb gorilla seems set to put on some weight!

Inspect something whose status is not likely to have changed since the project was created. ls -lc EXAMPLE1.SOURCE is a good candidate.

Initialize svCount to @PARTITIONNUM

Derive svCount as svCount + @NUMPARTITIONS

Derive column (or svRow) as svCount