 |
BACKUP savesets can be corrupted by FTP file transfers and by
tools such as zip (particularly when the zip tool has not been
asked to save and restore OpenVMS file attributes or when it
does not support OpenVMS file attributes), as well as via other
means of corruptions.
To repair these saveset corruptions, download
» RESET_BACKUP_SAVESET_FILE_ATTRIBUTES.ZIP
unzip to get the RESET_BACKUP_SAVESET_FILE_ATTRIBUTES.COM
DCL command procedure. (Be aware that some web
browsers on some platforms will try to invoke this DCL command
procedure as an executable, based on the (mis)interpretation
of the COM file extension on the particular platform.) When
downloading this tool, use of the the web browser's "save link
as" mechanism is recommended.)
For additional details on repairing corrupted BACKUP savesets:
» read the OpenVMS FAQ
-- OpenVMS FAQ text --
MGMT20. How do I fix a corrupt BACKUP saveset?
BACKUP savesets can be corrupted by FTP file transfers and by tools
such as zip (particularly when the zip tool has not been asked to
save and restore OpenVMS file attributes or when it does not support
OpenVMS file attributes), as well as via other means of corruptions.
If you have problems with the BACKUP savesets after unzipping them
or after an FTP file transfer, you can try restoring the appropriate
saveset attributes using the tool:
$ @RESET_BACKUP_SAVESET_FILE_ATTRIBUTES.COM
This tool is available on the OpenVMS Freeware (in the [000TOOLS]
directory). The Freeware is available at various sites -- see the
Freeware location listings elsewhere in the FAQ -- and other similar
tools are also available from various sources.
In various cases, the following command might work:
$ SET FILE/ATTRIBUTES=(RFM:FIX,MRS:32256,LRL:32256,RAT:NONE) file.bck
|
|
