Hi,
I'm trying to write a perl script to find CISAM & PROISAM record locks.
CISAM is no problem, but PRO-ISAM (of course!!) is a problem.
Does anyone know the answer to this....
I use isview to list all open records for PRO-ISAM.
I can work out all the fields apart from the file ID field.
I know that this is made up of the inode & device id from unix.
The inode is no problem as it is the one in unix, but the device ID is not the one from unix (ie the major/minor dev id).
PRO-IV seams to index this too an internal table (at the end of isview).
Example.(end of isview)
device table
next free slot (dev_table[0]) = 0x 6
[ 0] 0x 6
[ 1] 0x4F7FEEAB
[ 2] 0xD5B332F5
[ 3] 0x43A7505B
[ 4] 0x4914B66B
[ 5] 0x1A106C4B
Question.
Does anyone know how to map the 0x4F7FEEAB to a 'file set' or directory path???
Thanks,
Rob
Click the link below to see the new game I'm developing!
7 replies to this topic
#1
Rob Donovan
-
- Admin
-
- 1,652 posts
rob@proivrc.com
- Gender:Male
- Location:Spain
Posted 21 February 2000 - 02:15 PM
#2
Dan Shannon
-
- Members
-
- 374 posts
ProIV Guru
- Gender:Male
- Location:Australia
Posted 21 February 2000 - 04:42 PM
Rob,
Under SCO at least the device ID in the table IS the device's major/minor ID in 2 HEX bytes. For example my output from isview gives
device table
next free slot (dev_table[0]) = 0x 2
[ 0] 0x 2 [ 1] 0x 12A
where 12A gives 2 HEX bytes 01 and 42, which are the major and minor device numbers of the FILESYSTEM not the physical device. The filesystems are defined in /etc/default/filesys under SCO.
In my case the /dev/root filesystem (which is where the files are) is
br--r----- 1 root backup 1, 42 Jul 28 1999 root
Hope this is of some help
Cheers
Dan Shannon
Under SCO at least the device ID in the table IS the device's major/minor ID in 2 HEX bytes. For example my output from isview gives
device table
next free slot (dev_table[0]) = 0x 2
[ 0] 0x 2 [ 1] 0x 12A
where 12A gives 2 HEX bytes 01 and 42, which are the major and minor device numbers of the FILESYSTEM not the physical device. The filesystems are defined in /etc/default/filesys under SCO.
In my case the /dev/root filesystem (which is where the files are) is
br--r----- 1 root backup 1, 42 Jul 28 1999 root
Hope this is of some help
Cheers
Dan Shannon
#3
Rob Donovan
-
- Admin
-
- 1,652 posts
rob@proivrc.com
- Gender:Male
- Location:Spain
Posted 21 February 2000 - 04:51 PM
Hi,
Thanks for that, but we are using DEC UNIX with ADVFS file system and I think that is only applicable if you are using a UFS file system (???)
Rob
Thanks for that, but we are using DEC UNIX with ADVFS file system and I think that is only applicable if you are using a UFS file system (???)
Rob
#4
Guest_Doctor PRO IV_*
Guest_Doctor PRO IV_*
-
- Guests
Posted 10 May 2000 - 03:26 PM
Rob
It is just as applicable to ADVFS
The usual way to retrieve the device major and minor
numbers and the inode is to use the stat() and fstat()
routines
These system calls work the same way and return the same information on ADVFS. If they did not the a significant number of Unix applications would fail.
These calls even work on NT and VMS.
I believe that they are defined by the POSIX.1 standard
It is just as applicable to ADVFS
The usual way to retrieve the device major and minor
numbers and the inode is to use the stat() and fstat()
routines
These system calls work the same way and return the same information on ADVFS. If they did not the a significant number of Unix applications would fail.
These calls even work on NT and VMS.
I believe that they are defined by the POSIX.1 standard
#5
Rob Donovan
-
- Admin
-
- 1,652 posts
rob@proivrc.com
- Gender:Male
- Location:Spain
Posted 10 May 2000 - 03:46 PM
Hi,
OK then, how do I decide which fileset this file is on.....
isview ------ PRO-IV ® View Shared Memory/Semaphore.
Copyright © 1999 PROIV Technology, Inc.
All rights reserved. Unauthorised use strictly prohibited.
PRO-ISAM Version: 13.04.16.00S Date: Oct 04, 1999
Shared memory key starts with 'i' [ hex 0x69 ]
Shared Memory ID : 2
Semaphore ID : 3
sem 0, id 3 = val 1: pid = 18517, ncnt = 0, zcnt = 0
sem 1, id 3 = val 0: pid = 27714, ncnt = 0, zcnt = 0
iscollect last ran at Wed May 10 16:29:29 2000
#files: 45 Maxfiles: 199
id free/hi owner rab: pid fd curr lock
100732d 306/2 0 13f8: 5794 5 69/123 0
device table
next free slot (dev_table[0]) = 0x 6
[ 0] 0x 6 [ 1] 0xA07310B9 [ 2] 0x98BBFB5D [ 3] 0xDB2A866E [ 4] 0x9C4C0CB3
[ 5] 0xCD1D63F5
Spinlocks not enabled
ID = 100732d
The inode is 732d
I guess that you index the '1' to the device table and get 0xA07310B9
How do you get to the fileset name from that.
Thanks,
Rob
OK then, how do I decide which fileset this file is on.....
isview ------ PRO-IV ® View Shared Memory/Semaphore.
Copyright © 1999 PROIV Technology, Inc.
All rights reserved. Unauthorised use strictly prohibited.
PRO-ISAM Version: 13.04.16.00S Date: Oct 04, 1999
Shared memory key starts with 'i' [ hex 0x69 ]
Shared Memory ID : 2
Semaphore ID : 3
sem 0, id 3 = val 1: pid = 18517, ncnt = 0, zcnt = 0
sem 1, id 3 = val 0: pid = 27714, ncnt = 0, zcnt = 0
iscollect last ran at Wed May 10 16:29:29 2000
#files: 45 Maxfiles: 199
id free/hi owner rab: pid fd curr lock
100732d 306/2 0 13f8: 5794 5 69/123 0
device table
next free slot (dev_table[0]) = 0x 6
[ 0] 0x 6 [ 1] 0xA07310B9 [ 2] 0x98BBFB5D [ 3] 0xDB2A866E [ 4] 0x9C4C0CB3
[ 5] 0xCD1D63F5
Spinlocks not enabled
ID = 100732d
The inode is 732d
I guess that you index the '1' to the device table and get 0xA07310B9
How do you get to the fileset name from that.
Thanks,
Rob
#6
Guest_Doctor PRO IV_*
Guest_Doctor PRO IV_*
-
- Guests
Posted 10 May 2000 - 04:14 PM
Rob,
A very good question.
To answer that properly you would need access to the C API for ADVFS. To my knowledge this is not available.
You could probably do something with the contents of
/etc/fdmns where I believe the physical/virtual mapping takes place.
However, the st_dev field returned by the (f)stat() call
should still be the same as a 'device' shown by the mount
command.
Of course, if Unix allowed fstat to run in reverse we would not have any problem!
A very good question.
To answer that properly you would need access to the C API for ADVFS. To my knowledge this is not available.
You could probably do something with the contents of
/etc/fdmns where I believe the physical/virtual mapping takes place.
However, the st_dev field returned by the (f)stat() call
should still be the same as a 'device' shown by the mount
command.
Of course, if Unix allowed fstat to run in reverse we would not have any problem!
#7
Rob Donovan
-
- Admin
-
- 1,652 posts
rob@proivrc.com
- Gender:Male
- Location:Spain
Posted 10 May 2000 - 04:47 PM
Okay,
So there is no way to get the filename from the isview information then?
Rob
So there is no way to get the filename from the isview information then?
Rob
#8
Guest_Doctor PRO IV_*
Guest_Doctor PRO IV_*
-
- Guests
Posted 10 May 2000 - 05:05 PM
Rob
Not quite - but there is no easy way as far I know.
Have you seen 'locate' the Unix utility?
This is like 'find' but much faster though not real time.
It may be possible to modify this to store away the device and inode info going forward and then search when enquiring.
Just a thought!
Not quite - but there is no easy way as far I know.
Have you seen 'locate' the Unix utility?
This is like 'find' but much faster though not real time.
It may be possible to modify this to store away the device and inode info going forward and then search when enquiring.
Just a thought!
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
