<?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: HSG80, CMDSCRIPT and a hanging GS160... in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/hsg80-cmdscript-and-a-hanging-gs160/m-p/3157220#M896</link>
    <description>as you reboot, you should take a crash, and then you will  have plenty of time to analyze and see why it was hanging.&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;Gerard</description>
    <pubDate>Tue, 06 Jan 2004 10:38:42 GMT</pubDate>
    <dc:creator>labadie_1</dc:creator>
    <dc:date>2004-01-06T10:38:42Z</dc:date>
    <item>
      <title>HSG80, CMDSCRIPT and a hanging GS160...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/hsg80-cmdscript-and-a-hanging-gs160/m-p/3157219#M895</link>
      <description>Hi all.&lt;BR /&gt;&lt;BR /&gt;We have experienced a hanging GS160 when adding&lt;BR /&gt;a device using CMDSCRIPT on an HSG80 controller.&lt;BR /&gt;Here are some details:&lt;BR /&gt;&lt;BR /&gt;The GS160 is running OpenVMS v7.3-2&lt;BR /&gt;The HSG80s are running the latest firmware rev&lt;BR /&gt;87P-4.&lt;BR /&gt;The node in question is running a command&lt;BR /&gt;which adds a unit at the controller running&lt;BR /&gt;SYS$SYSTEM:CMDSCRIPT.&lt;BR /&gt;Passed to CMDSCRIPT is a series of commands&lt;BR /&gt;with several delays before invoking a single command.  Example:  &lt;BR /&gt;&lt;BR /&gt;add snap d95 disk10400 d14                                                      &lt;BR /&gt;delay 15                                                                        &lt;BR /&gt;set d95 dis=all                                                                 &lt;BR /&gt;delay 5                                                                         &lt;BR /&gt;set d95 enable=phobos2a1,phobos1b1                                              &lt;BR /&gt;delay 5                                                                         &lt;BR /&gt;set d95 identifier=95&lt;BR /&gt;&lt;BR /&gt;Last night, at the 'Add' command the GS160 hung requiring a reboot of the node.  This does not happen often but every now and then.&lt;BR /&gt;Is this a timing issue?  HSG saturation?&lt;BR /&gt;(No hardware errors are detected on the device&lt;BR /&gt;being added nor on the controller itself)&lt;BR /&gt;&lt;BR /&gt;Any ideas?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Richard Brock&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Jan 2004 09:31:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/hsg80-cmdscript-and-a-hanging-gs160/m-p/3157219#M895</guid>
      <dc:creator>Richard Brock</dc:creator>
      <dc:date>2004-01-06T09:31:44Z</dc:date>
    </item>
    <item>
      <title>Re: HSG80, CMDSCRIPT and a hanging GS160...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/hsg80-cmdscript-and-a-hanging-gs160/m-p/3157220#M896</link>
      <description>as you reboot, you should take a crash, and then you will  have plenty of time to analyze and see why it was hanging.&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;Gerard</description>
      <pubDate>Tue, 06 Jan 2004 10:38:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/hsg80-cmdscript-and-a-hanging-gs160/m-p/3157220#M896</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2004-01-06T10:38:42Z</dc:date>
    </item>
    <item>
      <title>Re: HSG80, CMDSCRIPT and a hanging GS160...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/hsg80-cmdscript-and-a-hanging-gs160/m-p/3157221#M897</link>
      <description>On a GS 160, you should install Amds or Availability manager anyway. And may be it will help. it is available at&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/openvms/products/availman/index.html" target="_blank"&gt;http://h71000.www7.hp.com/openvms/products/availman/index.html&lt;/A&gt;</description>
      <pubDate>Tue, 06 Jan 2004 15:35:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/hsg80-cmdscript-and-a-hanging-gs160/m-p/3157221#M897</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2004-01-06T15:35:29Z</dc:date>
    </item>
    <item>
      <title>Re: HSG80, CMDSCRIPT and a hanging GS160...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/hsg80-cmdscript-and-a-hanging-gs160/m-p/3157222#M898</link>
      <description>How is your CMDSCRIPT connecting to the CLI of the HSG?  Are you using HSZTERM$SCSIPAD.EXE?  If so, do you also have a SAN appliance that is monitoring the same HSG?  If so, both are attempting to use the same I/O channel into the HSG80 controller.  while this would stomp on the others monitoring, it should not have hung your system.&lt;BR /&gt;&lt;BR /&gt;According to the CLI manual, you do not need the SET D95 DIS=all  This is the default when creating a snapshot unit.&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Jan 2004 17:45:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/hsg80-cmdscript-and-a-hanging-gs160/m-p/3157222#M898</guid>
      <dc:creator>Mike Naime</dc:creator>
      <dc:date>2004-01-06T17:45:28Z</dc:date>
    </item>
  </channel>
</rss>

