Phantom and Zombie process

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
ds_is_fun
Premium Member
Premium Member
Posts: 194
Joined: Fri Jan 07, 2005 12:00 pm

Phantom and Zombie process

Post by ds_is_fun »

I'd appreciate if someone can briefly tell me about phantom and zombie process in Datastage. Thanks!
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Phantom process is a DataStage internal process. Thats the high level definition. A zombie is a process from Freddy Vs. Jason. Just messing with ya. Click here
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
narasimha
Charter Member
Charter Member
Posts: 1236
Joined: Fri Oct 22, 2004 8:59 am
Location: Staten Island, NY

Post by narasimha »

To add to the list, a quote from Kenneth's post
kcbland wrote:Phantom errors occur when DS BASIC errors send messges to stdout, and since Server jobs don't have a screen component those messages are caught and return as "phantom" errors. Phantom is just the name of the background program used in DS Server to manage a task.

The most common messages are variable not assigned a value zero used, illegal datatype, abnormal termination, and non-numeric value.
DSguru2B wrote:A zombie is a process from Freddy Vs. Jason
Thats humorous. :lol:
Narasimha Kade

Finding answers is simple, all you need to do is come up with the correct questions.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

"Phantom" is DataStage terminology for "background process". You can trace the history of this usage back through UniVerse, Prime INFORMATION, PRIMOS, back to Pick O/S.

"Zombie" is a UNIX term, describing a process - typically a background process - that is prevented from being killed (or even from logging out) because it is unable to notify its parent process - probably because that parent process no longer exists. So even though you can send it a kill signal, it can not log out because it cannot notify its parent.
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