Recording pass error

[Alon Jacob]

I don't think that's it.
The log file that is in use for backup is of-course open for writing, but then the backup job won't try to access it in the recording pass stage.
To support that - the same log file has been backed-up (or acctualy passed-by) for years.

[Bojan Nemec]

Alon,

I write my previous post, after a litle test which I write after your dir/full.

The procedure was submited with:
$ SUBMIT/LOG=[.B]B.LOG B.COM

And you can see the contents of the attached log file.

Bojan

[Antoniov.]

Hi Alon,
I use /EXCL qualifier to exclude LOG file from saveset; I don't know why this worked for you because in my case I always met problem.

Hi Bojan,
I'm not yet congratulated with you because you are well kwnoledge person; welcome in vms forum and still continue your answers. Because you are newbie here, I hint you, when give attachment, use .txt extension even for .log or .com to avoid problem when reading.

Antonio Vigliotti

[Doug Phillips]

So, does anyone know if this documentation conflict is being or has been corrected or resolved yet?

++
$ help backup /record
BACKUP
/RECORD
Command Qualifier
...
o To use the /RECORD qualifier you must either own the file or
have SYSPRV privileges.
++
From the "Guide to System Security", Appendix A. Readall privilege:
"READALL (...) allows updating of such backup-related file characteristics as the backup date".
++

Doug

[Bojan Nemec]

Atonio,

Thank you for yours congratulations, and about the extension I will remember your hint.

Doug,

I look at the help backup /record on OpenVMS 7.3-2, as you (and me) write,
in "HP OpenVMS System Management Utilities Reference Manual" is the same,
the "HP OpenVMS System Manager's Manual, Volume 1: Essentials" does not mention any privileges (In one example there is a BYPASS privilege!),
in the "OpenVMS Utility Routines Manual" and "HP OpenVMS DCL Dictionary" not mentioned and
as Jan and you mentioned in "HP OpenVMS Guide to System Security" there is a lot abbout READALL privilege and backup.

(By the way the HTML link to "HP OpenVMS Guide to System Security" on the "HP OpenVMS Systems Documentation" http://h71000.www7.hp.com/doc/os732_index.html seems broken and
when I try to search READALL from this page there was no results).

Bojan

[Uwe Zessin]

The ability to change some file header characteristics with READALL privilege was changed quite some time in the past - OpenVMS (VAX) V6.0, if I recall correctly.

[Jan van den Ende]

Uwe,

clarify please. Changed from What to What?

Do I understand correctly that some docs reflect old behavior, while others have been updated?

Anyway, of course HP should make the docs consistent, and reflective of actual behavior.

Jan

[Bojan Nemec]

Uwe,

I try the READALL privilege and BACKUP/RECORD on OpenVMS (Alpha) 6.2 and VMS 5.5-2 (VAX ) it works on both.

Jan,

The READALL privilege is not mentioned in the HELP BACKUP /RECORD, there is only SYSPRV or ownership the same is in "HP OpenVMS System Management Utilities Reference Manual". I agrre with you that the documentation and the help should be updated.

Bojan

[Uwe Zessin]

I hope this explains it better than my attempt:
http://groups.google.de/groups?selm=1993Jul21.231140.1968%40nntpd.lkg.dec.com&output=gplain

[Alon Jacob]

Dear HP forum managers - this is to clarify that my problem was solved, and I consider this issue closed.
Once again I'd like to thank all people who shared their good knowledge with me, and I'll continue reading replies to this issue as well as all others.

Thanks a lot, everyone.

[Doug Phillips]

I hope this explains it better than my attempt:
http://groups.google.de/groups?selm=1993Jul21.231140.1968%40nntpd.lkg.dec.com&output=gplain


I explains that READALL should be enough, but it doesn't explain the conflict in the documentation, and if Alon's fix was to give the backup process SYSPRV, then, although his problem is solved, it is not yet explained.

Maybe someone should start a new thread if this needs further discussion since Alon feels this one is complete?

[Alon Jacob]

Problem solved.