- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- data over run in decnet task to task communication
Operating System - OpenVMS
1753781
Members
7444
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО05-11-2009 12:03 AM
тАО05-11-2009 12:03 AM
data over run in decnet task to task communication
Hi
I have decnet task to task communication, where say process x communicates with process y. Process x writes into mailbox some data and process y reads that data from mailbox. All this is implemented using sys$qiow system call. I getting error "%SYSTEM-W-DATAOVERUN, data overrun".
I traced the reason for this error, every where they are suggesting to increase the RMS buffer using set rms_default /networkblockcount. I have tried that but no success.
Same code worked for many years and now it is causing the problem. Seems strange, not able to figure out the problem.
Could any one help me in solving this.
I have decnet task to task communication, where say process x communicates with process y. Process x writes into mailbox some data and process y reads that data from mailbox. All this is implemented using sys$qiow system call. I getting error "%SYSTEM-W-DATAOVERUN, data overrun".
I traced the reason for this error, every where they are suggesting to increase the RMS buffer using set rms_default /networkblockcount. I have tried that but no success.
Same code worked for many years and now it is causing the problem. Seems strange, not able to figure out the problem.
Could any one help me in solving this.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 01:17 AM
тАО05-11-2009 01:17 AM
Re: data over run in decnet task to task communication
If you're using $QIOWs, then you're NOT using RMS. This is why setting an RMS parameter does not help.
Can you identify the failing QIOW in your code ? Run the program with the debugger and check all parameters. Find out, how much data the other side has actually sent.
Volker.
Can you identify the failing QIOW in your code ? Run the program with the debugger and check all parameters. Find out, how much data the other side has actually sent.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 01:30 AM
тАО05-11-2009 01:30 AM
Re: data over run in decnet task to task communication
hi
process x sends request using sys$qiow.
Process y reads the request as shown below
vf_l_status = SYS$QIOW(,%VAL(vh_t_lnkchn), %VAL(IO$_READVBLK),
vg_t_central_io,,,
%REF(vg_t_oprequest),
%VAL(kh_t_cdmrequestlen),,,,)
vg_t_central_io.vh_iosb_iosts) is giving data over flow error during run time.
If its not RMS what could be the problem for data over run.
process x sends request using sys$qiow.
Process y reads the request as shown below
vf_l_status = SYS$QIOW(,%VAL(vh_t_lnkchn), %VAL(IO$_READVBLK),
vg_t_central_io,,,
%REF(vg_t_oprequest),
%VAL(kh_t_cdmrequestlen),,,,)
vg_t_central_io.vh_iosb_iosts) is giving data over flow error during run time.
If its not RMS what could be the problem for data over run.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2009 02:40 AM
тАО05-11-2009 02:40 AM
Re: data over run in decnet task to task communication
Ravikanth,
Please review the relevant material in the Guide to Networking.
Unlike TCP, which is stream-based, DECnet task level communictions (using NSP) is message based. The entire message must fit within the buffer.
Check the length of the message sent, and check the size of the receiving buffer. Check the documentation, the IOSB will contain details.
- Bob Gezelter, http://www.rlgsc.com
Please review the relevant material in the Guide to Networking.
Unlike TCP, which is stream-based, DECnet task level communictions (using NSP) is message based. The entire message must fit within the buffer.
Check the length of the message sent, and check the size of the receiving buffer. Check the documentation, the IOSB will contain details.
- Bob Gezelter, http://www.rlgsc.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP