[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

867.0. "What does FILPURGED mean?" by ASD::MINTZ (Erik @ Spit Brook (Nashua, NH)) Mon Aug 31 1987 15:28

I have encountered an odd error, which I think is a DOCUMENT problem.
For some reason, there is one document file which I can't process in batch.
We have DOCUMENT V1.0 installed.

The following terminal dialogue demonstrates the error:

--------------------------------------------------------------------

Hombre> DOCU RME_FS SOFT.SPEC LN03/NOPRI/BAT/DIAG/CONTENT
%DOC-I-IDENT, VAX DOCUMENT V1.0
%RMS-F-FILEPURGED, oldest file version purged
Hombre>

Hombre> DOCU PROTOCOL SOFT.SPEC LN03/NOPRI/BAT/DIAG/CONTENT
%DOC-I-IDENT, VAX DOCUMENT V1.0
Job DOC$PROTOCOL (queue SYS$BATCH, entry 1005) started on HOMBRE_BATCH
Hombre>

Hombre> DOCU RME_FS SOFT.SPEC LN03/NOPRI/BAT/DIAG
%DOC-I-IDENT, VAX DOCUMENT V1.0
%RMS-F-FILEPURGED, oldest file version purged
Hombre>

--------------------------------------------------------------------

PROTOCOL is handled properly, while RME_FS is not.

The problem does not occur when another user issues the same command,
on the same file, in the same directory,
nor does it occur if the /BAT switch is removed.

RME_FS is not a new file; it worked correctly until last friday, when
it suddenly started to fail.  I may have changed something, but
since the error message does even indicate which file is causing
the problem, I have no idea where to start looking.

Any ideas about what is going on here?
T.RTitleUserPersonal
Name		DateLines
867.1hmmmm, something is fishy here!VAXUUM::PELTZ�lvynstar Dun�dainMon Aug 31 1987 18:5831
         Well, if it is Document's fault then nobody elses account
         would be able to run the same command line without an
         error.  Which narrows it down to something about your
         account, or your sys$login directory.
         
         Seeing that the problem happens when you run with /batch
         leads me to believe that there is something different
         about your sys$login directory.  I can't seem to recreate
         this, but do you have a version limit set for files within
         your SYS$LOGIN?   Document tries to create a .COM file
         which it will use for the submit to batch, and it tries
         to create it in your SYS$LOGIN directory.
         
         If you cannot find this to be a reason, then please send
         me a DIR of your SYS$LOGIN and do a DIR/FULL of your
         directory from the directory ABOVE your SYS$LOGIN.  Also,
         run the command with /list and send me the listing file,
         and then I will see what I can see.
         
         When you run /BATCH document doesn't open or read the
         file before it gets submited.  (the tag translator is
         the first to open the file.)  So I doubt that it has anything
         to do with the guts of your SDML file.
         
         Hope that this helps...
         
         
         Chris
867.2FILPURGED means no disk space?ASD::MINTZErik @ Spit Brook (Nashua, NH)Tue Sep 01 1987 11:1512
Chris-

My problem appears to have been a lack of disk space on
my login device (not the same as the working directory).
Is this possible?  Why would this lead to the "FILPURGED" message?

Anyway, the current problem has gone away.

Thanks,

Erik
867.3oky dokyVAXUUM::PELTZSpot the loony!Tue Sep 01 1987 11:239
> Is this possible?  Why would this lead to the "FILPURGED" message?


         I have no idea why the RMS services reply with that message.
         In the VMS doc set it says that only the command PURGE
         utters that message.  Either this is a RMS bug, or the
         doc set is in error.  I am glad that you found the problem.
         
         Chris
867.4Minor addendum: SYS$SCRATCHASD::MINTZErik @ Spit Brook (Nashua, NH)Tue Sep 01 1987 11:5212
Then again...

On second examination, I think it MAY have been a version problem.
It appears that the temp file is created in SYS$SCRATCH, which
I have directed away from SYS$LOGIN.  Unfortunately, the offending
files are no longer available for inspection, so I can't tell
exactly what characteristic of the file might have been at fault.

If the problem comes up again I'll try to pin down the exact circumstances.

-- Erik