- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Evaluating Patches
Operating System - OpenVMS
1753416
Members
5683
Online
108793
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
тАО01-22-2007 07:45 AM
тАО01-22-2007 07:45 AM
Evaluating Patches
Does anyone know of a document that correlates the patch names to the module('s) affected? Additonaly does anyone know of a document that provides an overview of the modules and their function.
We read the release notes and pass on the info to our developers and QA. It would be helpful if more specific info could be supplied as to the effect of the patch being applied
Thank you
We read the release notes and pass on the info to our developers and QA. It would be helpful if more specific info could be supplied as to the effect of the patch being applied
Thank you
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2007 09:01 AM
тАО01-22-2007 09:01 AM
Re: Evaluating Patches
Usually the ECO Cover Letter includes what modules/images are affected by installing the particular kit.
As far as an overview of the modules is concerned, I'd start by looking through the VMS Doc. set.
Dave...
As far as an overview of the modules is concerned, I'd start by looking through the VMS Doc. set.
Dave...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2007 02:56 PM
тАО01-22-2007 02:56 PM
Re: Evaluating Patches
I am aware of no similar document available outside of HP OpenVMS Engineering.
You can construct your own local version of the image-level information, using the PCSI PRODUCT commands to extract the contents of the ECO kits, and cross-indexing these images with the information from the OpenVMS source listings. From that, you can work upwards to user APIs in some areas. Other images can and will have affects throughout the system environment, and won't have a single or visible user API associated with the API. Errors and changes within the modular executive images and within many of the core device drivers, for instance, can manifest themselves most anywhere in the environment.
If you're tracking back to what OpenVMS Engineering calls the source module level, then you'll definitely need access to internal HP details; that level of detail is not particularly available outside of HP. These source modules are the starting point for building or rebuilding OpenVMS itself, and you'll see listings of most of these on the source listings distributions.
I'd tend to look at the DEC test manager (DTM) or other such, and work on evaluating the application itself. With large applications, this can involve integrating debugging and testing support -- even if it's as simple as suppressing the details of the dates or the PID values or other such details that can through off DTM-level comparisons -- can be quite useful. For many applications, a DTM test suite can be used periodically and potentially even automatically. From the DTM suite, direct testing of the application and indirect testing of the ECOs...
Not the answer that you want, I expect.
You can construct your own local version of the image-level information, using the PCSI PRODUCT commands to extract the contents of the ECO kits, and cross-indexing these images with the information from the OpenVMS source listings. From that, you can work upwards to user APIs in some areas. Other images can and will have affects throughout the system environment, and won't have a single or visible user API associated with the API. Errors and changes within the modular executive images and within many of the core device drivers, for instance, can manifest themselves most anywhere in the environment.
If you're tracking back to what OpenVMS Engineering calls the source module level, then you'll definitely need access to internal HP details; that level of detail is not particularly available outside of HP. These source modules are the starting point for building or rebuilding OpenVMS itself, and you'll see listings of most of these on the source listings distributions.
I'd tend to look at the DEC test manager (DTM) or other such, and work on evaluating the application itself. With large applications, this can involve integrating debugging and testing support -- even if it's as simple as suppressing the details of the dates or the PID values or other such details that can through off DTM-level comparisons -- can be quite useful. For many applications, a DTM test suite can be used periodically and potentially even automatically. From the DTM suite, direct testing of the application and indirect testing of the ECOs...
Not the answer that you want, I expect.
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