I do the same but every time you login.
Louis
'
- Original Message -
From: [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Saturday, August 06, 2005 12:43 AM
Subject: Re: [U2] File name of the RECORDS which are listed in LIST.READU
output
: In a message dated 8/4/2005 1:56:49
Louis Windsor [EMAIL PROTECTED] wrote on 08/06/2005 04:12:35 AM:
I do the same but every time you login.
The context of this is a bit blurred due to over-quoting, so I just want
to make sure I understood correctly. Does the same mean going through
all file references in an account and
WARNING - LONG STORY
I'm sorry Tim - I told a lie!
The first User to login for the day causes the inode table to be refreshed.
The logic is built in (through subroutines) called by ALL programs that
update
files. Should a lock occur the subroutine rerefreshes before notifying
the User.
The
I use a (borrowed) program that relies on GETREADU() (Unidata)
GETREADU
Syntax
GETREADU()
Description
The UniBasic GETREADU function returns a dynamic array containing
information about all
records that have been locked by any UniBasic or ECL command that updates
any record.
This command
Unfortunately this is not in Universe.
- Original Message -
From: Jon Wells [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Friday, August 05, 2005 7:59 AM
Subject: Re: [U2] File name of the RECORDS which are listed in LIST.READU
output
I use a (borrowed) program that relies
In a message dated 8/4/2005 1:56:49 AM Pacific Daylight Time,
[EMAIL PROTECTED] writes:
2. Write a simple program to build your own register of inode numbers. You
can do this with a loop based on the following
I take Martin's idea one step further.
I have a phantom, that every night rebuilds
on a RedHat 8.0 the following find commando will work :
find /path_to_data/ -inum inode
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Pankaj Gupta04
Sent: Thursday, August 04, 2005 8:03 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] File name of
I have some records which are locked. The Item ID is same. Can I get the
database filename to which the records belong?
The locking tables use device and inode numbers and have no reference to the
file name.
Two easy solutions...
1. Run ACCOUNT.FILE.STATS and look up the inode number in the
That's what I did here and it works quite nicely. I have
a nightly process that (re)builds a registry of all file with
their device and inode number. Then I shelled the 'LIST.READU'
command to produce a locks listing showing the file name for
each locked item. Quite helpful for us here.
Barry
Doesn't LIST.READU DETAIL give you the file name?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Pankaj Gupta04
Sent: Thursday, August 04, 2005 2:03 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] File name of the RECORDS which are listed in LIST.READU
LIST.READU EVERY will show you what you should need regarding locks.
Note the INODE number then shell to Unix/Linux and do ls -li | grep
[inode] this will give you a file name.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael Roberts
Sent:
DETAIL does not appear to be an available option, at least on uv
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Michael Roberts
Sent: Thursday, August 04, 2005 09:07 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] File name of the RECORDS which are
Not on UV. UV 10.1.6 Pick flavor. It just returns a few more numbers.
Device Inode Netnode Userno Lmode Pid Login Id
Item-ID.
63029562 528980 56380 1 RU 9156 login_1
020750*02#001*18#13516
630265603567660 42 2 RU 6993 login_2
UV 10.1.7 on AIX 5.2.2 The LIST.READU DETAIL returns:
LIST.READU DETAIL
Active Record Locks:
Device Inode Netnode Userno Lmode Pid Login Id
Item-ID.
2490371 255640 34 17 RU 08644 karen-sa 75
2490371 452720106 18 RU 35872 cp-tracy
14 matches
Mail list logo
