<?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 Output device communication error in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/output-device-communication-error/m-p/4470238#M58517</link>
    <description>hi, i have this problem.&lt;BR /&gt;&lt;BR /&gt;i need help!&lt;BR /&gt;&lt;BR /&gt;I_CB_INFO PHIFAC startup OK &lt;BR /&gt;E_CB_IE Internal error (Error in scan_reply(): Machine error: R;E;0;1111;"No machine response";) &lt;BR /&gt;E_CB_IE Internal error (Error in qh_write_cmd(): device returned E (R;E;0;1111;"No machine response";), level 0) &lt;BR /&gt;E_CB_IE Internal error (start_recorder: qh_write_cmd failed (reply: R;E;0;1111;"No machine response";)) &lt;BR /&gt;E_CB_IE Internal error (fripout_startpage: start_recorder failed) &lt;BR /&gt;E_CTRL_ODCE Output device communication error (fripout(10): E_OPENDEV) &lt;BR /&gt;Entered stage "" &lt;BR /&gt;Progress: 0% &lt;BR /&gt;INFO: bgfrm.exposeresult(3,) &lt;BR /&gt;Entered stage "bgfrs.unregister" &lt;BR /&gt;INFO: bgfrm.holdqueue(BG-3800-L2)</description>
    <pubDate>Thu, 30 Jul 2009 13:53:51 GMT</pubDate>
    <dc:creator>NUVIC</dc:creator>
    <dc:date>2009-07-30T13:53:51Z</dc:date>
    <item>
      <title>Output device communication error</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/output-device-communication-error/m-p/4470238#M58517</link>
      <description>hi, i have this problem.&lt;BR /&gt;&lt;BR /&gt;i need help!&lt;BR /&gt;&lt;BR /&gt;I_CB_INFO PHIFAC startup OK &lt;BR /&gt;E_CB_IE Internal error (Error in scan_reply(): Machine error: R;E;0;1111;"No machine response";) &lt;BR /&gt;E_CB_IE Internal error (Error in qh_write_cmd(): device returned E (R;E;0;1111;"No machine response";), level 0) &lt;BR /&gt;E_CB_IE Internal error (start_recorder: qh_write_cmd failed (reply: R;E;0;1111;"No machine response";)) &lt;BR /&gt;E_CB_IE Internal error (fripout_startpage: start_recorder failed) &lt;BR /&gt;E_CTRL_ODCE Output device communication error (fripout(10): E_OPENDEV) &lt;BR /&gt;Entered stage "" &lt;BR /&gt;Progress: 0% &lt;BR /&gt;INFO: bgfrm.exposeresult(3,) &lt;BR /&gt;Entered stage "bgfrs.unregister" &lt;BR /&gt;INFO: bgfrm.holdqueue(BG-3800-L2)</description>
      <pubDate>Thu, 30 Jul 2009 13:53:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/output-device-communication-error/m-p/4470238#M58517</guid>
      <dc:creator>NUVIC</dc:creator>
      <dc:date>2009-07-30T13:53:51Z</dc:date>
    </item>
    <item>
      <title>Re: Output device communication error</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/output-device-communication-error/m-p/4470239#M58518</link>
      <description>These are not DECnet messages, nor are these OpenVMS messages.  These appear to be application messages.  These may well be secondary to an OpenVMS or network error, but what that might be is not visible from what's been posted.&lt;BR /&gt;&lt;BR /&gt;The previous question posted here appears to have involved the Barco Graphics FastRip application package.  &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1328701" target="_blank"&gt;http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1328701&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If this is again the same package that's tossing errors, then for assistance with that application software package, you'll want to contact Barco directly.&lt;BR /&gt;&lt;BR /&gt;The Barco folks have a web site at:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.barco.com/" target="_blank"&gt;http://www.barco.com/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If this is not the same configuration, then more details will be required.  And as this looks to be application software, it's usually best to discuss these sorts of cases with the application vendor(s) or with a local application or system support resource. &lt;BR /&gt;&lt;BR /&gt;Also consider migrating to an operating system platform and/or to an application platform that you're more comfortable with supporting, or consider working with somebody (whether local or remote) that can assist you in troubleshooting and supporting and operating specific local application server platform(s).  OpenVMS doesn't need much on-going maintenance, but it definitely does need some.  And I'd expect Barco or most any other non-trivial application package can require some maintenance, too.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Jul 2009 16:06:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/output-device-communication-error/m-p/4470239#M58518</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-07-30T16:06:49Z</dc:date>
    </item>
  </channel>
</rss>

