V2T@NIHCU.BITNET (Terry Voss) (02/02/90)
I have sent the following message to Eric. I thought I would also
ask the members of LSTSRV-L. I am not a subscriber to LSTSRV-L;
all replies should be directed to V2T@NIHCU. Thanks.
I am currently having a problem with LISTSERV. It seems
that Listserv's A-disk (specifically the directory) is being
corrupted by something. No other disk for any other machine is
experiencing the same problem. Last fall, the A-disk suddenly
had duplicate files for some, missing files for others, okay
files for the rest. I went through a tedious exercise to make
the A-disk viable again. Just recently, several directory
entries have been corrupted such that some fileids are not
displayable (and thus not obtainable) and the date and time
fields are no longer numeric (causing program exceptions for a
simple filelist). Obviously, Listserv cannot operate.
I would like to know if there is any Listserv function
(EXEC, etc) that directly writes to the mini-disk directory. I
have some experienced VM people who are knowledgeable in EXECs
that could help me work on the reason for my problem. I
understand that you do not support the level of CMS (Rel 6) that
I am running; we just need some direction to begin investigating
Listserv functions and how they interact with IBM software.
Thank you for your time.
Terry Voss
V2T@NIHCU (mail, messages)
V2T@NIHCUSV1 (code, files)STAN@VM.TEMPLE.EDU (Stan Horwitz) (02/02/90)
On Thu, 1 Feb 90 11:16:23 EST Terry Voss said: >I have sent the following message to Eric. I thought I would also >ask the members of LSTSRV-L. I am not a subscriber to LSTSRV-L; >all replies should be directed to V2T@NIHCU. Thanks. > > > I am currently having a problem with LISTSERV. It seems >that Listserv's A-disk (specifically the directory) is being >corrupted by something. Terry, it seems to me as if two users are trying to access the A disk in write mode simultaneously. If two or more users try to alter any of the files on the same minidisk simultaneously, the results typically lead to disaster. This is because user A and user B are both modifying the information relating to files on that disk at the same time. They are both trying to modify the same file which contains minidisk info at the same time which means that when they both release the disk, the saved disk info gets corrupted along with many of the files that were previously on the disk prior to it being simultaneously accessed by two or more people. If someone else is accessing the disk without permission, you might want to be sure to change the disk's write password. Stan Horwitz Bitnet: STAN AT TEMPLEVM Temple University Internet: STAN AT VM.TEMPLE.EDU Mainframe Consultant Ma Bell: 215-787-5555
BEC@ALBNYVM1.BITNET (Ben Chi) (02/02/90)
Regarding mysterious corruption of LISTSERV 191, is there any possibili- ty that you or someone else LINKed it MW (without necessarily having performed any writes)? That'll do it for sure.
PDB@CORNELLF.BITNET (Philip Bogdonoff) (02/05/90)
>Phil - This item itself isn't all that important, but note the sender: >Ben Chi from Albany. Ben just started running LISTSERV within the past >couple of months, and he might be a good one to ask about how much >person and machine resources are needed. I've met Ben at a conference, >but not in a context where he'd remember me. It was my impression that >he'd be willing to respond to such a question. Steve Thanks for the suggestion. I may follow-up when I get back and caught up. (I'm not really here right now -- I expected to get back from Vermont about 6 hours earlier and I've got to get ready to catch an 8am plane.)