DSXchange

Hello guys,
we have a strange problem with a parallel job.
The job working fine in version 8.1 and in the new version of datastage (11.3) the job don'0t work properly.

This is the job structure:


There are two strange things:

1) Joi_QM: When checking operator: Operator of type "APT_JoinSubOperatorNC": will partition despite the
preserve-partitioning flag on the data set on input port 0.

2) the job endend in status finished(see log) but if we look at the job log there is a strange messagge

'Contents of phantom output file
DataStage Job 263 Phantom 15426
incomplete <response> element
DataStage Phantom Finished.

and if we look the monitor we see that there is some stage in status stopped



Any suggestions ?
Thanks in advance.

Luca

any ideas?
I try to create a copy of a job but the problem still here.

I'm no longer able to see your images where I could before... are they still on that hosting site? Have you involved your official support provider yet?

And just to play Devil's Advocate, it probably isn't really "working fine" in your older version, all you know is that it just wasn't blowing up. Unless they've introduced a new bug (hence the question about support) then what these typically turn out to be is a loophole or bug in the old version you have inadvertently taken advantage of and which they've... plugged / fixed.

Edited to add: okay, images work from home but not on my trusty government issue laptop, so... another blocked site. Yay.

I would address the first issue...the stop happens because after the first error happens a signal is send to the rest of the processes to stop....

Search in this forum the message, it has been discussed several times
"will partition despite the preserve-partitioning flag on the data set on input port 0"

Right, start with that and see where the rest goes.

i have an update: i was able to remove the warning of partitioning.
The job run fine only one/two time and then the phantom error return again.
If i try to re-run the job after the phantom message the job have the same behaviour that i describe in first post (the job end but some stage are in stopped status and phantom error message appears).
That error message doesn't help a lot...