| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 453.1 | | IOSG::MAURICE | IOSG ain't a place to raise a kid | Fri Apr 10 1992 11:01 | 6 |
| No - we only know who has reserved a document. We hope to do better in
a PFR.
Cheers
Stuart
|
| 453.2 | SH DEV /FILES | IOSG::CARLIN | Dick Carlin IOSG, Reading, England | Fri Apr 10 1992 11:34 | 13 |
| > ..., except by going through SDA>SH LOCK...
... and SHOW DEVICE /FILES for the file locks of course. That'll give
some idea who is actually reading or editing a document content file.
The picture will be incomplete because, for example, the text dsab may
close the file, releasing the lock if someone is reading a very short
file.
SDA SH LOCK can be very tedious on a busy system, unless there are some
options I haven't discovered. But I think that is the only way to see
the FC locks.
Dick
|
| 453.3 | Use DECwatch to view locks, not SDA | IOSG::TALLETT | Just one more fix, then we can ship... | Fri Apr 10 1992 20:38 | 1 |
|
|
| 453.4 | SET WATCH FILE ? | EVTAI1::PROT | | Mon Apr 13 1992 18:11 | 5 |
| what do you mean by DECwatch ?
$ SET WATCH FILE /CLASS ?
Louis
|
| 453.5 | DECwatch | IOSG::TALLETT | Just one more fix, then we can ship... | Mon Apr 13 1992 21:31 | 16 |
| Hi there!
No, I mean DECwatch, the product. It used to be the internal
tool WHAT, which became an ASSET, and now is a product (I think).
It formats the lock database in ASCII (I wish people would use
ASCII lock names all the time). There is a kit in KITSDIR.DOC.
I guess you could write a small program to list the locks relevant
to document locking if you knew the format. However, I guess most
of them would be owned by the FileCab server with no way to trace
back to the real owner. How do we plan to get this information in
the future Stuart? Would the FCS have to cooperate?
Regards,
Paul
|