 |
The Question is:
WE ran an logging program which opened and
wrote out a fairly large data file. But the
process had to be shutdown, and the log file
was never closed. How can I read that file.
everything I've tried, e.g., type, edit, dump, etc., gives results consistent
with the file being empty, but by monitoring
dir/siz=all we could see it get built.
The Answer is :
Use of sys$forcex or similar call is recommended. (At least one example
of using the sys$forcex to cause a process to exit -- and to invoke the
I/O rundown handling -- is on the OpenVMS Freeware.)
To reset the end-of-file marker, try the DCL command SET FILE/END_OF_FILE
or a similar tool that resets the location of the EOF marker. This tool
will permit access to the information, assuming the desired information
was written to the file. Processes that are deleted via STOP or sys$delrpc
system service call may not have written out all I/O buffers, and will not
invoke the normal rundown handling to flush out these buffers.
Please see the OpenVMS FAQ for information on using shared-write access.
Topics specific to unintential initialization or the overwriting of
disk and tape media include (1286) and (6990).
For errors resulting from file structure, directory structure, or
file structure corruptions, please see topics such as (1213), (4088),
(4571), (5071), (5553), (5719), (6021), (6234).
If you want to overwrite the data on the media, related topics include
(841), (3926), (4286), (4598), and (7320).
|
|
|
|
|
