of your blocking wait?
George
-Original Message-
From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-
boun...@listserver.u2ug.org] On Behalf Of Dan McGrath
Sent: Monday, December 07, 2009 11:11 PM
To: U2 Users List
Subject: Re: [U2] PORT.STATUS affecting program
Thanks Wally
or was this all fixed as part of that?
Regards,
Dan
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wally Terhune
Sent: Tuesday, 8 December 2009 10:59 AM
To: U2 Users List
Subject: Re: [U2] PORT.STATUS affecting program
Dan,
I've seen something similar with very same port.status options where
PORT.STATUS seemed to cause other uv telnet sessions to drop..
Maybe UV10.0 or earlier. I'm still not clear on whether you are ud or uv.
It was during my most intensive use of the command ever. I did not pursue
the bug,
Thanks again Wally.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wally Terhune
Sent: Wednesday, 9 December 2009 12:44 AM
To: U2 Users List
Subject: Re: [U2] PORT.STATUS affecting program
Since your process
Assuming this is UniData, (though you don't specify db, version or os), you may
be encountering a signal issue that is fixed at 7.2.3. From the readme:
Issue 11687 - Problem Description
UniData -- When using the PORT.STATUS command with the PID option
to review the CALL.STACK or another udt
Hi,
The option keywords for PORT.STATUS are only in the UV account by default.
You can copy them to other accounts to get PORT.STATUS to work.
Martin Phillips
Ladybridge Systems Ltd
17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB
+44-(0)1604-709200
---
u2-users mailing list
Copy VOC item PID from uv account?
Mark
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Results
Sent: Tuesday, October 21, 2008 5:55 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] PORT.STATUS
REPOSTED FOR NON-MEMBER ADDRESS: braini [EMAIL PROTECTED]
, September 03, 2008 10:04 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] port.status
OK, I ignored it the first time, but if this is going to keep rolling then I
need to jump in with a correction before people assume it must be correct.
This is not the 'sticky' bit. The purpose of the sticky
] On Behalf Of Ken Wallis
Sent: Wednesday, September 03, 2008 10:04 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] port.status
OK, I ignored it the first time, but if this is going to keep rolling then
I
need to jump in with a correction before people assume it must be correct
, September 4, 2008 11:42 am
Subject: Re: [U2] port.status
To: u2-users@listserver.u2ug.org
that was my point, easier to remember that +s is that sticky is
easier to
remember or associate with +s. Also, unless i don't understand
what an OS
is, this program (port.status) is not part of the OS
, September 04, 2008 12:56 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] port.status
To all.
thanks for your suggestions. there was something hincky with aix and
universe. server had been setup in July. Universe added at the same
time.Then in August, we imported our files.And started
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lloyd Cottrell
Sent: Friday, 5 September 2008 12:59 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] port.status
that was my point, easier to remember that +s is that sticky is easier to
remember or associate with +s. Also, unless i don't
Sep 03 12:13 (rogergxp.ezp.pri)
There are currently 1 users logged on the system.
- Original Message -
From: jpb-u2ug
Date: Tuesday, September 2, 2008 7:07 pm
Subject: RE: [U2] port.status
To: u2-users@listserver.u2ug.org
Are you running it from the administrators account
i've found that you need to flip on the sticky bit on the list_readu program
to fix this problem, which makes it run as root
On Tue, Sep 2, 2008 at 2:49 PM, [EMAIL PROTECTED] wrote:
New install of Universe 10.2.4
PORT.STATUS
There are no uniVerse sessions that match the specified conditions.
Subject: Re: [U2] port.status
i've found that you need to flip on the sticky bit on the list_readu
program
to fix this problem, which makes it run as root
On Tue, Sep 2, 2008 at 2:49 PM, [EMAIL PROTECTED] wrote:
New install of Universe 10.2.4
PORT.STATUS
There are no uniVerse sessions that match
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of JPB-U2UG
Sent: Thursday, 4 September 2008 11:24 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] port.status
Yes, but it should have already been set. If you want it to work with
everyone then set the sticky bit in the /usr
Are you running it from the administrators account?
Jerry Banker
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, September 02, 2008 3:49 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] port.status
New install of
Whate else do people turn to?
SYSTEM(9001) is a little different tool, but at
least tangential to the
current discussion.
There is GET.USERS which calls the SYSTEM(1302).
SYSTEM(1302) isn't supported by IBM but GET.USERS is.
CALL
!GET.USERS(PI.USERS,MAX.PI.USERS,SYS.USERS,INFO,CODE)
Scott,
We run AIX 5.3 and UniData 6.1.17-64 and we have the same problem with
phantoms.
What we did is create a baby sitter that stops and starts our phantoms every
three hours.
In our case is not related to PORT.STATUS, just phantoms hanging. In our
case PORT.STATUS is based of the
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
From: [EMAIL PROTECTED]
So if port.status is not a good option for determining what
state a process is in, what do people turn to?
Oh, I still use port.status, including LAYER.STACK, but only from tcl to
research a specific issue as it is happening.
I haven't tried the mass
: 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
Hi Ang,
Assuming that you are using Universe
The PORT.STATUS command is usually locked by a semaphore. You can check the
status of semaphores by using the SEMAPHORE.STATUS command (nomrally only
available in the uv account)
To unlock the PORT.STATUS semaphore:
UNLOCK PSTATLOCK SEMAPHORE
Dear Asvin,
Thanks for providing the solution. The problem has solved . Thanks
Regards
-Original Message-
From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]
Sent: Wednesday, 04 August, 2004 6:38 PM
To: [EMAIL PROTECTED]
Subject: Memo: Re: [U2] PORT.STATUS
24 matches
Mail list logo
