I've seen different flavors of things over the years - bugs in different
shells (for instance C shell vs K shell), etc.
stty settings may come into play. There isn't one pat answer I can give you
in this forum.
The simplest thing you can try to see if the problem lies in this area is
to replace the 'exec udt' with 'udt' - possibly followed by 'exit' to
close the user's session when udt exits.
You will have more processes on the system (users shell plus udt process),
but that generally is not a big issue.
Happy hunting.
Wally Terhune
U2 Support Architect
IBM Information Management
4700 South Syracuse Street, Denver, CO 80237
Tel: 303.773.7969
Fax: 303.773.5915
[EMAIL PROTECTED]
"Noah Hart"
<[EMAIL PROTECTED]
om> To
Sent by: <[email protected]>
[EMAIL PROTECTED] cc
stserver.u2ug.org
Subject
RE: [U2] Orphan record locks
01/23/2007 09:34
AM
Please respond to
[EMAIL PROTECTED]
er.u2ug.org
Wally,
I am not a unix guru, can you give simple instructions how to
accomplish this, or direct me to the manual where I can read more about
this?
FYI, we do run via a shell script that ultimately runs 'exec udt'
Thanks,
Noah
-----Original Message-----
From: Wally Terhune
On UniData/UNIX, if you have your environment set up so that a
disconnected
telnet session properly passes a hangup signal to the udt process, udt
will
catch that signal and exit, releasing locks and licenses. Sometimes
there
is a difference in whether your login script runs udt directly or runs
'exec udt'.
The udt process holding these locks is likely still alive.
If the process is killed with a hard signal (like -9), the UniData
cleanupd
and smm processes work together to release locks and licenses for the
process that has disappeared from the system.
There is no reason to have orphaned database process or locks from a
telnet
disconnect.
Wally Terhune
U2 Support Architect
IBM Information Management
4700 South Syracuse Street, Denver, CO 80237
Tel: 303.773.7969
Fax: 303.773.5915
[EMAIL PROTECTED]
-----Original Message-----
From: Noah Hart
Sent: Friday, January 19, 2007 9:49 AM
To: '[email protected]'
Subject: [U2] Orphan record locks
CONFIGURATION: Unidata 6.1; Solaris 5.7
BACKGROUND: Last week I noticed that a process had been holding a
readlock for 4 days.
12 kristin DIS-CHK-HOLD LOCK*B00332 09:55:30 Dec 15
2006
13 mariap CORR-MASTER UPD-MEM-INFO*1 11:17:58 Dec 11
2006
14 mariap MEMBER UPD-MEM-INFO*1 11:17:58 Dec 11
2006
The operator was no longed logged into our application, and told me that
last week her computer crashed.
I called our application software provider, and was told that when a U2
telnet session is terminated while a process holds a read lock, the lock
is not released.
QUESTION: Is this true? Is there any way to change this behavoir.
Regards,
Noah Hart
Sr. IT Analyst
Lipman Insurance Administrators, Inc.
CONFIDENTIALITY NOTICE:
This message may contain confidential and/or privileged information. If you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose, or take any action based on this message or
any information herein. If you have received this message in error, please
advise the sender immediately by reply e-mail and delete this message.
Thank you for your cooperation.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
[demime 1.01d removed an attachment of type image/gif which had a name of
graycol.gif]
[demime 1.01d removed an attachment of type image/gif which had a name of
pic07425.gif]
[demime 1.01d removed an attachment of type image/gif which had a name of
ecblank.gif]
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
