- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- C++ problem with %CXX-E-INCOMPLETETYP
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
07-15-2011 07:57 AM
07-15-2011 07:57 AM
Re: C++ problem with %CXX-E-INCOMPLETETYP
Pull the files and diff'm, if you're interested in changes. Between this libxext procedure and this directory-differences tool, you should have the tools that deal with everything you need here to differences the old and the new libraries.
And FWIW, the typical (modern) approach when dealing with HP OpenVMS or other Enterprise software is to contact the vendor's support center directly, and get the updates. (When you have support, obviously.) HP clearly prefers this approach, and (when the initial basic Google search that is an inherent part of researching most any problem turns up nothing) this direct-to-support approach is (usually) the fastest approach to get your issues resolved or your servers back online. Asking questions in forums (if Google turns up nothing) (usually) just delays the resolution. Somebody (like me) will usually just tell you "call HP", and you can cut to the chase yourself.
What's also involved and somewhat more subtle, HP also uses these reports to prioritize and generate and push out kits with fixes. The more times a bug is reported, the more likely that the fix will be a patch. (Shipping out isolated files is comparatively problematic; folks can make mistakes with the installations (copying the file to the SYS$SPECIFIC directory, for instance), and there's no integrated tracking of hand-installed images.)
- « Previous
-
- 1
- 2
- Next »