<?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: OpenVMS Alpha 8.3 DECnet Phase 4 file close delay in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083605#M55796</link>
    <description>Jim,&lt;BR /&gt;&lt;BR /&gt;COPY uses RMS, so consider to compare the RMS sysgen parameters (SYSGEN&amp;gt; SHOW/RMS and $ SHOW RMS).&lt;BR /&gt;&lt;BR /&gt;On the remote node, you could enable FAL logging:&lt;BR /&gt;&lt;BR /&gt;$ DEFINE/SYSTEM FAL$LOG FFFF&lt;BR /&gt;&lt;BR /&gt;Make sure the NETSERVER process has disappeared, then try the COPY command again. The FAL$LOG output will show up in the remote NETSERVER.LOG file in the login-directory of the remote user. Maybe you can at least spot the 30-second delay. Then it's time to think about what may be causing this.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
    <pubDate>Mon, 10 Dec 2007 18:58:13 GMT</pubDate>
    <dc:creator>Volker Halle</dc:creator>
    <dc:date>2007-12-10T18:58:13Z</dc:date>
    <item>
      <title>OpenVMS Alpha 8.3 DECnet Phase 4 file close delay</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083602#M55793</link>
      <description>I am seeing an unusual delay in DECnet phase IV activity when the source is one of our OpenVMS 8.3 systems. This delay takes place when copying files from a system named HCPT to any other OpenVMS system. All of the systems are running OpenVMS Alpha 8.3. I am confident that this problem did not exist when we were running OpenVMS Alpha 7.3-2.&lt;BR /&gt;&lt;BR /&gt;Here is an example of the problem: I can copy a 93-block file called ucount.exe from HCPT to another system called HCPA. Using Control-T shows that 100% of the blocks are copied (93 blocks copied of 93), but on HCPA I see that the EOF is still at 0 and then there is an almost 30-second delay before the file is closed and the command completes. The target disk is not active, and if I copy the same file to a system with no users and almost no activity, the same delay occurs. If I repeat the command immediately to take advantage of the now-existing NETSERVER process, there is no change -- the same delay takes place.&lt;BR /&gt;&lt;BR /&gt;If I copy the same file to HCPT, the command completes in about a second. The problem seems to be copying files from HCPT to any of the OpenVMS Alpha 8.3 systems, strongly suggesting that something is different with HCPT. When I copy the same file from any OpenVMS system other than HCPT to any other OpenVMS system, the command completes within about a second. All of the systems are in the same DECnet area, and I have verified that the DECnet name-to-address lists are consistent (ncp list known nodes, show known nodes).&lt;BR /&gt;&lt;BR /&gt;How can I determine the cause and solution to this problem?</description>
      <pubDate>Mon, 10 Dec 2007 18:37:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083602#M55793</guid>
      <dc:creator>Jim Geier_1</dc:creator>
      <dc:date>2007-12-10T18:37:50Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Alpha 8.3 DECnet Phase 4 file close delay</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083603#M55794</link>
      <description>DECnet's FAL object has a debug option which might be useful here. See &lt;A href="http://www.decus.org/libcatalog/document_html/vs0174_39.html" target="_blank"&gt;http://www.decus.org/libcatalog/document_html/vs0174_39.html&lt;/A&gt; for details on activating it.</description>
      <pubDate>Mon, 10 Dec 2007 18:51:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083603#M55794</guid>
      <dc:creator>Jim_McKinney</dc:creator>
      <dc:date>2007-12-10T18:51:42Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Alpha 8.3 DECnet Phase 4 file close delay</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083604#M55795</link>
      <description>Jim,&lt;BR /&gt;&lt;BR /&gt;Before going any further, I would recommend verifying that the duplex settings are correct on the network adapter AND the switch that the system is connected to.&lt;BR /&gt;&lt;BR /&gt;In several client situations, I have seen Full/Half duplex mismatches produce "interesting" symptoms such as these. Small differences in the underlying software affect the collision rate.&lt;BR /&gt;&lt;BR /&gt;Along this line, what are the error counters throughout the network path involved?&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Mon, 10 Dec 2007 18:54:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083604#M55795</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2007-12-10T18:54:26Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Alpha 8.3 DECnet Phase 4 file close delay</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083605#M55796</link>
      <description>Jim,&lt;BR /&gt;&lt;BR /&gt;COPY uses RMS, so consider to compare the RMS sysgen parameters (SYSGEN&amp;gt; SHOW/RMS and $ SHOW RMS).&lt;BR /&gt;&lt;BR /&gt;On the remote node, you could enable FAL logging:&lt;BR /&gt;&lt;BR /&gt;$ DEFINE/SYSTEM FAL$LOG FFFF&lt;BR /&gt;&lt;BR /&gt;Make sure the NETSERVER process has disappeared, then try the COPY command again. The FAL$LOG output will show up in the remote NETSERVER.LOG file in the login-directory of the remote user. Maybe you can at least spot the 30-second delay. Then it's time to think about what may be causing this.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Mon, 10 Dec 2007 18:58:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083605#M55796</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2007-12-10T18:58:13Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Alpha 8.3 DECnet Phase 4 file close delay</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083606#M55797</link>
      <description>Thanks Bob -- I have been focusing so much on isolating and defining the problem from the software and DECnet perspective that I had forgotten to check the duplex settings in LANCP, something so obvious. That was the problem: the switch ports are hard-coded to 100-full, and the adapter was set to autonegotiate, and that never (in my experience) results in a good match. LANCP reported that full duplex was enabled but not operational. I was able to correct the problem with no downtime using LANCP with the commands&lt;BR /&gt;&lt;BR /&gt;&amp;gt; set ewa0 /noautonegotiate/full/speed=100&lt;BR /&gt;&amp;gt; set ewb0 /noautonegotiate/full/speed=100&lt;BR /&gt;&lt;BR /&gt;This system, an AlphaServer ES40, had the system board replaced about 7-8 weeks ago, so my guess is that the ew* settings were not scrutinized as carefully as they should have been when the hardware testing was completed.</description>
      <pubDate>Mon, 10 Dec 2007 19:47:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083606#M55797</guid>
      <dc:creator>Jim Geier_1</dc:creator>
      <dc:date>2007-12-10T19:47:18Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Alpha 8.3 DECnet Phase 4 file close delay</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083607#M55798</link>
      <description>Network adapter duplex setting was inconsistent with switch port setting as Bob suggested. Solution was applied with no downtime to system.</description>
      <pubDate>Mon, 10 Dec 2007 19:49:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-alpha-8-3-decnet-phase-4-file-close-delay/m-p/5083607#M55798</guid>
      <dc:creator>Jim Geier_1</dc:creator>
      <dc:date>2007-12-10T19:49:26Z</dc:date>
    </item>
  </channel>
</rss>

