| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 407.1 | | BUSY::KLEINBERGER | Have a MAXCIMum Day! | Sat Oct 24 1987 13:37 | 7 |
| Rob,
I can duplicate the same error that you are getting.. I have
sent mail to the owner of this file...
Gale Kleinberger
co-moderator
|
| 407.2 | | DELNI::SILK | | Sun Oct 25 1987 11:43 | 5 |
| The problem isn't just getting a directory listing... I can't
read any of the replies to 393. I've tried using the NEXT
command from 393 and specifying 393.n from the prompt...
Nina
|
| 407.3 | Mixed results here | REGENT::GETTYS | Bob Gettys N1BRM 223-6897 | Sun Oct 25 1987 16:34 | 7 |
| I get a slightly different result. I CAN access the
notes in 393, but the dir command works the same as Rob's
listing.
I guess it is fouled up to some degree.
/s/ Bob
|
| 407.4 | recovery will be attempted | HUMAN::CONKLIN | Peter Conklin | Mon Oct 26 1987 09:02 | 10 |
| The replies to note 393 indeed seem to be inaccessible. The other
notes in that range seem OK. I have now temporarily set 393 to
/NOWRITE as a protection. During a quiet time, probably tonight,
I will write-lock the conference and use CONVERT to try to reclaim
it, then write enable.
I am now writelocking this topic as well. I will update the status
after the recovery to report on the results.
/moderator
|
| 407.5 | file recovered by CONVERT | HUMAN::CONKLIN | Peter Conklin | Tue Oct 27 1987 07:47 | 8 |
| RMS ISAM had trouble with note 393.1. Everything else seemed OK
according to ANALYZE/RMS. I did a CONVERT, which appears successful
and 393.1 is back OK, as is DIR 393.*.
If you have any problems, please post them here. But it looks OK,
so resume noting!
/moderator
|
| 407.6 | Not completely fixed | 20263::REEVES | Jon Reeves | Tue Nov 17 1987 22:07 | 3 |
| I'm just catching up on a big backlog of notes... Note 394.0 is
deleted, but some of its replies keep popping up as I "NEXT UNSEEN"
along. So far I've seen 394.4-6, but I can't get back to them.
|
| 407.7 | | POBOX::RILEY | I *am* the D.J. | Fri Jun 10 1994 09:48 | 18 |
|
I've been having a problem with this conference since the weekend (I
read the R/O copy).
I'll read a string of replies to the end, hit next unseen, and I'll be
back at the topic I just read.
This happens over and over and over.
This is only happening with this conference.
I've tried SET SEEN but the problem persists.
Ideas anyone?
Thanks
Bob
|
| 407.8 | | AKOCOA::BBARRY | Laudabamusne Rex | Fri Jun 10 1994 10:00 | 4 |
| Well I don't know what is happening in your case, but I tried
to duplicate what you have, and could not. sorry.
/Bob
|
| 407.9 | | NOTIME::SACKS | Gerald Sacks ZKO2-3/N30 DTN:381-2085 | Fri Jun 10 1994 10:17 | 2 |
| It's possible that your notebook has been corrupted. See if you get errors from
$ analyze/rms notes$notebook.note
|
| 407.10 | Probably a notebook problem | NOVA::SWONGER | DBS Software Quality Engineering | Fri Jun 10 1994 11:06 | 27 |
| I had the same problem a while back. The solution was to compress
and fix up my notes$notebook.note file. I generally do this
periodically anyway, as the file can grow quite large, depending on
your noting activiy and the activity of the conferences to which you
subscribe.
Here's a command procedure that will compress your notebook for you.
You should look at your sys$Login directory after you run it, and
purge the old copy of your notebook once you have confirmed that it
worked OK.
Roy
$!------------------------------ cut here ------------------------------
$ analyze :=
$ convert :=
$ edit :=
$ delete :=
$ analyze/rms/fdl/out=sys$scratch:comp.fdl -
sys$login:notes$notebook.note
$!
$ edit/fdl/nointer/anal=sys$scratch:comp.fdl sys$scratch:comp.fdl
$!
$ convert/fdl=sys$scratch:comp.fdl sys$login:notes$notebook.note -
sys$login:notes$notebook.note
$!
$ delete sys$scratch:comp.fdl;*
|
| 407.11 | | TOPDOC::AHERN | Dennis the Menace | Fri Jun 10 1994 11:10 | 14 |
| RE: .7 by POBOX::RILEY
>I'll read a string of replies to the end, hit next unseen, and I'll be
>back at the topic I just read.
>This happens over and over and over.
>This is only happening with this conference.
Same here. Only it's happening to me in the shadow DIGITAL conference
and nowheres else. I had a thought that maybe the shadow was being
updated while I was reading and that was resetting something. It
hasn't been happening the past few days though so maybe it's OK now.
|
| 407.12 | Another one | LOCH::SOJDA | | Sat Jun 11 1994 00:56 | 5 |
| I've had it happen to me too. I guess I just thought that the stress
was getting to me and my fingers....
Larry
|
| 407.13 | It may be the shadow conference file | SMURF::BLINN | Keep toys in the bathtub. | Tue Jun 14 1994 12:37 | 20 |
| There is some suspicion that the shadow conference itself may be
the culprit. Notes conferences are, after all, "just" large RMS
files (and multi-key at that), and there are ways in which they
can become corrupted.
Being that as it may, you can assure it's not a problem in your
own notebook file by deleting the conference entry (e.g., if you
have the shadow conference as entry DIGITAL, at the Notes prompt
say DEL ENT DIGITAL /CLASS=* if you use the character cell user
interface, or do the equivalent with the DECwindows or similar
user interface). Then re-enter it in your notebook (e.g., via the
ADD ENTRY MORTAL::DIGITAL command) and open it, then SET SEEN or
SET SEEN/BEFORE=TODAY or whatever and read to the end. If you are
STILL seeing the problem, then it's probably the conference file,
not your notebook.
We don't (yet) have an action plan to attack the conference file
corruption possibility.
Tom
|
| 407.14 | | NEWOA::BAILEY | R = S | Tue Jun 14 1994 17:46 | 6 |
|
If you find/believe there t be problems with the shadow.. please contact me
peter (PAN) Bailey
|
| 407.15 | | RT128::BATES | You can't kill a man born to hang | Tue Jun 14 1994 18:45 | 7 |
|
I'm going to recopy the master file on HUMANE and use it to replace the
existing shadow on MORTAL in an attempt to resolve any problems. Once
this is complete in the next few days, I'll announce it here.
-Joe
|