[Info-vax] OpenVMS - file selection abnormally with Copy / Rename or user ignorance?

[JF Mezei]

On 15-03-28 16:36, Stephen Hoffman wrote:

> AFAIK, the circumstances are not officially documented.
> This because there's no upside to discussing the details.

I declare that satisfying JF's curiosity to be an "upside". Therefore
the above statement is false. :-)


>         Also, all cases in which these data corruptions can occur
>         in the data that BACKUP transfers are not reliably reported
>         to you;

Are there cases where BACKUP/IGNORE would NOT report a file as currently
opened at the time BACKUP begins to copy a file ?


And in terms of problems, instead of "corruption" isn't it more correct
to state "unpredictable data" ?

>From a true "corruption" point of view, would the only corruption
possible be an indexed file where bucket split and new records added
after BACKUP has already copied the index blocks , and ends up copying
the new data buckets ?

>From a sequential or relative file point of view, wouldn't file
integrity remain , but new data may or may not be copied ?
(unpredictable). ?