Do you mean no error on the screen, in the error logs, or in the _PH_ file for the phantom process?
The _PH_ file is the best place to look first for any notifications. We run a number of these that can run for over 8 hours overnight. Generally the only two problems we have that cause it to stop are the backup process locking a file that the phantom process is trying to write to - this is in the _PH_ file. The second is the server (or just UniData). You should be able to see this in the server logs. (on NT you can quickly check the last boot time with "net statistics server | more" Hth Colin Alfke Calgary Currently in sunny LA Celebrity sightings: 1 -----Original Message----- From: Suresh Chappidi [mailto:[EMAIL PROTECTED] Hi, We are running into a problem when running a phantom process in Unidata. The process seems to stop after 2 hours 40 minutes approximately without giving any error. I'm wondering if any of you have any ideas on how to make the process run without stopping. Thanks in advance for all your help! Regards, Suresh ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
