DSXchange

...are you still in 7.x ? The MQ Plugin isn't as flexible here, but with the 8.x MQ Connector, you can set the "Correlation ID"....this is a property in the MQ header that allows an application to logically group messages together..... That might be an option for you, if you are on release...

I can't remember the exact numbers and internals, but there are multiple buffers created. I'll try to dig up some tests I did on this and let you know.... ...bottom line --- there is a point where you will max out, with little alternative in EE except to write the chunks out independently. I've done...

...or alternatively you could also just make sure that the value for that column on that row is truly "null"...the default is to not create the element tag....

...of course, it's strange that the receiving application cares.....it should be able to handle empty elements.

Ernie

This was it. On most platforms the problem was resolved in 8.1, but it doesn't surprise me if it still pops up. This issue impacted WSPack in all places and JavaPack in all places, and the env variables, while "similar" on all platforms, are not identical. To future searchers, check with y...

It's apparently supposed to go out and find all the various appropriate logs for you too...

Curious --- how big is the machine that you are using for your DataStage engine? How many cpu's? How much real memory? Are your development boxes and production boxes the same size? Is it dedicated to DataStage primarily, or running many other apps? We've talked about benchmarks in various threads, ...

Be sure you have aggregation as one of the checked options in the XMLOutput Stage, and try making one of the lowest elements (such as FriendName your repetition element (key).

Ernie

Does the Service work successfully outside of DataStage?

Now you are treading into deeper water. Complex flat files (with occurs, etc.) are handled in a more proprietary way by all the tools out there. Things aren't as standard. I'm sure it can still be done, but now you probably are going to need to have some deeper experience with the CFF stage and its ...

Can you describe more what you mean by a 'group'. There are varuous things you can do that might be described as grouping.

All the solutions are the same thing --- albeit with perhaps a few more steps in some cases than others..... Find something (DataStage?) to read the xml metadata from the other tool. Manipulate that metadata and create whatever other file type that you are most comfortable with..... study a .dsx.......

FastTrack will help you create a source to target mapping, which then could lead to the generation of a DataStage Job....and it can import spreadsheets that already have source/target mappings....but that won't help you with the pure table definitions.... IBM Services has tools that can assist with ...

Could be a lot of things....Craig's question above is critical ---- has this particular Job as a service ever worked? Quite often this pipe error occurs when an initializing Job instance is trying to start up, and it times out before being able to contact the ASBAgent........try increasing the timeo...

DataStage Server "comes along for the ride" with DataStage Enterprise Edition (Parallel)...so, yes....your existing DataStage Server Jobs will import, work and operate just fine, as they do today. When and where you need parallel performance, you can build parallel jobs and optionally use ...

Use the one that is most complete. The metadata importer, in my experience, is not going to scan beyond the initial instance of each node tree..... That's why you need to use a document that has "all" possibible nodes fully populated. The best way to do that is to have the xsd and "ge...