DSXchange

Trivial in a Server job as well. No looping required.

You need something to drive out the last group change and a known "EOD" record will allow that. This capability will be built natively into "a future" (the next?) release.

All jobs? Only jobs with a Transformer? Just you? Everyone? Always or sometimes?

They shouldn't be so stingy with their undo space.

Please mark your post as Resolved using the button at the top of the page.

After-job routine, check filesize, call DSLogFatal() if non-empty.

Why not tell us what you saw when you ran the job, what columns were included in the output? That should go a long ways todays answering your question. Then mix it up, re-run and re-see.

OK... teeth pulling time... let's start over. :? What does your job design look like now? Did you get rid of the Sequential File stage as noted in the blog entry I linked you to? If not, do so now and then try it again. If it continues to fail, post all of these same details again, down to the setti...

Then they didn't increase it enough.

How big is your flat file? What kind of "load" are you doing?

Your "most of the time" statement, is that just for our understanding or is that an issue? Assuming the former. :? How many rows are in your source data? Lookup / target table? What kind of lookup? Why the 'order by', it will definitely have a performance impact but may not in fact be nece...

Talk to your DBA. They may need to increase that tablespace or you may need to commit more often. Or perhaps just wait and try again.

As noted, at the very least your XML document seems to be invalid. Get a corrected one from the source and try again. Did you open it in IE?

Hence my question.

Your sources need to be 'local' to the DataStage server, be that truly on the server or NFS mounted so that it appears that way. As noted, get your limits changed so it can be moved properly.

And no, the Sequence job level checkpointing is at that level, the job level. Record level 'checkpointing' you have to build in, as noted.

There is no native Windows command for that, however you should have the MKS Toolkit installed and thus access to UNIX commands like split. You can also find utilities people have written for Windows that cut files up, something called 'Chainsaw' springs to mind, but it has been years since I've use...