DSXchange

There's no "OSH" in a Server job.

BTW, all caps is considered SHOUTING. Please don't shout.

Don't know DB2 but is that normal for a timestamp? Are they some kind of offset? Curious what values those three should convert to.

What about leaving it as a string (not a date) with the string in 'yyyy-mm-dd' format and then taking the minimum of that? That or an integer in 'yyyymmdd' format.

Then this one should be marked as Resolved using the button at the top of the stage.

Never said it would be simple or that was the only answer. And I did mention the need for an account-based hashed file. And yes, you may prefer to use SQL.

They're decimal fields, set them to zero when null.

You need to set the field as Nullable=Yes in the Aggregator and then use the handle_null() function in the Modify stage for each of the fields. They can be set back to Nullable=No in the Modify stage.

First post here:

viewtopic.php?t=130757

Oddly enough... 'count'.

igorbmartins wrote:But if I put with the ENTIRE partitioning my record would multiply by 4 because I have 4 nodes.

Ummm... no. Re-read Ray's first reply.

... and then pad it yourself.

You'd have to change the partitioning to 'Entire', it would seem.

For the first warning, use the 'Preserve type' option. For the second, you'll need to do what the error says and handle_null in a downstream modify stage.

You'll have a "Procedure status to link" option in 8.x that would help with that but I don't believe it is available for 7.