Datastage 7.1 Server Job hangs when reading a named pipe.

[maddog]

I have a shell script that writes a named pipe. I have a Server Job to read the named pipe. The server job has the performance options to enable row buffering checked , the Inter process radio button selected, and the Timeout(sec) parameter is set to 60. The shell script is not started by a before job routine (there are no before or after rountines) but is started before the Datastage server job is run. The stage that reads the named pipe has the "Stage uses named pipes" box checked. When run the stage is run the log shows the following message as the last line: BIZDR3ExSalS120..ConvUoMandPipe: DSD.StageRun Active stage starting, tracemode = 0. The DS job does not time out. The DS job does not read the named pipe. It just hangs. Any ideas?

[ray.wurlod]

Welcome aboard. :D

What is your timeout setting? How do you know it doesn't time out?

[maddog]

Timeout set to 60. I expected the job to abort when limit was reached. It did not. Why doesn't it read the named pipe? Is there another time out setting such as in the read stage on the format tab where the settings:

Wait for writer timeout = 0
Read timeout = 0

Should these be set as well?

[ray.wurlod]

Certainly read timeout should be non-zero. Zero means wait forever. Is anything writing into the other end of the pipe?

[maddog]

The script that writes the pipe is working. If I issue a Unix command that reads the pipe(e.g. wc), the pipe is emptied and the script exits with good return.

[chulett]

Silly question, but are you absolutely certain the DataStage job is reading from the same pipe that the shell script is writing to? I also seem to recall something about the pipe needing to be in the Project directory??