<?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: CMDSCRIPT and VTDPY in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106658#M90687</link>
    <description>I ended up rebooting the HSG.  Thank to those that responded with suggestions.</description>
    <pubDate>Mon, 04 Aug 2008 18:33:31 GMT</pubDate>
    <dc:creator>Jim D Frederick</dc:creator>
    <dc:date>2008-08-04T18:33:31Z</dc:date>
    <item>
      <title>CMDSCRIPT and VTDPY</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106652#M90681</link>
      <description>I tried to use cmdscript to run VTDPY.  To get to command mode of vtdpy, the instructions say hit Control-C, which unfortunately breaks me out of cmdscript and back to DCL instead of sending the Control-C to the VTDPY program.&lt;BR /&gt;&lt;BR /&gt;Is there a way to either 1) send Control-C through to VTDPY or 2) somehow exit VTDPY so I can run it using hyperterm and the wired command line interface?&lt;BR /&gt;&lt;BR /&gt;I am stuck!&lt;BR /&gt;Thanks.</description>
      <pubDate>Thu, 01 May 2008 14:17:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106652#M90681</guid>
      <dc:creator>Jim D Frederick</dc:creator>
      <dc:date>2008-05-01T14:17:43Z</dc:date>
    </item>
    <item>
      <title>Re: CMDSCRIPT and VTDPY</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106653#M90682</link>
      <description>If by cmdscript you mean a DCL .COMmand procedure, then add this line to it:&lt;BR /&gt;&lt;BR /&gt;$ SET NOCONTROL=Y</description>
      <pubDate>Thu, 01 May 2008 14:30:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106653#M90682</guid>
      <dc:creator>Jess Goodman</dc:creator>
      <dc:date>2008-05-01T14:30:37Z</dc:date>
    </item>
    <item>
      <title>Re: CMDSCRIPT and VTDPY</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106654#M90683</link>
      <description>Jess,&lt;BR /&gt;&lt;BR /&gt;No, CMDSCRIPT is a utility to control HSG raid controllers (I have an HSG80 running version V86F-8 ... which I am trying to upgrade to -13) from the DCL prompt instead of connecting to the management port of the HSG raid controller via a serial cable and hyperterminal.&lt;BR /&gt;&lt;BR /&gt;You would use a command like :&lt;BR /&gt;$ CMDSCRIPT :== $CMDSCRIPT&lt;BR /&gt;$ CMDSCRIPT -f "$1$GGA99"&lt;BR /&gt;which gets you to the HSG80 prompt where I ran VTDPY.&lt;BR /&gt;&lt;BR /&gt;HSGOCC3&amp;gt; RUN VTDPY&lt;BR /&gt;&lt;BR /&gt;When I hit CONTROL-C, I get ...&lt;BR /&gt;&lt;BR /&gt;*INTERRUPT*&lt;BR /&gt;$&lt;BR /&gt;&lt;BR /&gt;I did try the $ SET NOCONTROL=Y before using the CMDSCRIPT -f "$1$GGA99" and I still get the *INTERRUPT*, however it does not kick me back to the DCL prompt.  &lt;BR /&gt;&lt;BR /&gt;It was worth a try! :)</description>
      <pubDate>Thu, 01 May 2008 14:49:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106654#M90683</guid>
      <dc:creator>Jim D Frederick</dc:creator>
      <dc:date>2008-05-01T14:49:25Z</dc:date>
    </item>
    <item>
      <title>Re: CMDSCRIPT and VTDPY</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106655#M90684</link>
      <description>I might look to trump this, given the somewhat spotty status of the cmdscript tool.  Can you acquire the data you need via SNMP?&lt;BR /&gt;</description>
      <pubDate>Thu, 01 May 2008 14:51:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106655#M90684</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2008-05-01T14:51:46Z</dc:date>
    </item>
    <item>
      <title>Re: CMDSCRIPT and VTDPY</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106656#M90685</link>
      <description>Hoff,&lt;BR /&gt;&lt;BR /&gt;Thanks for the response.&lt;BR /&gt;&lt;BR /&gt;The data I need is the HSG80 controller % idle.  The patch procedure states that I can restart the HSG80 without shutting down the OpenVms system if the idle time is greater that 50%.&lt;BR /&gt;&lt;BR /&gt;The system does not run SNMP, so if it is possible to get the data that way, it will not be an easy process to get setup.  I assume there is some setup required to get SNMP to report back HSG80 statistics.  A lot of setup issues there I do not know how to do :(&lt;BR /&gt;&lt;BR /&gt;It is really too bad there does not seem to be a way to kill off the CMDSCRIPT session on the HSG80 from the hyperterminal/serial cable session.  I could get the data I need by running VTDPY via hyperterminal and the serial cable, but with VTDPY already running via CMDSCRIPT it will not allow me to run any other program.&lt;BR /&gt;&lt;BR /&gt;I also tried to create a file that has a CONTROL-C ascii character (03) in it, and copying that to the FTA terminal device that is running CMDSCRIPT/VTDPY but that did not work.  :(&lt;BR /&gt;&lt;BR /&gt;My main problem now is trying to kill off the CMDSCRIPT session on the HSG80 that is currently running the VTDPY program.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;</description>
      <pubDate>Thu, 01 May 2008 19:28:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106656#M90685</guid>
      <dc:creator>Jim D Frederick</dc:creator>
      <dc:date>2008-05-01T19:28:49Z</dc:date>
    </item>
    <item>
      <title>Re: CMDSCRIPT and VTDPY</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106657#M90686</link>
      <description>You might be able to write a program to do this using the pseudo-terminal driver.  See chapter 6 of the I/O User's Reference Manual.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/732FINAL/aa-pv6sf-tk/aa-pv6sf-tk.HTMl" target="_blank"&gt;http://h71000.www7.hp.com/doc/732FINAL/aa-pv6sf-tk/aa-pv6sf-tk.HTMl&lt;/A&gt;</description>
      <pubDate>Fri, 02 May 2008 21:45:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106657#M90686</guid>
      <dc:creator>Jess Goodman</dc:creator>
      <dc:date>2008-05-02T21:45:35Z</dc:date>
    </item>
    <item>
      <title>Re: CMDSCRIPT and VTDPY</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106658#M90687</link>
      <description>I ended up rebooting the HSG.  Thank to those that responded with suggestions.</description>
      <pubDate>Mon, 04 Aug 2008 18:33:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/cmdscript-and-vtdpy/m-p/5106658#M90687</guid>
      <dc:creator>Jim D Frederick</dc:creator>
      <dc:date>2008-08-04T18:33:31Z</dc:date>
    </item>
  </channel>
</rss>

