Phantom Output File: incomplete <response> file

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
computexweb
Premium Member
Premium Member
Posts: 2
Joined: Wed May 02, 2007 5:53 am

Phantom Output File: incomplete <response> file

Post by computexweb »

My job does not run and does not give me a clue as to why it does nothing. The job was running fine until I added additional outputs to the Switch control in the job.

Note: I increased the outputs from 9 to 35 since read a Switch could have up to 128 outputs.

The job doesn't do anything anymore; it just completes with a status of OK. I did notice I now get the following message in my log though:

Contents of phantom output file =>
DataStage Job 240 Phantom 24966
incomplete <response> element
DataStage Phantom Finished.

I'm not sure what "incomplete <response> element" is suppose to tell me???

Has anyone run into a similar problem, or have any idea what I might need to do to resolve this issue?

JOB DESCRIPTION:

Job has 2 Dataset inputs that go into a Join and then a Switch and finally 35 Datasets (see below)

DS_IN1 => => DS_OUT1
JOIN => SWITCH => DS_OUT2
DS_IN2 => => DS_OUT3


Any assistance/ideas would be greatly appreciated.

Many thanks!

Computexweb
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

It looks like your selector doesn't account for all possible data values.

What selector mode have you specified? What have you put into your "not found" condition?
computexweb
Premium Member
Premium Member
Posts: 2
Joined: Wed May 02, 2007 5:53 am

Post by computexweb »

Thanks for your reply. T

- My selector mode is: User-defined Mapping

Note: the input has a selector field that I use to map to the various values I've specified in the User-defined Mapping CASE statements.

- My Not Found condition is currently set to "Output".

Note: I have a reject link and a Sequential File waiting to catch the rejects. However, there should not be any since I specified every possible case in the User-defined Mapping.

More Info:

- A typical CASE condition would look like this: 012121 = 0

- The selector field has the following datatype: Char(6)

- There are 95 columns coming in on the input link of the Switch; and each of the 35 output links has around 15 columns.

- The job's input dataset has approximately 3 million rows.
Post Reply