Phantom error 10819

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
Prakashs
Participant
Posts: 26
Joined: Mon Jun 06, 2005 5:43 am
Location: Melbourne, Australia

Phantom error 10819

Post by Prakashs »

Any idea what the folowing phantom error is ? I am using Datastage 7.5 EE on Linux.

Contents of phantom output file =>
DataStage Job 298 Phantom 10819
writeSocket() returned 39
Program "DSD.OshMonitor": Line 322, Variable "finished" previously undefined. Zero used.
writeSocket() returned 16
DataStage Phantom Finished.
roy
Participant
Posts: 2598
Joined: Wed Jul 30, 2003 2:05 am
Location: Israel

Post by roy »

Hi,
10819 is not an error code!
this is what's wrong:
writeSocket() returned 39
Program "DSD.OshMonitor": Line 322, Variable "finished" previously undefined. Zero used.
writeSocket() returned 16
it really sound like a support call to me.
you might also need some patch/es regarding your job monitor so check that as well.
(I know solaris needs the patch)

IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.

Search before posting:)

Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Image
Eric
Participant
Posts: 254
Joined: Mon Sep 29, 2003 4:35 am

Post by Eric »

Is the Job Monitor working?
(You will see a message like this if the JobMonApp is not running)

Search the forums ...
Prakashs
Participant
Posts: 26
Joined: Mon Jun 06, 2005 5:43 am
Location: Melbourne, Australia

Post by Prakashs »

Checked the Job Monitor log but there are no recent entries in the log.

There are no messages to state JobMonApp is not running.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

"phantom" is DataStage's term for "background process". 10819 is the process ID (user number) of the process reporting the error. The actual error message suggests what the problem is and a possible underlying reason that writeSocket() failed is that the listener on the other end of the socket (JobMonApp) was not running. Solution seems to be to check whether JobMonApp is running and start it if it isn't.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

That would seem to be a logical conclusion. Currently I have no way to verify it. Get in touch with your support provider, who may be able to source the 9.1 adapter for you.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply