<?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 tapesys V6.2.3, on alpha 8.2 in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/tapesys-v6-2-3-on-alpha-8-2/m-p/4328455#M92697</link>
    <description>installation was successful &lt;BR /&gt;1. @tapesys_sytem:startup     ok&lt;BR /&gt;2. sho system /proc=tap* &lt;BR /&gt; &lt;BR /&gt;$ sho system /pro=tap*&lt;BR /&gt;OpenVMS V8.2  on node JASPER  24-DEC-2008 12:06:16.97  Uptime  0 02:04:09&lt;BR /&gt;  Pid    Process Name    State  Pri      I/O       CPU       Page flts  Pages&lt;BR /&gt;204000A5 TAPESTART       COM      0      905   0 00:00:06.01      2424    130&lt;BR /&gt;$ sho system /pro=tap*&lt;BR /&gt;OpenVMS V8.2  on node JASPER  24-DEC-2008 12:06:58.04  Uptime  0 02:04:50&lt;BR /&gt;  Pid    Process Name    State  Pri      I/O       CPU       Page flts  Pages&lt;BR /&gt;204000A5 TAPESTART       COM      0     2486   0 00:00:18.06      5636     88&lt;BR /&gt;204000A6 TAPMGRDB        LEF     10      737   0 00:00:04.91      2746    334&lt;BR /&gt;204000A7 TAPMGRRQ        LEF      8      773   0 00:00:05.62      3413    105&lt;BR /&gt;&lt;BR /&gt;but during the startup process I get the final message as &lt;BR /&gt;&lt;BR /&gt;%%%%%%%%%%%  OPCOM  24-DEC-2008 12:07:14.63  %%%%%%%%%%%&lt;BR /&gt;Message from user TAPESYS on JASPER&lt;BR /&gt;TAPMGRDB, %TAPMGR-F-ALROPNERR, failed to open alias reel file !AD&lt;BR /&gt;&lt;BR /&gt;$&lt;BR /&gt;%%%%%%%%%%%  OPCOM  24-DEC-2008 12:07:15.13  %%%%%%%%%%%&lt;BR /&gt;Message from user TAPESYS on JASPER&lt;BR /&gt;TAPMGRDB, -RMS-F-DUP, duplicate key detected (DUP not set)&lt;BR /&gt;&lt;BR /&gt;$&lt;BR /&gt;%%%%%%%%%%%  OPCOM  24-DEC-2008 12:07:17.58  %%%%%%%%%%%&lt;BR /&gt;Message from user TAPESYS on JASPER&lt;BR /&gt;TAPMGRDB, TAPMGRDB has stopped - %TAPMGR-F-ALROPNERR, failed to open alias reel&lt;BR /&gt;file !AD&lt;BR /&gt;        - restart TAPESYS&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;BR /&gt;Bjay&lt;BR /&gt;</description>
    <pubDate>Wed, 24 Dec 2008 11:49:23 GMT</pubDate>
    <dc:creator>Bjay</dc:creator>
    <dc:date>2008-12-24T11:49:23Z</dc:date>
    <item>
      <title>tapesys V6.2.3, on alpha 8.2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tapesys-v6-2-3-on-alpha-8-2/m-p/4328455#M92697</link>
      <description>installation was successful &lt;BR /&gt;1. @tapesys_sytem:startup     ok&lt;BR /&gt;2. sho system /proc=tap* &lt;BR /&gt; &lt;BR /&gt;$ sho system /pro=tap*&lt;BR /&gt;OpenVMS V8.2  on node JASPER  24-DEC-2008 12:06:16.97  Uptime  0 02:04:09&lt;BR /&gt;  Pid    Process Name    State  Pri      I/O       CPU       Page flts  Pages&lt;BR /&gt;204000A5 TAPESTART       COM      0      905   0 00:00:06.01      2424    130&lt;BR /&gt;$ sho system /pro=tap*&lt;BR /&gt;OpenVMS V8.2  on node JASPER  24-DEC-2008 12:06:58.04  Uptime  0 02:04:50&lt;BR /&gt;  Pid    Process Name    State  Pri      I/O       CPU       Page flts  Pages&lt;BR /&gt;204000A5 TAPESTART       COM      0     2486   0 00:00:18.06      5636     88&lt;BR /&gt;204000A6 TAPMGRDB        LEF     10      737   0 00:00:04.91      2746    334&lt;BR /&gt;204000A7 TAPMGRRQ        LEF      8      773   0 00:00:05.62      3413    105&lt;BR /&gt;&lt;BR /&gt;but during the startup process I get the final message as &lt;BR /&gt;&lt;BR /&gt;%%%%%%%%%%%  OPCOM  24-DEC-2008 12:07:14.63  %%%%%%%%%%%&lt;BR /&gt;Message from user TAPESYS on JASPER&lt;BR /&gt;TAPMGRDB, %TAPMGR-F-ALROPNERR, failed to open alias reel file !AD&lt;BR /&gt;&lt;BR /&gt;$&lt;BR /&gt;%%%%%%%%%%%  OPCOM  24-DEC-2008 12:07:15.13  %%%%%%%%%%%&lt;BR /&gt;Message from user TAPESYS on JASPER&lt;BR /&gt;TAPMGRDB, -RMS-F-DUP, duplicate key detected (DUP not set)&lt;BR /&gt;&lt;BR /&gt;$&lt;BR /&gt;%%%%%%%%%%%  OPCOM  24-DEC-2008 12:07:17.58  %%%%%%%%%%%&lt;BR /&gt;Message from user TAPESYS on JASPER&lt;BR /&gt;TAPMGRDB, TAPMGRDB has stopped - %TAPMGR-F-ALROPNERR, failed to open alias reel&lt;BR /&gt;file !AD&lt;BR /&gt;        - restart TAPESYS&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;BR /&gt;Bjay&lt;BR /&gt;</description>
      <pubDate>Wed, 24 Dec 2008 11:49:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tapesys-v6-2-3-on-alpha-8-2/m-p/4328455#M92697</guid>
      <dc:creator>Bjay</dc:creator>
      <dc:date>2008-12-24T11:49:23Z</dc:date>
    </item>
    <item>
      <title>Re: tapesys V6.2.3, on alpha 8.2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tapesys-v6-2-3-on-alpha-8-2/m-p/4328456#M92698</link>
      <description>After installation usually the next step is configuration.  Is this a new install?  Have you "setup" tapesys?  I'm by no means a tapesys expert but I played with it a little when I was working for another company.  IIRC, on a new install your setup.par file will be empty.  You probably need to "customize and configure" before you can start up.  This is pretty much SOP.&lt;BR /&gt;</description>
      <pubDate>Wed, 24 Dec 2008 13:26:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tapesys-v6-2-3-on-alpha-8-2/m-p/4328456#M92698</guid>
      <dc:creator>EdgarZamora_1</dc:creator>
      <dc:date>2008-12-24T13:26:45Z</dc:date>
    </item>
    <item>
      <title>Re: tapesys V6.2.3, on alpha 8.2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tapesys-v6-2-3-on-alpha-8-2/m-p/4328457#M92699</link>
      <description>I did populated setup.par actually it is same from other system which is working fine I edit it to reflect for this node , indeed it is a new installation and never worked b4&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Dec 2008 05:33:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tapesys-v6-2-3-on-alpha-8-2/m-p/4328457#M92699</guid>
      <dc:creator>Bjay</dc:creator>
      <dc:date>2008-12-25T05:33:59Z</dc:date>
    </item>
    <item>
      <title>Re: tapesys V6.2.3, on alpha 8.2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tapesys-v6-2-3-on-alpha-8-2/m-p/4328458#M92700</link>
      <description>&amp;gt; [...] I edit it [...]&lt;BR /&gt;&lt;BR /&gt;Edit how?  -RMS-F-DUP sounds like an indexed&lt;BR /&gt;file, and if you edited it with a normal text&lt;BR /&gt;editor, you probably damaged it.  You might&lt;BR /&gt;compare DIRE /FULL output from a working&lt;BR /&gt;system and your new system for the file you&lt;BR /&gt;edited.&lt;BR /&gt;&lt;BR /&gt;I know nothing about TAPESYS, but if it uses&lt;BR /&gt;indexed files, it might include some tools to&lt;BR /&gt;use to create and change them.&lt;BR /&gt;&lt;BR /&gt;Is it time to read the documentation yet?</description>
      <pubDate>Thu, 25 Dec 2008 18:02:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tapesys-v6-2-3-on-alpha-8-2/m-p/4328458#M92700</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-12-25T18:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: tapesys V6.2.3, on alpha 8.2</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tapesys-v6-2-3-on-alpha-8-2/m-p/4328459#M92701</link>
      <description>It sounds like you have your 'PRI' or 'SEC' set to an unknown node.&lt;BR /&gt;&lt;BR /&gt;Can you confirm node names and send in SETUP.PAR.&lt;BR /&gt;&lt;BR /&gt;Rob.</description>
      <pubDate>Mon, 05 Jan 2009 11:51:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tapesys-v6-2-3-on-alpha-8-2/m-p/4328459#M92701</guid>
      <dc:creator>Robert Atkinson</dc:creator>
      <dc:date>2009-01-05T11:51:06Z</dc:date>
    </item>
  </channel>
</rss>

