DSXchange

Ah... that's what I was waiting for. Now we know Ken is truly back.

Then this seems to be something you should report to your official support provider, see if it is a known issue.

No worries, you wouldn't want to see my French. :wink: The example helps alot. So... does this problem seem to be coming directly from the Sequential File stage itself or is it being introduced in later processing, say the 'remove duplicates' step you mentioned? I've seen posts about odd problems wi...

Ok, so much for details. [sigh]

What's different about this 'other environment'? As Ray would say, 'Nothing is not the correct answer'.

Affected to? To quote The Princess Bride: You keep using that word. I do not think it means what you think it means. Could you please clarify what exactly you mean by 'affected to' in this context?

You can also script the same thing using dsjob from the command line. FYI.

Right, that UserVariable stage is the key here. It can build a delimited list of 'things' and pass elements from the list, one at a time, to the Start Loop stage. In your case, that list can be a list of all filenames that match your wildcard pattern. Then inside the loop you run your job to process...

There is a function "GetFiscalYear()" under DSRoutine in transformer stage. How can this help us as in this regard. :!: As noted, that is a custom routine someone there either developed or cribbed from somewhere else. We have no idea what it actually does. Double-click on it to answer you...

Regardless of your 'observation' that is not the way to be handling aborted jobs in DataStage. :? As noted, determine the cause of the abort and take steps to prevent it from happening. Proactive, not reactive. If you need help with that, post the nature of the problem here and we'll help you figure...

What's not feasible about it? It's just... tedious.

The dsjob command with the -report option does the same thing, from what I recall, so you could create a batch file to get a list of jobs and then loop through that list to create reports for all of them.

In the Server product, the Sort stage is fine for smaller volumes but I'd stick with either a UNIX command line sort or 3rd party tools for anything... 'large'. What I've seen is the command line sort (properly maxed) gave us around 10x the speed of the stage.

And there are literally tons of books out there on the subject. Go to a site like Amazon where users review the books and browse there. There's also a document we uploaded to Kim Duke's website in his Tips section that covers XML 'Best Practices' in DataStage, well worth anyone's time to go through ...

Custom sql or generated by the stage? Regardless, please post your sql and let us know if you're doing anything 'before' or 'after' in the stage as well. In other words... details. I'd also be curious if you've ever used the DB2 stage before and just this one has a problem or this is your first time...

The rule is - upgrade the server, upgrade the client to match. If you need to connect to two different server versions, install both clients and use the MCM or Multiple Client Manager to switch betwee the two as only one can be 'active' at any given time.

This. And perhaps this as well.