<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to modify a backup save set in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385868#M3729</link>
    <description>Wim,&lt;BR /&gt;&lt;BR /&gt;I don't have an answer about your editting, but maybe I can answer your underlying question.&lt;BR /&gt;Back in the time of DSA devices, before SCSI, the tape units WOULD give you any data behind an error, be it parity or CRC.&lt;BR /&gt;&lt;BR /&gt;Tapes used to be relatively expensive, an you needed A LOT of them, so as long as they were usable they WERE used.&lt;BR /&gt;&lt;BR /&gt;If BACKUP encountered tape errors (be it on reding OR ON WRITING (with verify), the whole operation finished nicely, with a final message:&lt;BR /&gt;nnnnn RECOVERABLE ERRORS.&lt;BR /&gt;&lt;BR /&gt;Back in 1990 I worked at a site that did have IBM, Bull, and VMS. They had (long since) discovered, that tapes refused by IBM and Bull functioned quite happily on VMS, so we ONLY got the old tapes. Most of them showed (not always) RECOVERABLE ERRORS.&lt;BR /&gt;&lt;BR /&gt;I even introduced a schema to 'clean out' the worst ones: each backup report had to be specifically checked for the errors, and as soon as the number reached THREE digits, the saveset was still OK, but the tape was marked for replacement, and the next time it was due for overwriting, it was destroted and replaced.&lt;BR /&gt;&lt;BR /&gt;If you get REALLY many errors, BACKUP will take longer, and use (much) more CPU, but that is all there is to it.&lt;BR /&gt;&lt;BR /&gt;Now we "only" have to convince the SCSI device and/or driver builders that we DO have an interest in any data past a parity error....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Jan&lt;BR /&gt;</description>
    <pubDate>Fri, 24 Sep 2004 04:39:09 GMT</pubDate>
    <dc:creator>Jan van den Ende</dc:creator>
    <dc:date>2004-09-24T04:39:09Z</dc:date>
    <item>
      <title>How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385864#M3725</link>
      <description>To test the backup utility, I would like to see how it reacts when there is a data corruption. After modifying 1 character with TPU and doing set file/at=rfm=fix, backup/list reports an empty save set (no errors). But the contents of the file is not exactly the same because tpu reorganized it.&lt;BR /&gt;&lt;BR /&gt;How can I modify only 1 character (no program writing please) ?&lt;BR /&gt;&lt;BR /&gt;How is backup reacting when there is a error caused by a corruption (crc check fail, should recalculate based upon /group=10) ? T.i. which messages are given (I didn't find any with help/mes backup) ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 24 Sep 2004 02:30:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385864#M3725</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-09-24T02:30:01Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385865#M3726</link>
      <description>There is a 'Virual File Editor' VFE availale (check comp.os.vms using Google), which can be used to block-edit a file preserving its attributes.</description>
      <pubDate>Fri, 24 Sep 2004 03:35:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385865#M3726</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2004-09-24T03:35:12Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385866#M3727</link>
      <description>Sorry for replying to myself:&lt;BR /&gt;&lt;BR /&gt;On the latest freeware CD is a utility called DIX, a screen oriented edit utility for binary files, may be you can use that one.</description>
      <pubDate>Fri, 24 Sep 2004 03:39:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385866#M3727</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2004-09-24T03:39:04Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385867#M3728</link>
      <description>I modified lots of characters of the data and got the message (while doing backup)&lt;BR /&gt;"1 error recovered by redundancy group".&lt;BR /&gt;&lt;BR /&gt;When I modified too much I got the message&lt;BR /&gt;"block iof x.sav lost due to unrecoverable error" and "software header CRC error".&lt;BR /&gt;&lt;BR /&gt;I am however impressed by the amount of data I could change. But wonder what the format is.&lt;BR /&gt;&lt;BR /&gt;Wim&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 24 Sep 2004 04:36:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385867#M3728</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-09-24T04:36:35Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385868#M3729</link>
      <description>Wim,&lt;BR /&gt;&lt;BR /&gt;I don't have an answer about your editting, but maybe I can answer your underlying question.&lt;BR /&gt;Back in the time of DSA devices, before SCSI, the tape units WOULD give you any data behind an error, be it parity or CRC.&lt;BR /&gt;&lt;BR /&gt;Tapes used to be relatively expensive, an you needed A LOT of them, so as long as they were usable they WERE used.&lt;BR /&gt;&lt;BR /&gt;If BACKUP encountered tape errors (be it on reding OR ON WRITING (with verify), the whole operation finished nicely, with a final message:&lt;BR /&gt;nnnnn RECOVERABLE ERRORS.&lt;BR /&gt;&lt;BR /&gt;Back in 1990 I worked at a site that did have IBM, Bull, and VMS. They had (long since) discovered, that tapes refused by IBM and Bull functioned quite happily on VMS, so we ONLY got the old tapes. Most of them showed (not always) RECOVERABLE ERRORS.&lt;BR /&gt;&lt;BR /&gt;I even introduced a schema to 'clean out' the worst ones: each backup report had to be specifically checked for the errors, and as soon as the number reached THREE digits, the saveset was still OK, but the tape was marked for replacement, and the next time it was due for overwriting, it was destroted and replaced.&lt;BR /&gt;&lt;BR /&gt;If you get REALLY many errors, BACKUP will take longer, and use (much) more CPU, but that is all there is to it.&lt;BR /&gt;&lt;BR /&gt;Now we "only" have to convince the SCSI device and/or driver builders that we DO have an interest in any data past a parity error....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Jan&lt;BR /&gt;</description>
      <pubDate>Fri, 24 Sep 2004 04:39:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385868#M3729</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-09-24T04:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385869#M3730</link>
      <description>Jan,&lt;BR /&gt;&lt;BR /&gt;I checked all log files of all backup and found no "recoverable" errors. I guess the drives are handling it. They must be because some frequently used Unix tools don't have any built-in raid.&lt;BR /&gt;&lt;BR /&gt;DEC should have made more publicity of this feature.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 24 Sep 2004 04:51:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385869#M3730</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-09-24T04:51:16Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385870#M3731</link>
      <description>PATCH/ABSOLUTE is a binary file editor available on all VMS systems and works on data files just fine. TECO can also be used to edit binary files.&lt;BR /&gt;&lt;BR /&gt;I don't know how DLT (which most of my backups use) drives react to unreadable tapes. I have had reason to be greatful to BACKUP's abilties with 10+ year old mag tapes.</description>
      <pubDate>Fri, 24 Sep 2004 05:28:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385870#M3731</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-09-24T05:28:36Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385871#M3732</link>
      <description>Ian,&lt;BR /&gt;&lt;BR /&gt;Patch is VAX only or is it freeware ?&lt;BR /&gt;&lt;BR /&gt;In any case, DIX works fine.&lt;BR /&gt;&lt;BR /&gt;But if you don't have the "recover" messages, I think it was the drive that did all the corrections.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 24 Sep 2004 05:31:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385871#M3732</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-09-24T05:31:03Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385872#M3733</link>
      <description>for information on the VMS backup file format you may be interested in this partial implementation of VMSBACKUP.&lt;BR /&gt;&lt;A href="ftp://ftp.lp.se/free-vms/" target="_blank"&gt;ftp://ftp.lp.se/free-vms/&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 24 Sep 2004 06:11:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385872#M3733</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-09-24T06:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385873#M3734</link>
      <description>On the VMS Freeware under RMS_TOOLS I have a little (Macro) program called ZAP.&lt;BR /&gt;It is intended to help you repair INDEXED files, and has some (minimal) smarts to format buckets to support that.&lt;BR /&gt;&lt;BR /&gt;However, it will happily change any file, including backup savesets.&lt;BR /&gt;&lt;BR /&gt;The ZAP tools works by reading a select 'bucket' into memory.&lt;BR /&gt;You then manipulate the data in the buffer with the debugger (giving support for date, float, and so on).&lt;BR /&gt;Finally write back the changed buffer.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt; How can I modify only 1 character (no program writing please) ?&lt;BR /&gt;&lt;BR /&gt;Is a dcl script a program? :-)&lt;BR /&gt;The following is based on my 'fix_saveset.com':&lt;BR /&gt;&lt;BR /&gt;$IF p1.EQS."" THEN INQUIRE p1 "Save set file name ?"&lt;BR /&gt;$IF f$search(p1).EQS."" THEN EXIT&lt;BR /&gt;$&lt;BR /&gt;$vbn = 12&lt;BR /&gt;$byte = 34&lt;BR /&gt;$value = 56&lt;BR /&gt;$&lt;BR /&gt;$save_lrl = f$file(p1,"LRL")&lt;BR /&gt;$save_mrs = f$file(p1,"MRS")&lt;BR /&gt;$save_rfm = f$file(p1,"RFM")&lt;BR /&gt;$WRITE SYS$OUTPUT " RFM was ", save_rfm, -&lt;BR /&gt;  ", MRS = ", save_mrs, ", LRL = ", save_lrl, "."&lt;BR /&gt;$SET FILE /ATTR=(RFM=FIX, MRS=512, LRL=512) 'p1 ! Easier for DCL&lt;BR /&gt;$&lt;BR /&gt;$OPEN/READ/WRITE file 'p1&lt;BR /&gt;$int_as_string[0,32] = vbn&lt;BR /&gt;$READ/KEY=&amp;amp;int_as_string file record&lt;BR /&gt;$WRITE SYS$OUTPUT "byte value was : ", f$cvsi(byte*8,8,record)&lt;BR /&gt;$record[byte*8,8]=value&lt;BR /&gt;$WRITE/UPDATE/SYMBOL file record&lt;BR /&gt;$CLOSE file&lt;BR /&gt;$SET FILE /ATTR=(RFM='save_rfm', MRS='save_mrs', LRL='save_lrl') 'p1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;fwiw,&lt;BR /&gt;Hein.&lt;BR /&gt;</description>
      <pubDate>Fri, 24 Sep 2004 10:00:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385873#M3734</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2004-09-24T10:00:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385874#M3735</link>
      <description>There is always more than one way to do it.&lt;BR /&gt;&lt;BR /&gt;On a slightly irrellavent, Friday afternoon sort of diversion -I once wrote a program called ZAP which was a partial implementation in C for VMS of the program of the same name used for patching on the RSX11 operating systems on PDP11 systems. I probably still have the source somewhere.</description>
      <pubDate>Fri, 24 Sep 2004 10:31:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385874#M3735</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-09-24T10:31:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to modify a backup save set</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385875#M3736</link>
      <description>Stuart Rance's DISKBLOCK utility is another tool (it's on at least the VMS V4 Freeware) that can be used to modify bytes within a file. (But I mostly use it for its TEST command that measures disk performance so nicely).&lt;BR /&gt;&lt;BR /&gt;The VMS V3 documentation contained information about the internal format of VMS Backup savesets.&lt;BR /&gt;&lt;BR /&gt;A quick Google search indicates someone has written a UNIX utility called vmsbackup which reads Backup savesets.&lt;BR /&gt;&lt;BR /&gt;You may also find the command BACKUP/LIST/ANALYZE to be helpful in decoding savesets.</description>
      <pubDate>Mon, 27 Sep 2004 10:11:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/how-to-modify-a-backup-save-set/m-p/3385875#M3736</guid>
      <dc:creator>Keith Parris</dc:creator>
      <dc:date>2004-09-27T10:11:10Z</dc:date>
    </item>
  </channel>
</rss>

