Don’t you just hate it when something breaks the build of your software? Build problems create extra, unplanned work.
Read More
Ever wonder how STCP knows what its name is? In the >system>stcp directory is a file called host.
The general rule of thumb when porting an open-source package is to keep track of the changes you make to get it to build and execute on your system, and if you think the changes would be useful to the community at large, to submit them to the maintainers of the package.
A journey that began nearly 30 years ago continues today for many Stratus customers with the release of Stratus OpenVOS 17.1, arguably the world’s most reliable operating system for running mission-critical applications.
Watch a technical training seminar about the recently announced fourth generation V Series platform/OpenVOS 17.1 and Kona for OpenVOS.
Prior to VOS 17.1 STCP would not accept a TCP connection request unless the server application had called the accept function.
I recently diagnosed an apparent compiler problem for an OpenVOS customer. He has two modules running OpenVOS Release 17.1.
I have recently ported several new or updated open-source packages to OpenVOS Release 17.1. They are now available on the VOS anonymous ftp site.
Under STCP when you have multiple processes listening on the same port number only the first process that bound to the port number is notified when a connection is requested.
The CAC is frequently asked to look into problems with VOS message queues. Here are a couple of interesting ones, along with some solutions and recommendations that I’d like to share with you.