| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
VMS 5.5 ALL-IN-1 3.0
The ALL-IN-1 system manager is running the archiving housekeeping
procedure, and every time it attempted to archive a document, the error
"%OA-W-NOARCAREA, noarchive filename given on command line."
appears in the log file. I thought that the archive area was checked
before the arcghive went ahead and I can't find any mention of the
error.
Can anyone shed any light on this?
Also, during the same procedure, the archiving run looped on a certain
users file cabinet. It ran through his file cabinet and processed 127
document, and then it did the same 127 again, and again, and again...
Anyone seen this before? Ideas?
Steve.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1974.1 | IOSG::MAURICE | Is there life on IOSG? | Wed Dec 16 1992 17:34 | 20 | |
Hi,
I've looked in the code and you can get this error either by having
written your own script with bad calls to the ARCHIVE functions, or,
what seems much more likely, by having a duff directory in the archive
area record.
Type SM MAR and select the OPEN archive area, and type R to read it.
Look at the directory field and check that the directory referred to
does in fact exist. If it's a logical check the translation.
Do also check there are no customisations.
As for your loop I'd recommend putting a set_trace function call in
oa$lib:archive.com. I don't think this problem has come up before with
V3.0
Cheers
Stuart
| |||||
| 1974.2 | Files missing from the [.DOC%] directories? | HSKPRF::TAURIAINEN | Wed Dec 30 1992 13:55 | 7 | |
Back in v2.4 time I noticed that the archive procedure could loop if
there was an entry for a document in the users docdb but the actual
file from the [.DOC%] directories had been deleted. I tested this in our
local language version of 2.4 but haven't tried on a v3.0 system.
--Matti
| |||||