<?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: ABS Tape Library errors in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/abs-tape-library-errors/m-p/5234817#M98370</link>
    <description>Thanks.  I know it is old, but I believe the update past this required something else I could not upgrade.&lt;BR /&gt;&lt;BR /&gt;But, you may have suggested something that could be the problem.  I had a disk fail that had some of my (not used much anymore) backup catalogs that were not for this saveset.  I was able to recover those catalog files (16 GB) but had them on another disk until I could get the right H/W in place. (Shoestring budget here).  I just got those files back into the same location as before in the past few days.  &lt;BR /&gt;&lt;BR /&gt;I restarted the job again tonight and it is already past Thread #13, so I think I have got it fixed.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Rick</description>
    <pubDate>Wed, 14 Apr 2010 02:40:00 GMT</pubDate>
    <dc:creator>Rick Dyson</dc:creator>
    <dc:date>2010-04-14T02:40:00Z</dc:date>
    <item>
      <title>ABS Tape Library errors</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/abs-tape-library-errors/m-p/5234815#M98368</link>
      <description>I have an OpenVMS/Alpha Cluster v7.3-2 with a node having a TL892    &lt;BR /&gt;library.  I use an old version of ABS (v3.2A) (I know, much newer but this                                                  &lt;BR /&gt;has worked for years so why change it if it was not broken?).  In past                     &lt;BR /&gt;couple weeks I have noticed these errors that break the backup process. &lt;BR /&gt;It should be noted that it ***DOES*** work OK (from logs anyway) for 8                     &lt;BR /&gt;entire disks before getting this error in my monthly archive job:   &lt;BR /&gt;  &lt;BR /&gt;Operation #9 starting at  9-APR-2010 19:36:10              &lt;BR /&gt;  &lt;BR /&gt;   Data Movement Type:    UNKNOWN MOVEMENT TYPE            &lt;BR /&gt;   Incremental Level:     Full Operation       &lt;BR /&gt;  &lt;BR /&gt;   Object Set:    &lt;BR /&gt;      Object Type:        VMS_FILES                        &lt;BR /&gt;      Include List:       DISK$RAID3:                      &lt;BR /&gt;      Exclude List:    &lt;BR /&gt;  &lt;BR /&gt;   Archive Information:    &lt;BR /&gt;      Storage Class Name: MONTHLY_ARCHIVE                  &lt;BR /&gt;      Saveset Location:   000037                           &lt;BR /&gt;      Saveset Name:       9APR201019360300.                &lt;BR /&gt;  &lt;BR /&gt;   Execution Environment:                                  &lt;BR /&gt;      Name:               MONTHLY_ARCHIVE                  &lt;BR /&gt;      Number of retries:  3 &lt;BR /&gt;      Retry Interval:     15 minute(s)                     &lt;BR /&gt;  &lt;BR /&gt;&lt;BR /&gt;19:36:10 THREAD #9: ABS_SYSOPEN_FAILED, SYS$OPEN service failed&lt;BR /&gt;19:36:10 THREAD #9: -%RMS-E-DNF, directory not found      &lt;BR /&gt;19:36:10 THREAD #9: ABS_SUBPROCDELETEERR, Error deleting subprocess  &lt;BR /&gt;19:36:10 THREAD #9: -Line = 1257, File = RESD$:[SRC]AGENT_SUBPROCESS.C;1                   &lt;BR /&gt;19:36:10 THREAD #9: ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific error in diag block&lt;BR /&gt;19:36:10 THREAD #9: -%SYSTEM-F-IVCHAN, invalid I/O channel       &lt;BR /&gt;19:36:10 THREAD #9: SYS$OPEN service failed  &lt;BR /&gt;  &lt;BR /&gt;&lt;BR /&gt;Does anyone have any suggestions on what is meant by "UNKNOWN MOVEMENT&lt;BR /&gt;TYPE" and the subsequent service Open failure and invalid I/O channel?&lt;BR /&gt;This might have started after the VMS732_Update v20 but I can't confirm&lt;BR /&gt;that since old logs are not around anymore.  That update was applied here&lt;BR /&gt;in early Feb 2010.&lt;BR /&gt;      &lt;BR /&gt;Thanks for any suggestions!&lt;BR /&gt;      &lt;BR /&gt;Rick Dyson</description>
      <pubDate>Tue, 13 Apr 2010 12:29:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/abs-tape-library-errors/m-p/5234815#M98368</guid>
      <dc:creator>Rick Dyson</dc:creator>
      <dc:date>2010-04-13T12:29:40Z</dc:date>
    </item>
    <item>
      <title>Re: ABS Tape Library errors</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/abs-tape-library-errors/m-p/5234816#M98369</link>
      <description>Hi Rick,&lt;BR /&gt;&lt;BR /&gt;ABS V3.2A is a very old version and is unsupported. The latest one is ABS V4.5 (1200). It is recommended to upgrade ABS to get the latest features, bug-fixes and HP support for the product.&lt;BR /&gt;&lt;BR /&gt;For the problem you have reported,&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;&lt;BR /&gt;19:36:10 THREAD #9: ABS_SYSOPEN_FAILED, SYS$OPEN service failed&lt;BR /&gt;19:36:10 THREAD #9: -%RMS-E-DNF, directory not found &lt;BR /&gt;&amp;gt;&amp;gt;&lt;BR /&gt;&lt;BR /&gt;I think this may have something to do with opening the catalog/catalog staging file. See if the ABS$CATALOG logical is a search-list. If so, check if all the paths defined in the search list are correct.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Deepa</description>
      <pubDate>Wed, 14 Apr 2010 01:00:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/abs-tape-library-errors/m-p/5234816#M98369</guid>
      <dc:creator>Deepa R Shenoy</dc:creator>
      <dc:date>2010-04-14T01:00:56Z</dc:date>
    </item>
    <item>
      <title>Re: ABS Tape Library errors</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/abs-tape-library-errors/m-p/5234817#M98370</link>
      <description>Thanks.  I know it is old, but I believe the update past this required something else I could not upgrade.&lt;BR /&gt;&lt;BR /&gt;But, you may have suggested something that could be the problem.  I had a disk fail that had some of my (not used much anymore) backup catalogs that were not for this saveset.  I was able to recover those catalog files (16 GB) but had them on another disk until I could get the right H/W in place. (Shoestring budget here).  I just got those files back into the same location as before in the past few days.  &lt;BR /&gt;&lt;BR /&gt;I restarted the job again tonight and it is already past Thread #13, so I think I have got it fixed.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Rick</description>
      <pubDate>Wed, 14 Apr 2010 02:40:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/abs-tape-library-errors/m-p/5234817#M98370</guid>
      <dc:creator>Rick Dyson</dc:creator>
      <dc:date>2010-04-14T02:40:00Z</dc:date>
    </item>
    <item>
      <title>Re: ABS Tape Library errors</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/abs-tape-library-errors/m-p/5234818#M98371</link>
      <description>I had a broken link to some of my ABS Catalog data files that was the problem.&lt;BR /&gt;&lt;BR /&gt;rick</description>
      <pubDate>Wed, 14 Apr 2010 02:42:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/abs-tape-library-errors/m-p/5234818#M98371</guid>
      <dc:creator>Rick Dyson</dc:creator>
      <dc:date>2010-04-14T02:42:49Z</dc:date>
    </item>
  </channel>
</rss>

