DSXchange

Moved this one, took care of the extras.

5.10626668035311

Still hoping I can cash them in for a pony.

Me, I'd need the last two rows explained. Up to that point it's just a running total and then suddenly... it's not.

Always best to spell your transformation requirements out in words. This rather than forcing people to puzzle them out.

'Processed individually' confirms my fear - they cannot be spilt up as a post activity - they have to be built in those smaller pieces so they are viable XML files. I had to do something like this "back in the day" when producing search results for Google, they imposed a limit on the file ...

Not really sure why you felt the need to repeat all that nor how DataStage would have any clue what size the file will be once it has been zipped. And all I meant was the fact that an XML file cannot simply be chopped up into pieces and still have those pieces usable as individual files. So I was as...

qt_ky wrote:Your job type says server but you mention the Copy stage.

Corrected.

Will these pieces be put back together before being processed? If they'll be processed individually then you can't simply "split" them.

I meant for both the source and target... still the same answer?

What are the charactersets involved?

Since you've yet to start a post here, let's get some vitals from you - DataStage version and Server O/S in particular. I'd also be curious what error you had while importing. And not really sure what you mean by your sentence. I for one would appreciate it if you could rephrase it. while importing ...

Huh... always thought it was best to use the xsd rather than the actual file for metadata as the file may not have all occurrences of elements in it. I guess you solve that with asking for a 'formal instance' of the file?

Did you look up that error code? Seems a strange one to be coming from a bulk load, are you certain you have all of your metadata correct?

Note that I'm not familiar with DB2 so perhaps it will make more sense to others out there.

Sounds like you're calling this in the 'normal SQL' area. It would need to be in either the before or after SQL (which does not expect a result set) and let the stage do a simple select from some innocuous table to keep it happy. Heck, it could even do something like "where 1=2" to ensure ...

olgc - let's keep your question in one place rather than repeating it when you find a similar topic from the past. This one is much more 'on topic' so I removed your post in the other thread.

Thanks.