<?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: SFTP and large files in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189643#M58530</link>
    <description>Packet too long?  I would interpret this as a statement that you have mismatched network settings on sender vs. receiever.  In LANCP, you should be able to show the device characteristics as&lt;BR /&gt;&lt;BR /&gt;$ MC LANCP SHOW DEVICE/CHAR devname&lt;BR /&gt;&lt;BR /&gt;The questions I would ask include whether the device buffer sizes match (but these are negotiated so SHOULDN'T give trouble) and whether the partner node has jumbo frames enabled.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 05 Aug 2009 14:23:44 GMT</pubDate>
    <dc:creator>Richard W Hunt</dc:creator>
    <dc:date>2009-08-05T14:23:44Z</dc:date>
    <item>
      <title>SFTP and large files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189636#M58523</link>
      <description>We have a site running OpenVMS V8.3-1h1, TCPIP 5.6 ECO 4 that is trying to SFTP files from a non-VMS site. When trying to get some of the large files, SFTP terminates with an error of "packet too long".&lt;BR /&gt;&lt;BR /&gt;I can't find any restrictions on transferring large files. The only thing I found in the release notes said:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;3.10.14 SSH Transferring Large Files&lt;BR /&gt;&lt;BR /&gt;This section includes restrictions pertaining to transferring large files:&lt;BR /&gt;&lt;BR /&gt;    * The minimum version of DECC$SHR running on your system must be that which was released with OpenVMS Version 8.2.&lt;BR /&gt;    * You may need to adjust memory parameters (WSDEF, WSQUO, WSEXTENT, and PGFLQUO) to accommodate the memory requirements of the file copy client and server. The exact value depends on system resources and virtual memory configuration. For more information, see Section 2.3. For ssh filecopy, testing has shown that the main parameter to adjust is PGFLQUO.  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Another strange thing is that if you try the GET multiple times, the number reported in the "packet too long" message varies.&lt;BR /&gt;&lt;BR /&gt;Here is output from one such GET:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;sftp&amp;gt; ls -l&lt;BR /&gt;drwxrw-rw-   1 user     group           0 Jul 13 10:44 archive&lt;BR /&gt;-rw-rw-rw-   1 user     group        7942 Jul 25 00:54 dly0967&lt;BR /&gt;-rw-rw-rw-   1 user     group        4332 Apr 28 00:52 dly0967.04272009&lt;BR /&gt;-rw-rw-rw-   1 user     group       22382 May  2 01:07 dly0967.05012009&lt;BR /&gt;-rw-rw-rw-   1 user     group        4332 May  6 00:55 dly0967.05052009&lt;BR /&gt;-rw-rw-rw-   1 user     group        1083 May  8 00:54 dly0967.05072009&lt;BR /&gt;-rw-rw-rw-   1 user     group        4332 May 14 00:54 dly0967.05132009&lt;BR /&gt;-rw-rw-rw-   1 user     group        1444 May 15 00:58 dly0967.05142009&lt;BR /&gt;-rw-rw-rw-   1 user     group        1444 May 19 00:54 dly0967.05182009&lt;BR /&gt;-rw-rw-rw-   1 user     group       34295 Jun  2 01:30 dly0967.06012009&lt;BR /&gt;-rw-rw-rw-   1 user     group        4332 Jun  3 00:59 dly0967.06022009&lt;BR /&gt;-rw-rw-rw-   1 user     group        1083 Jun  4 00:58 dly0967.06032009&lt;BR /&gt;-rw-rw-rw-   1 user     group        4332 Jun 10 00:54 dly0967.06092009&lt;BR /&gt;-rw-rw-rw-   1 user     group        4693 Jun 19 00:55 dly0967.06182009&lt;BR /&gt;-rw-rw-rw-   1 user     group        4332 Jul  2 01:15 dly0967.07012009&lt;BR /&gt;-rw-rw-rw-   1 user     group        1083 Jul 10 01:03 dly0967.07092009&lt;BR /&gt;-rw-rw-rw-   1 user     group        7942 Jul 11 00:56 dly0967.07102009&lt;BR /&gt;-rw-rw-rw-   1 user     group        4332 Jul 15 00:58 dly0967.07142009&lt;BR /&gt;-rw-rw-rw-   1 user     group        3971 Jul 16 00:58 dly0967.07152009&lt;BR /&gt;-rw-rw-rw-   1 user     group        1083 Jul 21 00:56 dly0967.07202009&lt;BR /&gt;-rw-rw-rw-   1 user     group        7942 Jul 24 00:55 dly0967.07232009&lt;BR /&gt;-rw-rw-rw-   1 user     group        7942 Jul 25 00:54 dly0967.07242009&lt;BR /&gt;-rw-rw-rw-   1 user     group           0 Jul  6 13:10 ERS&lt;BR /&gt;-rw-rw-rw-   1 user     group       93670 Jun  3 19:18 findtl0967.01012009&lt;BR /&gt;-rw-rw-rw-   1 user     group       94010 May 15 14:55 findtl0967.04012009&lt;BR /&gt;-rw-rw-rw-   1 user     group       93840 Jun 15 16:53 findtl0967.05012009&lt;BR /&gt;-rw-rw-rw-   1 user     group       94180 Jul 13 13:52 findtl0967.06012009&lt;BR /&gt;-rw-rw-rw-   1 user     group       92480 Jun  3 19:14 findtl0967.09012008&lt;BR /&gt;-rw-rw-rw-   1 user     group       92480 Jun  3 19:15 findtl0967.10012008&lt;BR /&gt;-rw-rw-rw-   1 user     group       92990 Jun  3 19:16 findtl0967.11012008&lt;BR /&gt;-rw-rw-rw-   1 user     group       92820 Jun  3 19:17 findtl0967.12012008&lt;BR /&gt;-rw-rw-rw-   1 user     group     1328119 May 10 11:50 mth0967.04302009&lt;BR /&gt;-rw-rw-rw-   1 user     group     1325592 Jun  9 16:36 mth0967.05312009&lt;BR /&gt;-rw-rw-rw-   1 user     group     1324509 Jul  9 18:23 mth0967.06302009&lt;BR /&gt;-rw-rw-rw-   1 user     group       87252 Jul  9 16:51 mthretfml0967&lt;BR /&gt;-rw-rw-rw-   1 user     group       86592 May 10 06:09 mthretfml0967.04302009&lt;BR /&gt;-rw-rw-rw-   1 user     group       86592 Jun  9 14:54 mthretfml0967.05312009&lt;BR /&gt;-rw-rw-rw-   1 user     group       87252 Jul  9 16:51 mthretfml0967.06302009&lt;BR /&gt;-rw-rw-rw-   1 user     group         492 Jul 13 10:43 o967457.old&lt;BR /&gt;-rw-rw-rw-   1 user     group         106 Jul  1 10:32 o967dcp&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;sftp&amp;gt; get mth0967.06302009&lt;BR /&gt;&lt;BR /&gt;Disconnected; protocol error (Protocol error: packet too long: 64372.).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Warning: child process (/sys$system/tcpip$ssh_ssh2) exited with code 131.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;%TCPIP-E-SSH_FC_ERROR, error in ssh file transfer operation&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Any suggestions ?</description>
      <pubDate>Mon, 27 Jul 2009 14:36:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189636#M58523</guid>
      <dc:creator>Allan Large</dc:creator>
      <dc:date>2009-07-27T14:36:47Z</dc:date>
    </item>
    <item>
      <title>Re: SFTP and large files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189637#M58524</link>
      <description>Forgot to add that we can get the files that are 94,000 bytes just fine.</description>
      <pubDate>Mon, 27 Jul 2009 14:39:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189637#M58524</guid>
      <dc:creator>Allan Large</dc:creator>
      <dc:date>2009-07-27T14:39:33Z</dc:date>
    </item>
    <item>
      <title>Re: SFTP and large files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189638#M58525</link>
      <description>Found this (not the samer but comparable):&lt;BR /&gt;I've successfully tested TCPIP V5.4 ECO7J and V5.6 ECO2M ssh images and ls no longer results in "packet too long" and gets a successful listing. &lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Mon, 27 Jul 2009 14:56:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189638#M58525</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2009-07-27T14:56:53Z</dc:date>
    </item>
    <item>
      <title>Re: SFTP and large files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189639#M58526</link>
      <description>And do you know how would one go about obtaining the V5.6 ECO2M images ?</description>
      <pubDate>Mon, 27 Jul 2009 15:11:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189639#M58526</guid>
      <dc:creator>Allan Large</dc:creator>
      <dc:date>2009-07-27T15:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: SFTP and large files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189640#M58527</link>
      <description>&lt;!--!*#--&gt;&amp;gt; And do you know how would one go about&lt;BR /&gt;&amp;gt; obtaining the V5.6 ECO2M images ?&lt;BR /&gt;&lt;BR /&gt;Perhaps:&lt;BR /&gt;&lt;A href="ftp://ftp.itrc.hp.com/openvms_patches/layered_products/i64/" target="_blank"&gt;ftp://ftp.itrc.hp.com/openvms_patches/layered_products/i64/&lt;/A&gt;&lt;BR /&gt;?&lt;BR /&gt;&lt;BR /&gt;I don't know about the "J" and "M". but there&lt;BR /&gt;seems to be "HP TCP/IP Services for OpenVMS&lt;BR /&gt;V5.6 Update ECO 4" there.</description>
      <pubDate>Mon, 27 Jul 2009 15:36:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189640#M58527</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2009-07-27T15:36:56Z</dc:date>
    </item>
    <item>
      <title>Re: SFTP and large files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189641#M58528</link>
      <description>If it's not posted, call HP.</description>
      <pubDate>Mon, 27 Jul 2009 15:43:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189641#M58528</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-07-27T15:43:04Z</dc:date>
    </item>
    <item>
      <title>Re: SFTP and large files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189642#M58529</link>
      <description>Not sure if it will be the same, but we had the same issue. Currently:&lt;BR /&gt;Openvms 8.3 Alpha&lt;BR /&gt;TCPIP V5.6 - ECO 3&lt;BR /&gt;&lt;BR /&gt;What we do is convert the file to Stream_LF and that fixed the problem.&lt;BR /&gt;&lt;BR /&gt;Contents of strem_lf.fdl:&lt;BR /&gt;SYSTEM&lt;BR /&gt;        SOURCE                  OpenVMS&lt;BR /&gt;&lt;BR /&gt;FILE&lt;BR /&gt;        ORGANIZATION            SEQUENTIAL&lt;BR /&gt;&lt;BR /&gt;RECORD&lt;BR /&gt;        BLOCK_SPAN              yes&lt;BR /&gt;        CARRIAGE_CONTROL        carriage_return&lt;BR /&gt;        FORMAT                  stream_LF&lt;BR /&gt;        SIZE                    0&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Jul 2009 12:27:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189642#M58529</guid>
      <dc:creator>James T Horn</dc:creator>
      <dc:date>2009-07-28T12:27:07Z</dc:date>
    </item>
    <item>
      <title>Re: SFTP and large files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189643#M58530</link>
      <description>Packet too long?  I would interpret this as a statement that you have mismatched network settings on sender vs. receiever.  In LANCP, you should be able to show the device characteristics as&lt;BR /&gt;&lt;BR /&gt;$ MC LANCP SHOW DEVICE/CHAR devname&lt;BR /&gt;&lt;BR /&gt;The questions I would ask include whether the device buffer sizes match (but these are negotiated so SHOULDN'T give trouble) and whether the partner node has jumbo frames enabled.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Aug 2009 14:23:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189643#M58530</guid>
      <dc:creator>Richard W Hunt</dc:creator>
      <dc:date>2009-08-05T14:23:44Z</dc:date>
    </item>
    <item>
      <title>Re: SFTP and large files</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189644#M58531</link>
      <description>Thanks everyone for the suggestions.&lt;BR /&gt;&lt;BR /&gt;What we found was that the server side of the connection is Globalscape's FTP server. This particular version didn't honor the packet size requested from VMS and thus an error occurred.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.globalscape.com/tm.aspx?m=15249&amp;amp;mpage=1&amp;amp;key=packet%2ctoo%2clong" target="_blank"&gt;http://forums.globalscape.com/tm.aspx?m=15249&amp;amp;mpage=1&amp;amp;key=packet%2ctoo%2clong&lt;/A&gt;㮘</description>
      <pubDate>Wed, 05 Aug 2009 14:28:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sftp-and-large-files/m-p/5189644#M58531</guid>
      <dc:creator>Allan Large</dc:creator>
      <dc:date>2009-08-05T14:28:57Z</dc:date>
    </item>
  </channel>
</rss>

