David, I don't currently use a READU on my UD system to "LOCK" phantoms, but I use it on UniVerse and it works unless you do an "End Task" on the UVSH process from the windows console .. Then you have to do some syntax of the UNLOCK command to fix things .. On my AIX machine, I use the listuser and ps commands to see if a phantom is actually still running .. This has it's quirks too ..
That being said, I tested a small phantom process and had it do a "LOCK 1" command and had it shutdown 3 ways without explicitly running a CLEAR.LOCKS command 1) normal exit (STOP) 2) deleteuser 3) input required In all three cases, the LOCK went away .. I may start using this as a way to check that my phantoms are running .. I know that UniVerse has similar LOCK syntax .. Does anyone else out there have any experience with LOCK and phantoms on UV? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David Wolverton Sent: Wednesday, December 28, 2005 12:56 PM To: [email protected] Subject: [U2] [UD] BASIC "LOCK"s Since we don't have Semaphore-like COMMON structures, I was going to use the BASIC "LOCK" to know that a Phantom was running -- the lock missing would tell me to start the process. HOWEVER, if the phantom 'dies' - the documentation makes it read as if the LOCK will stay engaged -- does anyone have practical knowledge if a phantom falling over 'implies' an ECL QUIT? I know I could use READU, but my understanding is that BASIC LOCKs use far fewer resources to test - and as I will add a test for the Phantom being 'up' in several common routines, I don't want to cause extra bottlenecks. (I really wish we had cross-process COMMON for things like this!) Thanks - David W. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
