- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- VMS setsockopt permission failure
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2012 11:41 AM
11-11-2012 11:41 AM
Hi everyone,
When porting Linux networking code to OpenVMS 7.3-1, TCPIP 5.3-18 on XP1000,
the setsockopt function fails to set the size of send or receive buffer (unlike Linux):
. . . . .
sock = socket(AF_INET,SOCK_STREAM,0);
. . . . .
rbuf = 61440; /* just an example; this is the default */
retval = setsockopt(sock,SOL_SOCKET,SO_RCVBUF,&rbuf,sizeof(rbuf));
. . . . .
producing the message "permission denied". The other socket options are set successfully.
I wonder what permissions are necessary and why have I no full control on the socket I just created?
No information found in the Internet about privileges, protection codes, system parameters
concerning sockets in OpenVMS.
Thanks
Solved! Go to Solution.
- Tags:
- Permission
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2012 08:08 PM
11-11-2012 08:08 PM
SolutionHave you looked at the VMS documentation?
http://h71000.www7.hp.com/doc/82final/6529/6529pro_028.html#op_setsock_tab
To set SO_RCVBUF you must have SYSPRV, BYPASS or OPER privilege.
I image this would be because each socket buffer consumes system dynamic memory, but I could be mistaken.
Regards,
Jeremy Begg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2012 09:26 AM - edited 11-12-2012 09:44 AM
11-12-2012 09:26 AM - edited 11-12-2012 09:44 AM
Re: VMS setsockopt permission failure
Thank you for your attention to my question and the reference to the HP document.
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.
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>sysconfig but this may lead to undesirable side effects with the other network applications.
Thank you once again