- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- UCX Programming UDP
Operating System - OpenVMS
1745950
Members
4181
Online
108723
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
тАО09-27-2007 01:51 PM
тАО09-27-2007 01:51 PM
UCX Programming UDP
I got a problem with UCX. The communication (QIO) to a Windows XP system is not possible. The node/port is declared as UNREACHABLE.
The same program is working fine with a DOS box.
Is the UCX version 4.0 the main reason for that (as I expect). Do I have to upgrade the system? To which version? Where can I get it?
Any input is appreciated.
The same program is working fine with a DOS box.
Is the UCX version 4.0 the main reason for that (as I expect). Do I have to upgrade the system? To which version? Where can I get it?
Any input is appreciated.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2007 02:16 PM
тАО09-27-2007 02:16 PM
Re: UCX Programming UDP
Indiana,
IP is IP, it shouldn't matter what stack you're using to get basic stuff like reachability. That said, UCX 4.0 is very old, so it's probably a good idea to upgrade to a more recent version. You haven't mentioned what version of OpenVMS you're running, so I can't say what you should be looking for.
Kits are on the consolidated distribution, or (for TCPIP), on the layered products disk distributed with OpenVMS kits.
I'd be interested to see a program using $QIO that runs on a DOS system! Try some basic checks like:
$ UCX PING target-host
$ TELNET target-host
to see if your problem is systemic (ie: nothing works), or something specific to your program (the above will succeed to some extend, but your program still fails).
IP is IP, it shouldn't matter what stack you're using to get basic stuff like reachability. That said, UCX 4.0 is very old, so it's probably a good idea to upgrade to a more recent version. You haven't mentioned what version of OpenVMS you're running, so I can't say what you should be looking for.
Kits are on the consolidated distribution, or (for TCPIP), on the layered products disk distributed with OpenVMS kits.
I'd be interested to see a program using $QIO that runs on a DOS system! Try some basic checks like:
$ UCX PING target-host
$ TELNET target-host
to see if your problem is systemic (ie: nothing works), or something specific to your program (the above will succeed to some extend, but your program still fails).
A crucible of informative mistakes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2007 02:23 PM
тАО09-27-2007 02:23 PM
Re: UCX Programming UDP
> The node/port is declared as UNREACHABLE.
Who declares this, and how? Actual code and
actual status values might be more helpful
than colorful but vague descriptions.
Do other network operations (ping, Telnet,
traceroute, ...) between these systems work
or fail? (Actual commands with actual
output this time?)
> Is the UCX version 4.0 the main reason for
> that [...]
Probably depends on exactly what "that" is.
> To which version?
Probably depends on where you plan to put it.
> Where can I get it?
Probably depends on what it is. HP still
sells its products, I believe. Other folks
sell theirs.
Who declares this, and how? Actual code and
actual status values might be more helpful
than colorful but vague descriptions.
Do other network operations (ping, Telnet,
traceroute, ...) between these systems work
or fail? (Actual commands with actual
output this time?)
> Is the UCX version 4.0 the main reason for
> that [...]
Probably depends on exactly what "that" is.
> To which version?
Probably depends on where you plan to put it.
> Where can I get it?
Probably depends on what it is. HP still
sells its products, I believe. Other folks
sell theirs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2007 03:41 PM
тАО09-27-2007 03:41 PM
Re: UCX Programming UDP
Indiana Jones,
As has been mentioned, does PING and/or TRACEROUTE work? "Unreachable" implies a problem with either the specification of the network address or the underlying specification of the interfaces access to the network. More details about the network and the configuration of the interfaces (including IP address, subnet mask, gateway address, and any specified routes) would be extremely helpful.
- Bob Gezelter, http://www.rlgsc.com
As has been mentioned, does PING and/or TRACEROUTE work? "Unreachable" implies a problem with either the specification of the network address or the underlying specification of the interfaces access to the network. More details about the network and the configuration of the interfaces (including IP address, subnet mask, gateway address, and any specified routes) would be extremely helpful.
- 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