DSXchange

I'm prepared to bet that it can.

Document your precise requirement.

Premium membership is the means by which DSXchange is kept alive; it is used to pay the hosting and bandwidth costs of the site. I do not propose to undermine that. Premium membership is not expensive - less than 30c (Rs 11) per day. Don't delay. You have already made 119 posts, so you can't claim ...

People searching this thread in future might also contemplate investigating the Distributed Transaction stage.

I've moved on from that client since then. From memory, 3(a) was simply SELECT COUNT(*) FROM TABLE for both source and target, add artificial key ('X'), join and compare. 3(b) was very similar only it was SELECT * FROM TABLE ORDER BY keycolumn (with RCP enabled) and run through Checksum stages befor...

Looks like James did your thinking for you.

Specify Unicode VarChar(20) rather than unbounded non-Unicode VarChar in the stage that threw the error.

Of course there is, and you've nailed it with the word "generate". Generate all the months (not just the missing ones) and (outer) join. Then pivot.

I don't think there's any "automatic" mechanism here. The granularity is too fine to use Find. Others will recommend search and replace in a DSX file, but you would need to be so, so careful not to change anything incorrectly.

We don't do urgent here. DSXchange is an all-volunteer site whose members post as and when (and if) they can. If you need "urgent" sign up with your official support provider for priority service and learn just how much "urgent" is worth. Look at Web Services Transformer stage.

1) Yes.
2) Entire project. Or maybe entire server. Not individual hashed file.

You DO need either a UNIX script or DataStage routine, unless you construct everything into a sequence that executes the relevant UNIX commands in a set of Execute Command activities.

Be aware that, whichever approach you use, this is a non-trivial exercise. The job log for each job is in a separate database table (assuming you're using the recommended RTLogging).

Sounds like you need to invest in some training, or at least in some time reading the manual. Match and clerical cutoffs serve different purposes. Please research that and post your findings back here. Yes, I do know the answer, but my philosophy is to help you to help yourself. If I simply give you...

Add null handling to the Sequential File stage. For example add a Null Field Value property to the Format tab.

You know and I know that NULL will never be sent there, but the operator checker in DataStage doesn't, so we play its game and add null handling.

Did you really have copy | cp in your command?

Think about what this is doing!