Hi David
Just a thought, but you could change your approach to this and use some
newer technologies such as MQ or web services using connection pooling.
These are designed to handle issues like you have mentioned better than the
phantom process.
Regards
David Jordan
Managing Consultant
[EMAIL
Dear David,
Try setting the NOTIFY ON in the login proc. Whats happening is that, when
the phantom is done, its needs to tell someone, until thats is done the
zombie process will there.
Regards,
Guna
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
We had the same problem with a scheduling module. We found that if the
module CHAINed itself after a given period of time (like an hour) the
zombies went south, following the deceased parent.
On 11/5/07, Gunasegeran Pasupathy [EMAIL PROTECTED] wrote:
Dear David,
Try setting the NOTIFY ON in
David,
Easy fix: EXECUTE JOBS CAPTURING JUNK
Put this in your code prior to the PHANTOM launching code. It will
reap any dead child processes (zombies), that may be hanging around.
Kevin M. Sproule
Sr. Technical Consultant
AFS Technologies, Inc.
2141 E. Highland Ave, Ste. 100
Phoenix,
David
NOTIFY ON and also - as this is a scheduler PHANTOM - change any long SLEEP
into smaller chunks of SLEEPS - e.g.
Instead of SLEEP 36000 try
FOR delay = 1 to 100; SLEEO 360; NEXT delay
There were two issues there (from my memory) - the first was that a BREAK on
a foreground process that
