<?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 ftp server connection log file creation error in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189136#M56428</link>
    <description>::Thanks everyone for replying. Remotely supporting a system that others administer can be a pain.::&lt;BR /&gt;&lt;BR /&gt;I deal with these case quite regularly as part of normal support operations.  &lt;BR /&gt;&lt;BR /&gt;It's no big deal, save for those cases that require direct hardware reconfiguration or reading off LEDs or such.  &lt;BR /&gt;&lt;BR /&gt;I prefer to concentrate the general set-up effort up front.  This when everybody involved is awake, aware, properly caffeinated, and not in a hurry or a panic, and when the gear can be staged.  This set-up work includes setting up for remote access via network (via VPN or otherwise) and (if you're supporting the system to this level) setting up remote console access.   When working with OpenVMS support, I also prefer to have a scratch disk available, or to have access to a (host-based) InfoServer, or both. &lt;BR /&gt;&lt;BR /&gt;As part of remote support, having a local box or having a local emulation or such can be useful for testing cases such as this one.&lt;BR /&gt;&lt;BR /&gt;Once established, remote boxes aren't a big deal.&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs LLC</description>
    <pubDate>Wed, 30 Apr 2008 12:35:52 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2008-04-30T12:35:52Z</dc:date>
    <item>
      <title>OpenVMS ftp server connection log file creation error</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189131#M56423</link>
      <description>We dropped the ball recently and let the connection log file version reach 32767.  What is the expected behavior of the ftp server if this log file cannot be created?  I thought the connection would be refused, but others in the group say no.&lt;BR /&gt;We are running OpenVMS 7.3.2 TCPIP 5.4</description>
      <pubDate>Wed, 30 Apr 2008 00:21:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189131#M56423</guid>
      <dc:creator>David Hinrichs</dc:creator>
      <dc:date>2008-04-30T00:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS ftp server connection log file creation error</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189132#M56424</link>
      <description>Respectfully, why ask here?  It would seem faster to RENAME the current top log version to the specified ;32767 version and to try it.&lt;BR /&gt;&lt;BR /&gt;I'd expect the connection to operate, but to not create a log.  (Setting the file version to ;32767 has been a popular and long-standing way to disable the creation of log files, but this technique doesn't work in all cases.)&lt;BR /&gt;&lt;BR /&gt;Or is this a quiz?&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Apr 2008 01:26:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189132#M56424</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2008-04-30T01:26:08Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS ftp server connection log file creation error</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189133#M56425</link>
      <description>It's like Hoff said : it works but no further log is created.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 30 Apr 2008 06:34:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189133#M56425</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2008-04-30T06:34:40Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS ftp server connection log file creation error</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189134#M56426</link>
      <description>We call a special procedure during login to avoid such situations, it purges and/or renames selectable logfiles. I attached it to give you an idea.&lt;BR /&gt;&lt;BR /&gt;regards Kalle</description>
      <pubDate>Wed, 30 Apr 2008 07:29:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189134#M56426</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2008-04-30T07:29:50Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS ftp server connection log file creation error</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189135#M56427</link>
      <description>Thanks everyone for replying. Remotely supporting a system that others administer can be a pain.</description>
      <pubDate>Wed, 30 Apr 2008 11:06:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189135#M56427</guid>
      <dc:creator>David Hinrichs</dc:creator>
      <dc:date>2008-04-30T11:06:22Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS ftp server connection log file creation error</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189136#M56428</link>
      <description>::Thanks everyone for replying. Remotely supporting a system that others administer can be a pain.::&lt;BR /&gt;&lt;BR /&gt;I deal with these case quite regularly as part of normal support operations.  &lt;BR /&gt;&lt;BR /&gt;It's no big deal, save for those cases that require direct hardware reconfiguration or reading off LEDs or such.  &lt;BR /&gt;&lt;BR /&gt;I prefer to concentrate the general set-up effort up front.  This when everybody involved is awake, aware, properly caffeinated, and not in a hurry or a panic, and when the gear can be staged.  This set-up work includes setting up for remote access via network (via VPN or otherwise) and (if you're supporting the system to this level) setting up remote console access.   When working with OpenVMS support, I also prefer to have a scratch disk available, or to have access to a (host-based) InfoServer, or both. &lt;BR /&gt;&lt;BR /&gt;As part of remote support, having a local box or having a local emulation or such can be useful for testing cases such as this one.&lt;BR /&gt;&lt;BR /&gt;Once established, remote boxes aren't a big deal.&lt;BR /&gt;&lt;BR /&gt;Stephen Hoffman&lt;BR /&gt;HoffmanLabs LLC</description>
      <pubDate>Wed, 30 Apr 2008 12:35:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/openvms-ftp-server-connection-log-file-creation-error/m-p/4189136#M56428</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2008-04-30T12:35:52Z</dc:date>
    </item>
  </channel>
</rss>

