I disagree. Port Status is a good option for determining what the state of a process is if you are on the proper release of the database. We are working on uv 10.1.11 and are not having any problems with PORT.STATUS. You can only have one user in PORT.STATUS at a time, but it works just fine in our environment. (aix 5/2/2UV 10.1.11)
Tom Dodds [EMAIL PROTECTED] 708-234-9608 Office 630-235-2975 Cell -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, October 04, 2006 5:27 PM To: [email protected] Subject: RE: [U2] PORT.STATUS bug? So if port.status is not a good option for determining what state a process is in, what do people turn to? -------------- Original message -------------- From: "Stevenson, Charles" <[EMAIL PROTECTED]> > I saw something similar with telnet sessions, not phantoms a few years > ago. > Also HP, but UV 9.6.2.6, HPUX 11, August 2002. > > I hit it with PORT.STATUS...LAYER.STACK but I don't think I've hit it > anywhere else. At least I've never pinned it. > It happened when I was trying to collect stats on what we spent our time > on. I ran a job that repeatedly executed PORT.STATUS LAYER.STACK > (consistent with what Asvin says) and telnet sessions began hanging > right & left. > > It was only when I used the LAYER.STACK option and I never saw a problem > with phantoms, although several were running, only telnet. I did not > see the ":nanosleep: Interrupted system call" error message. > > 10.1.14 release notes says: > > Issue 7659 > If one UniVerse process was executing a SELECT statement > against a file, and a different UniVerse process was > executing the PORT.STATUS command, the process selecting > the file may have received an error message similar to > the following: > > "nanosleep: Interrupted system call" > > This problem was unique to the HP platform and has been fixed. > > There are 4 other notes that mention PORT.STATUS. > > I did not recognize 7659 as my issue, but reading both of your posts, it > looks like maybe it is. > I am at UV 10.0.16 at present. > > Chuck Stevenson > > > > From: [EMAIL PROTECTED] > > > > this is a known issue in some versions of Universe. It is > > fixed at one of the 10.1.nnn releases - not sure which. From > > our experience, it seems to only occur when you have a > > program that is sleeping, and you run PORT.STATUS more than > > once without any appreciable gap in between. > > > > Sent by:[EMAIL PROTECTED] > > > > HPUX 11 > > UV10.1.8 > > > > Has anyone had any problems with PORT.STATUS causing phantom > > jobs to hang? > > We have background jobs that, every once in a while, will > > hang. When > > looking at the output from PORT.STATUS the last command is > > always some > > simple EXECUTE. For example, the batch job EXECUTES a SH -C "ls > > ./dir/whatever*" and, seemingly, fails to return. > > > > I did see the following in the PH record > > ":nanosleep: Interrupted system call" > > > > How does PORT.STATUS work internally anywho? > > > > Thanks, > > > > Scott > ------- > 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/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
