 
| Subject: | |
| From: | |
| Reply To: | [log in to unmask][log in to unmask], 5 Jun 1997 08:49:32 PST428_- Greg Chaplin wrote: >I've been racking my brains trying to figure out a way of putting >certain groups in our development account off-limits. I'm trying to >set up source control procedures, such that the original files are >kept in the "secure" groups. [snip] >Anyone got any hints or ideas? I don't think we need to buy a >full-blown source control package. [...]46_5Jun199708:49: [log in to unmask] |
| Date: | Fri, 6 Jun 1997 09:16:08 -0400 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
Date: Thu, 5 Jun 1997 17:59:58 -0400
From: "Stigers, Gregory - ANDOVER" <[log in to unmask]>
Subject: 9x File status codes
You ought to have a program ERR in TELESUP. If you supply an error number, it
will return every subsystem's message for that number. If you supply the
error number and the word FILES (I think), you will get what you are looking
for.
COBERR 641 is a red herring for your purposes. You want the file system
error.
If you have a MPEX, they used to distribute Eugene and Vladimir's papers with
each release. Look for a file called TRUTH.PAPERS (or some such). This is an
old paper (1983?) by Eugene, "The Truth about Disc Files". In the back of the
article is a list (out of date, but still handy) of FSERRs with the text of
the error message and a solution. It's useful for most commonly found FSERRs.
The paper is also in a book that Vesoft used to give out at Interex. If you
have access to old Proceedings, check out one of the conferences in the early
80's (Montreal, I think).
Leonard Berkowitz
|
|
|
