[Info-vax] Can't find file retained on error

[Jan-Erik Soderholm]

tadamsmar wrote 2011-02-22 22:33:
> On Feb 22, 2:36 pm, abrsvc<dansabrservi... at yahoo.com>  wrote:
>> On Feb 22, 1:53 pm, "Richard B. Gilbert"<rgilber... at comcast.net>
>> wrote:
>>
>>
>>
>>
>>
>>> On 2/22/2011 11:25 AM, tadamsmar wrote:
>>
>>>> I have these messags in my print queue, but I cannot locate the
>>>> FOR010.DAT file that is referred to.   Can anyone explain?
>>
>>>>        87  FOR010          CELEES            1  Retained on error
>>>>          %SYSTEM-F-ABORT, abort
>>>>            Submitted 15-DEC-2010 17:09:53.37 /FORM=ERROR /PRIORITY=100
>>>>            File: _DSA0:[]FOR010.DAT; /DELETE
>>>>            Completed 15-DEC-2010 17:10:05.48 on queue EESLOG1
>>
>>>>       719  FOR010          CELEES            1  Retained on error
>>>>          %SYSTEM-F-ABORT, abort
>>>>            Submitted  4-FEB-2011 08:18:09.79 /FORM=ERROR /PRIORITY=100
>>>>            File: _DSA0:[]FOR010.DAT; (checkpointed) /DELETE
>>>>            Completed  4-FEB-2011 16:47:03.74 on queue EESLOG1
>>
>>> Don't make me use my imagination!  How about starting with the basics?
>>> What version of VMS are you using.  Which of the three possible
>>> architectures (VAX, Alpha, and Itanium) are you using?  Or are you
>>> emulating something using the x-86 platform? Is the system in question
>>> part of a VMS cluster?  Have any patches been applied?  Which ones?
>>> What sequence of commands did you use to produce the output shown?
>>
>>> It's times like that this that I REALLY miss the late Carl J. Lydick!!
>>
>> Regardless of the OpenVMS version, the behavior has been the same for
>> years. In this case, the filename of dsa0:[]for010.dat incates a
>> spooled file that has no directory home.  Since the message also
>> indicates that the file was retained on error, the fiel exists, but
>> without any directory entry.  The use of ANAL/DISK/REPAIR will place
>> those files into the [syslost] directory.- Hide quoted text -
>>
>> - Show quoted text -
>
> Thanks for the help. I did find the files using your procedure.
>
> In the queue entry (see the original post) there is a submitted time
> and a completed time
>
> Does the "completed time" indicate that the file was eventually
> printed at that time?

It is probably the time the %SYSTEM-F-ABORT error happend.
Maybe there was a STOP/QUE (/RESET) or something.



    Sometimes the completed time is much later
> than the submitted time (on the the examples I posted).  These files
> were logger message and I guess they were printed out of order if the
> printing was delayed to the completion time.