DSXchange

There was absolutely no reason to start a new post for this.

I'm writing a before job routine to read the parameters from the table and pass it on to the datastage job. Regardless of your handle issue (DSJ.ME should work just fine) you need to rethink this whole approach. Before Job is too late to assign parameter values as the job has already started at tha...

So different version, job type... off we go to your own post in the proper forum. For grins, can you detail what exactly your issue is, the error you are facing?

The 'Additional Info' in your post isn't really needed. You should put UNIX in as the OS property as that one indicates what your Server is running. The client is always on Windows.

FYI.

Typically, any "only on my machine" issue is a corruption of the client software. Have you tried completely removing and re-installing them? And by 'completely' I mean down to ensuring all related registry entries and left-over directory structures are gone. And rebooting before the re-ins...

There's no "usually" here, only one answer as one must be loaded before the other... and the relationships between the two should make that answer obvious.

Anyhow your answer confirms indirectly tells me that we will not email. I don't think that indirectly answers anything as Ray, just like all of us here, is just a user of the site and not directly involved in the running of it. I suspect you are correct but maybe we can get a more 'official' answer...

Well... we did tell you that wasn't the issue.

No, you can't have a dot in the actual Invocation ID value. Why not replace the second dot with something like an underscore?

Volume, I assume... and that it ran over the Fall Over Dead Limit. Unless you are ordering the data by your grouping keys and asserting that in the Aggregator? That would render that fairly moot.

Got nothing to do with EOL, as noted it is strictly an incompatible version issue.

I would imagine the copy stage would be optimized out of the runtime job unless you forced it to be kept... and as noted, there's no need for that.

Hard to say without more details but it seems your XPath expressions are incorrect or you're not building the chunks appropriately. I did a crap-ton of this back in the day and it can work just fine if done properly. Unless Ernie has a better idea, why not start by showing us the XPath Expressions y...

The only way to answer those questions would be to try both ways on your system with your data. Then you'll know.

mgsteiner wrote:I can relate and have together every Header and Content tags, but every group is separated with the <message xmlns...> tag

Use the option to create them as 'chunks', headerless segments.