DSXchange

Yes... what is the C in your FF?

Use the Execute Command stage to run 'orchadmin' with the option that deletes datasets. Point it at the '.ds' file.

Me, I don't use it and personally wouldn't bother with the FTP stage even if you do manage to get things dumped to a sequential file. Too many... quirks.

Out of curiousity, what exactly are you passing in? If it is already 'in the environment' the job can access it without needing to pass anything when invoking the job.

vmcburney wrote:This is fixed in DataStage 8.5

Now, that is interesting news. Any idea on the nature, the how of the fix?

Hopefully you found the button (that looks like it launches IE, or at least it did in 7.x) in the Designer that builds a 'job report' for the current job, including a picture of the canvas. As noted, you can also generate it at the command line.

With Fork() 'space' means 'memory'. You runned out.

This I assume.

There's too many variables, a file that's "too large" on my system may process fine on yours - and all that matters is your limit, not mine. About all I can suggest is you write something to generate test XML files of varying sizes and see how big you can push it until a reader job falls o...

Bah... as if everything is in the proper forum.

Fully path the dsjob command.

Do it based on the value of the key change column. Once you run some data through and see what it looks like, the 'how' will be obvious.

It's all automatic, you shouldn't have to do anything to get that to happen. Are you having an issue or just asking before you get started?

If you really want to ask them something, how about asking them for their recommendation as to a 'best practice' for processing huge XML files in DataStage? I'd be curious what they say.