<?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: VMS setsockopt permission failure in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/vms-setsockopt-permission-failure/m-p/5864355#M45920</link>
    <description>&lt;P&gt;Thank you for your attention to my question and the reference to the HP document.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I read a number of DEC/CPQ/HP OpenVMS documents related to TCP/sockets visible in the Internet, the reply "permission denied" was mentioned many times but without any comments which permissions were lacking. It happened that I did not meet the proper document. I have a set of VMS documentation on CDs but I am not sure in which document the required information could be located.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is a pity. By no means the target program should be run at elevated privileges, nor should it be installed as known image. I see the only way to increase the buffer size in TCPIP globally using TCPIP&amp;gt;sysconfig but this may lead to undesirable side effects with the other network applications.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you once again&lt;/P&gt;</description>
    <pubDate>Mon, 12 Nov 2012 17:44:41 GMT</pubDate>
    <dc:creator>alphacat</dc:creator>
    <dc:date>2012-11-12T17:44:41Z</dc:date>
    <item>
      <title>VMS setsockopt permission failure</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-setsockopt-permission-failure/m-p/5863341#M45918</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;When porting Linux networking code to OpenVMS 7.3-1, TCPIP 5.3-18 on XP1000,&lt;/P&gt;&lt;P&gt;the setsockopt function fails to set the size of send or receive buffer (unlike&amp;nbsp; Linux):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; . . . . .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; sock = socket(AF_INET,SOCK_STREAM,0);&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; . . . . .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; rbuf = 61440;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; /* just an example; this is the default */&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; retval = setsockopt(sock,SOL_SOCKET,SO_RCVBUF,&amp;amp;rbuf,sizeof(rbuf));&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; . . . . .&lt;/P&gt;&lt;P&gt;producing the message "permission denied". The other socket options are set successfully.&lt;/P&gt;&lt;P&gt;I wonder what permissions are necessary and why have I no full control on the socket I just created?&lt;/P&gt;&lt;P&gt;No information found in the Internet about privileges, protection codes, system parameters&lt;/P&gt;&lt;P&gt;concerning sockets in OpenVMS.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 11 Nov 2012 19:41:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-setsockopt-permission-failure/m-p/5863341#M45918</guid>
      <dc:creator>alphacat</dc:creator>
      <dc:date>2012-11-11T19:41:39Z</dc:date>
    </item>
    <item>
      <title>Re: VMS setsockopt permission failure</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-setsockopt-permission-failure/m-p/5863575#M45919</link>
      <description>&lt;P&gt;Have you looked at the VMS documentation?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="http://h71000.www7.hp.com/doc/82final/6529/6529pro_028.html#op_setsock_tab" target="_blank"&gt;http://h71000.www7.hp.com/doc/82final/6529/6529pro_028.html#op_setsock_tab&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To set SO_RCVBUF you must have SYSPRV, BYPASS or OPER privilege.&lt;/P&gt;&lt;P&gt;I image this would be because each socket buffer consumes system dynamic memory, but I could be mistaken.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jeremy Begg&lt;/P&gt;</description>
      <pubDate>Mon, 12 Nov 2012 04:08:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-setsockopt-permission-failure/m-p/5863575#M45919</guid>
      <dc:creator>Jeremy Begg</dc:creator>
      <dc:date>2012-11-12T04:08:08Z</dc:date>
    </item>
    <item>
      <title>Re: VMS setsockopt permission failure</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-setsockopt-permission-failure/m-p/5864355#M45920</link>
      <description>&lt;P&gt;Thank you for your attention to my question and the reference to the HP document.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I read a number of DEC/CPQ/HP OpenVMS documents related to TCP/sockets visible in the Internet, the reply "permission denied" was mentioned many times but without any comments which permissions were lacking. It happened that I did not meet the proper document. I have a set of VMS documentation on CDs but I am not sure in which document the required information could be located.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is a pity. By no means the target program should be run at elevated privileges, nor should it be installed as known image. I see the only way to increase the buffer size in TCPIP globally using TCPIP&amp;gt;sysconfig but this may lead to undesirable side effects with the other network applications.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you once again&lt;/P&gt;</description>
      <pubDate>Mon, 12 Nov 2012 17:44:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-setsockopt-permission-failure/m-p/5864355#M45920</guid>
      <dc:creator>alphacat</dc:creator>
      <dc:date>2012-11-12T17:44:41Z</dc:date>
    </item>
  </channel>
</rss>

