Managing Software Changes Abstract This manual introduces the TRM2000 release model and how it defines the distribution of HP NonStop™ software products. This manual also explains the software installation, upgrade, and maintenance processes, including related documents, services, and tools. It provides information on how to decide which release version updates (RVUs) and software product revisions (SPRs) have value for your installation. Product Version N.A.
Document History Part Number Product Version Published 427169-001 N.A. November 2000 427169-002 N.A. August 2002 427169-003 N.A. December 2002 427169-004 N.A. December 2004 427169-005 N.A.
Managing Software Changes Glossary Index What’s New in This Manual v Manual Information v New and Changed Information Examples Tables v About This Manual vii Who Should Read This Manual vii Purpose vii Organization of This Manual viii Related Reading ix Notation Conventions x Abbreviations x 1.
2. Resources for Managing RVUs and SPRs (continued) Contents 2.
4. Software Installation Planning Contents 4.
B. What Is in an SPR Note Contents B. What Is in an SPR Note SPR Introduction Document (SID) SID Example B-1 SID Fields B-2 Softdoc B-4 DSV Information B-5 SPR Note Example B-6 B-1 C. SPR Research Form D. How to Use a Content File Content File Details D-1 Included SPRs D-1 Excluded SPRs D-3 Using the Content File to Research a New RVU D-4 Researching SPRs D-4 Researching the Differences Between RVUs D-4 Researching SPR Regressions D-6 E.
What’s New in This Manual Manual Information Managing Software Changes Abstract This manual introduces the TRM2000 release model and how it defines the distribution of HP NonStop™ software products. This manual also explains the software installation, upgrade, and maintenance processes, including related documents, services, and tools. It provides information on how to decide which release version updates (RVUs) and software product revisions (SPRs) have value for your installation. Product Version N.A.
New and Changed Information What’s New in This Manual • Information for NonStop Technical Library (NTL) has been updated to add H-series RVUs.
About This Manual This manual serves as an introduction and reference to the HP NonStop TRM2000 release model, the software upgrade process, software product revision (SPR) analysis, and resources for investigating new release version updates (RVUs) and SPRs.
Organization of This Manual About This Manual Organization of This Manual It is recommended that the first-time reader read through the entire manual and then refer to it as needed. • • • • • • • • • • • Section 1, Release Management Overview, introduces the concept of managing RVUs and SPRs within the context of TRM2000. Section 2, Resources for Managing RVUs and SPRs, describes available products, services, and documentation for evaluating and managing RVUs and SPRs.
Related Reading About This Manual Related Reading For each RVU, the manuals in the NonStop Technical Library (NTL) Publications “Release and Migration Information” section contain RVU and system-specific planning, configuration, and installation information.
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. lowercase italic letters.
1 Release Management Overview HP periodically makes available collections of new and revised versions of its software products called release version updates (RVUs). RVUs consist of software object modules; data files containing information such as configuration data, error text, and examples; and the documentation for the product revisions, in addition to a set of documentation for the overall RVU. Between RVUs, HP makes available time-critical fixes when required.
Software Products Release Management Overview Software Products A software product consists of one or more product versions (PVs) which are composed of product version updates (PVUs). Only PVUs are distributed. Product Identifiers T1234G06AAA Product Product Version Product Number ID Version ID Update ID VST022.vsd Product Number A set of product version updates that share the same software component identifier (Tnnnn).
Release Management Overview Independent Products Initial and Successive PVUs Example T1234G05 Initial PVU Product Version T1234AAC Successive PVU T1234AAD Successive PVU T1234AAF Successive PVU Product Version T1234G06 Initial PVU T1234AAG Successive PVU VST010.vsd Independent Products An Independent Product (IP) is independent from the standard software release and delivery process and is generally delivered on media separate from that of other NonStop operating system software.
Release Management Overview Software Product Revisions (SPRs) SPR Attributes Delivery • Planned product maintenance (PPM) New features are normally first made available with an RVU before being released in a stand-alone SPR to ensure that they have been sufficiently integration tested for the RVU. Planned product maintenance SPRs usually also include rolled-up time-critical fix SPRs and defect repair or product enhancements that are not time-critical fixes.
Release Management Overview Software Product Revisions (SPRs) unrestricted access. In rare situations, a defect repair will work correctly only under certain conditions, and access is therefore restricted. A restricted SPR that supersedes an unrestricted SPR contains all the features and fixes present in that SPR. If you do not need a fix specific to the restricted SPR, you can install the superseded unrestricted SPR.
Release Management Overview Software Product Revisions (SPRs) Requisite SPRs There are two types of requisite SPRs: • • One type provides specific function or data that must be present in your software configuration for a specific fix or feature in a requiring SPR to be fully functional if you use the requisite product. The other type is required when using the requiring SPR to maintain compatibility, because the requiring SPR removed function on which another product depends.
Release Management Overview Recalled, Withdrawn, and Obsolete SPRs Recalled, Withdrawn, and Obsolete SPRs It is sometimes necessary or preferable to stop distributing an SPR. SPRs that are no longer available are classified as recalled, withdrawn, or obsolete: • • • A recalled SPR either contains a defect that, under certain conditions, could cause serious problems–a system outage or inaccurate operations results–or prevent normal operation of the system or applications.
Release Management Overview Software Releases Software Releases Release Identifiers H06.10.01 Release Release Release Release Version Series ID Version ID Version Update ID Update Revision ID VST020.vsd Release Series A new release series designates a major architectural change from the previous release series. A release series consists of release versions (RVs) and release version updates (RVUs). The release series identifier is a letter that is incremented for each new release series.
Release Management Overview Release Version Update Distribution Release Version Update Revision (RVUR) A release version update revision (RVUR) is a revision of an RVU that introduces an important correction to that RVU by means of an RVU overlay. Usually, the correction is a defect repair for a single fault with unusually severe potential consequences such as data-integrity problems, system outages, or unusable subsystems.
Release Management Overview Controlled Availability (CA) Controlled Availability (CA) A Controlled Availability (CA) release is a conditional release of a product or products that does not meet a published standard, or for which HP is unable to provide support under published policy. CA releases are used to limit the shipment of a product or a release to a set of customers who agree to specific use conditions, which include migrating to a General Availability (GA) release when it is ready.
2 Resources for Managing RVUs and SPRs Evaluating and managing software release version updates (RVUs) and software product revisions (SPRs) involves: • • • • • Tracking the availability of RVUs and SPRs Reviewing content information about release version updates and product revisions Identifying changes to your existing configuration Identifying potential impacts and risks Installing RVUs and SPRs This section describes the Support Services and Tools, Software Release Management Documentation and Change
Resources for Managing RVUs and SPRs ExpressNotice ExpressNotice ExpressNotice is an automated information delivery system that automatically sends information pertinent to your installed products and RVU whenever there are any issues or changes. (Note that ExpressNotice publishes notices only for supported RVUs.) ExpressNotice also enables you to customize your information notification needs interactively online.
Resources for Managing RVUs and SPRs NonStop Computing Web Site NonStop Computing Web Site The NonStop Computing World Wide Web home page lets you navigate to information about products, service, and support. http://www.hp.com/go/nonstop.
Resources for Managing RVUs and SPRs • • • • • NonStop Technical Library (NTL) Serve as a high-level overview of new and changed function delivered in the RVU and include information on new products or enhancements to existing products Contain the Content file and Readme file for the RVU Contain information about the impact of the RVU on applications, databases, networks, installation, configuration, operations, and system management List which products are new, obsolete, or not yet available, in additio
Resources for Managing RVUs and SPRs Software Management and Installation Products NTL Support and Service Library The Support and Service library contains general support and service content for NonStop servers, including information about Hotstuff messages, SPR Notes, SPR Summaries, Support Notes, and Release Docs. Note. For detailed information about SPR Notes, see Appendix B, What Is in an SPR Note. Starting with June 2006, SPR Notes are no longer created.
Resources for Managing RVUs and SPRs Software Release Management Documentation Software Release Management Documentation The following manuals and documents are available to help you evaluate new software release version updates and the impact of upgrading from one RVU to another. Release and Migration Manuals The manuals in the NTL Release and Migration library provide an overview of each RVU and describe the installation activities and changes for the RVU.
Resources for Managing RVUs and SPRs Site Update Tape (SUT) Documentation Site Update Tape (SUT) Documentation All the product version updates for a release are stored in distribution subvolumes (DSVs) on a site update tape (SUT). A DSV contains the object files and executables for a product, in addition to the product softdoc. The DSV for the RLSEDOC product (T9230), sometimes referred to as the release subvolume, contains the Content File and README File for the RVU as a whole.
Resources for Managing RVUs and SPRs Change Management Documentation Change Management Documentation These documents are available to help you evaluate software changes between RVUs. Hotstuff Messages Hotstuff messages are sent by the ExpressNotice service to describe a defect with unusually serious consequences and the steps you can take to avoid or prevent the problem.
Resources for Managing RVUs and SPRs Hotstuff Messages Example 2-1. Outage Prevention Notification (OPN) Hotstuff Message HOTSTUFF HS02860 OPN T9053G10 DP2 15SEP04 OUTAGE PREVENTION NOTIFICATION This notice describes a problem that potentially could cause an application outage and actions you can take to prevent it. Study this information carefully to evaluate how much risk, if any, this problem could present in your environment. Consider taking the preventive action described.
Resources for Managing RVUs and SPRs Example 2-2. SPR Recall Hotstuff Message HOTSTUFF HS02717 RECALL T8364F40 AAS WANSD AND G06.21 RVU OVERLAY 16JAN04 PLATFORM: NonStop Server REVISION HISTORY: Initial Publication: 16JAN04 SUMMARY: The following software product revision (SPR) has been recalled: T8364F40 AAS WANSD HS02815 previously announced that the following SPRs have been recalled: T9337F40 ACF ATP6100 T9338F40 ABK CP6100 The G06.
Resources for Managing RVUs and SPRs Hotstuff Messages Example 2-3. General Information Hotstuff Message HOTSTUFF HS02859 SQL/MX REMOVAL OF SUPPORT FOR RAND FUNCTION 16SEP04 PLATFORM: NonStop Server REVISION HISTORY: Initial Publication 16SEP04 SUMMARY: This hotstuff alerts users of possible data integrity issues when using the NonStop SQL/MX RAND function as part of a primary key on an INSERT statement. This hotstuff announces that support for the RAND function within SQL/MX is being withdrawn.
Resources for Managing RVUs and SPRs Software Revision Notifications Software Revision Notifications Software Revision Notifications are sent by the ExpressNotice service to announce the release of an unrestricted time-critical fix SPR and to provide enough information to help you decide whether to evaluate the SPR further. A Software Revision Notification contains one or more SPR Introduction Documents (SIDs).
Resources for Managing RVUs and SPRs Software Release Documents (Softdocs) Software Release Documents (Softdocs) A softdoc provides information about a software product revision, supplementing a product’s manuals between editions.
Resources for Managing RVUs and SPRs Release Documentation Distribution Matrix Release Documentation Distribution Matrix DSM/SCM User’s Guide X Release Version Update Compendium (Technical Documentation page) X Software Installation and Upgrade Guide X Hotstuff messages (including OPNs) X README file X Softdocs X www.hp.
3 Evaluating Software Changes This section describes the research procedures and tools you can use to help you evaluate the various types of software change notifications: • • • • • • Determining Which SPRs to Install Evaluating Outage Prevention Notifications Evaluating SPR Introduction Documents (SIDs) Evaluating Requisite SPRs Keeping Track of SPRs Using Software Change Research Tools You will use these procedures and tools during the tasks described in Section 4, Software Installation Planning and
Evaluating Software Changes Information Sources When Installing a New System or Software Upgrade Information Sources When Installing a New System or Software Upgrade Primary Sources Secondary Sources Outage Prevention Notifications (OPNs) Other Hotstuff messages (such as SPR recalls) SPR Introduction Documents (SIDs).
Evaluating Software Changes Evaluating Outage Prevention Notifications Evaluating Outage Prevention Notifications Outage Prevention Notification An Outage Prevention Notification (OPN) is a Hotstuff message issued to warn you of a defect that is likely to cause multiple unrelated outages. The problems described usually involve software products but occasionally apply to hardware products.
Evaluating Software Changes Evaluating SPR Introduction Documents (SIDs) Evaluating SPR Introduction Documents (SIDs) SPR Introduction Document An SPR Introduction Document (SID) summarizes the fixes and features introduced in an SPR. SIDs also highlight fixes that correct defects that could conceivably cause an outage, even under very unlikely conditions, including defects that do not warrant an Outage Prevention Notification.
Evaluating Software Changes How to Use an SID to Evaluate an SPR How to Use an SID to Evaluate an SPR You might want to keep a log of SPRs as you receive and review their SIDs. You should note which SPRs have the highest priority for your computing environment and those you ignore, and the reason why (see Keeping Track of SPRs on page 3-12). 1. Determine if the SPR is applicable to the RVU you have installed. If not, ignore it. For example, if you are on the G06.21 RVU and the SPR is usable only with G06.
Evaluating Software Changes SID Evaluation Examples SID Evaluation Examples SID Example 1: Fix Avoids Critical Problems ID: T9053 G11 APK DP2 This SPR is applicable to these RVUs (as of 2004-SEP-29) G06.24 HP ASSESSMENT considering all changes: 1 fix 0 features Install promptly to avoid critical problems in specific cases Consider using this SPR to avoid possible outage 1.
Evaluating Software Changes SID Evaluation Examples SID Example 2: Evaluate New Feature ID T7909 F40 AAH UNRESTRICTED WANBOOT This SPR is usable with these RVUs (as of 1999-JUN-07) G02.00 G03.00 G04.00 G05.00 G05.01 G06.00 G06.01 G06.04 G06.05 G06.
Evaluating Software Changes Evaluating Requisite SPRs Evaluating Requisite SPRs Note. Some SPRs have conditional requisites. In such cases, results displayed by Scout for NonStop Servers can be misleading or, in rare cases, incorrect. As a precaution, always review the softdocs of the SPRs you are sent to see if any of the requisites are conditional. See Researching Conditional Requisites on page 3-10 for detailed information.
Evaluating Software Changes Reviewing Requisites Secondary Requisite A secondary requisite is an SPR that provides the function of a primary requisite but is not a primary requisite (it supersedes or accumulates the primary requisite). Reviewing Requisites 1. Review the SPR’s requisites. Note that an SPR specified as a requisite is always the earliest usable revision of its product that supplies the required functionality. The requisite SPR might have been superseded by later SPRs. 2.
Evaluating Software Changes Researching Conditional Requisites choose it because it fixes another defect that you conclude presents a risk in your environment. Conversely, if the installation of a superseding SPR requires a system load or subsystem interruption but installation of the minimum requisite does not, installing the minimum requisite might be a better choice. 5.
Evaluating Software Changes • • Researching Conditional Requisites If you have already installed an SPR for the same product as one of the selected SPRs: ° You might not need the selected SPR (or its requisites, if any) because the SPR you installed supersedes it.
Evaluating Software Changes Keeping Track of SPRs Keeping Track of SPRs Keep an SPR log file listing which SPRs (including those cited in OPNs and other Hotstuff messages) have been reviewed, evaluated, and installed on each of your systems, and update the log regularly.
Evaluating Software Changes Using Software Change Research Tools Using Software Change Research Tools Identifying What Is Installed on Your System • • • You can generate DSM/SCM reports listing which products and SPRs have been installed (for more information, see the DSM/SCM User's Guide). You can determine which products were delivered on the SUT for a particular RVU and system number by examining the CUSTFILE for that system.
Evaluating Software Changes Identifying What Is Installed on Your System Managing Software Changes—427169-005 3- 14
4 Software Installation Planning When you install a new system or software upgrade (an RVU), you receive a site update tape (SUT) containing all the products for which you are licensed. In addition to the SUT, you might want or need to apply additional software product revisions (SPRs) to fix defects discovered since the RVU was first introduced or to obtain features that provide significant benefit. The software installation process requires detailed planning and preparation.
Software Installation Planning Task 1: Research and Select Additional SPRs Task 1: Research and Select Additional SPRs Step 1: Determine Which SPRs Are Important to You Between the time an RVU is first shipped and the time you install it, SPRs that are usable with the RVU might be issued. These guidelines can help you determine which of these SPRs to install. Effort Level Procedures Least Review SPRs cited in Outage Prevention Notification (OPN) Hotstuff messages.
Software Installation Planning Task 3: Create an Installation Plan For each SPR on your list: Step 1: Check to See if the SPR Has Been Superseded Check to see if the SPR has been superseded by a more recent SPR. If it has, review the SID or softdoc of the superseding SPR to determine which SPR provides the greater benefit. Note. Starting with G06.28 and H06.
Software Installation Planning Task 5: Install the SPRs Task 5: Install the SPRs Review the README file for the RVU. Install additional SPRs in a timely manner to avoid encountering known problems that have already been resolved. When you install an SPR, make sure you have all relevant information accumulated and examined during your review and research phases. If you plan to install more than one SPR or requisite, verify the order of installation.
Software Installation Planning Planning for an RVU Upgrade Planning for an RVU Upgrade • • • • • • • • • Task 1: Know What Is Currently Installed on Your System Task 2: Research the Scope of the New Release Version Update Task 3: Evaluate “Want to Keep” SPRs Task 4: Research Additional SPRs for the RVU Task 5: Evaluate Requisite SPRs Task 6: Evaluate the Impact of Upgrading to the New RVU Task 7: Obtain Needed SPRs Task 8: Install the Release Version Update and Additional SPRs Task 9: Create an SPR Log F
Software Installation Planning Task 3: Evaluate “Want to Keep” SPRs Step 2: Study the README File for the New RVU The README File (described on page 2-7) for the RVU contains information that might not have been available at the time manuals, softdocs, and other release materials were produced.
Software Installation Planning Task 3: Evaluate “Want to Keep” SPRs Step 3: Check to See if Your SPR Is Present in the New RVU The easiest way to see if your SPR is present in a new RVU is to use Scout for NonStop Servers to display the content for that RVU or the detailed information for that SPR. • • If an SPR on your “want to keep” list is listed in the Scout RVU Content page, all its features and corrections are included in the new RVU, and you do not need to install it with the new RVU.
Software Installation Planning Task 4: Research Additional SPRs for the RVU Check to see if your SPR is cited in Part 1 of the Content file for the new RVU: • • If it is, all of its fixes or features are present in the new RVU, and you do not need to reinstall your SPR with the RVU. Circle Completed on your SPR Research Form and end your research on this SPR. Continue with the next “want to keep” SPR. If it is not, check the softdoc for the initial PVU in the new RVU.
Software Installation Planning Task 5: Evaluate Requisite SPRs Step 2: Evaluate Which SPRs to Consider for Further Research Based on the selection criteria from Step 1, evaluate the SPRs by using the procedures described in Section 3, Evaluating Software Changes.
Software Installation Planning • Task 7: Obtain Needed SPRs Softdocs for products you are interested in that have new or changed product versions in the new RVU Use this information to identify all migration and installation impacts and to develop a detailed plan to upgrade to the RVU. Your plan should describe exactly what you have to do, including a fallback plan, in addition to listing the SPRs and hardware you need to order.
Software Installation Planning Task 9: Create an SPR Log File The Installation Instructions section of the softdoc is relevant only to the SPR being documented. You must use judgment in composing aggregate instructions to install multiple SPRs simultaneously (whether dependent on each other or not). Task 9: Create an SPR Log File Create an SPR log file to maintain an accurate and current software profile on your system. Be sure to document the reasons for your decision to install an SPR.
Software Installation Planning Task 9: Create an SPR Log File Managing Software Changes—427169-005 4- 12
5 Managing Changes Between Release Version Updates Between software release version updates, you are notified about certain SPRs you might need or want to apply to your current RVU. SPRs issued between RVUs provide time-critical fixes, so it is important to review them as they are issued to determine the applicability of the defect repair to the products installed on your system.
Managing Changes Between Release Version Updates Task 2: Track SPRs Task 2: Track SPRs HP provides the following tools to keep track of SPRs being made available for products you run on your system: • • • ExpressNotice service (see page 2-2) Scout for NonStop Servers NTL Softdoc Archive and NTL Support and Service library (see page 2-4) HP strongly recommends that you monitor Hotstuff messages and SIDs published through ExpressNotice, at least once a week, preferably every day. Note. Starting with G06.
Managing Changes Between Release Version Updates Task 4: Obtain Needed SPRs If you are using Scout for NonStop Servers, you can submit a search request for requisite SPRs. For example, a search for the requisites for T9064 AJA for the G06.05 RVU reveals that T1037 ABC and T6916 ACM are required for the SPR. VST090.vsd Task 4: Obtain Needed SPRs You can obtain an SPR through Scout for NonStop Servers or contact your local Global Customer Support Center (GCSC) or service provider.
Managing Changes Between Release Version Updates Task 6: Update Your SPR Log File Any steps to be carried out before or after those associated with DSM/SCM are listed in the Installation Instructions section of the softdoc. For example, for some products it is necessary to save subsystem configuration files before they are replaced during the installation. On occasion, microcode of a certain version must be downloaded before the DSM/SCM steps can occur.
A What Is in a Softdoc A software release document, commonly known as a softdoc, provides information regarding a software product revision (SPR).
What Is in a Softdoc • Softdoc Sections Revision History indicates revisions made to this softdoc. For example: Revision History: # Rev.-Date Description of changes in each revision 1 07OCT2004 Added New Features 23 2 07OCT2004 Deleted reference to T0394ABA.Correct reference should be T0394G10. 3 10OCT2004 Changed reference of Requisite PVU T9053APF to T9053APJ (if running G06.24 or later).
What Is in a Softdoc Softdoc Sections present in your software configuration for a specific fix or feature in this SPR to be fully functional. For example, this listing indicates that T9794D20 or later is required: Required Firmware: • T9794D20 HYA IPB MICROCODE Required Software lists the requisite software SPRs, which provide specific function or data that must be present in a software configuration for a specific fix or feature in this SPR to be fully functional.
What Is in a Softdoc ° Softdoc Sections What post-installation steps are required Because DSM/SCM automatically determines what steps are needed to install an SPR, only the general process of installing software using DSM/SCM (plus specific preinstallation and post-installation steps that DSM/SCM does not perform) are specified in the softdoc. • Installation Instructions describes the procedures that must be followed to properly install the SPR. Note.
What Is in a Softdoc Initial PVU Softdoc Example Initial PVU Softdoc Example SOFTWARE RELEASE DOCUMENT Product Name: SPR ID: DATE: MEASURE T9086G12 11NOV2004 Copyright Notice: HP CONFIDENTIAL: NEED TO KNOW ONLY Copyright 2004 Hewlett-Packard Development Company, L.P. Protected as an unpublished work. The computer program listings, specifications and documentation herein are the property of Compaq Computer Corporation and successor entities such as Hewlett-Packard Development Company, L.P.
What Is in a Softdoc Initial PVU Softdoc Example - Perform the pre-installation steps shown below. - Run ZPHIRNM to perform the RENAME step. - If not using G05.00 onward, VOLUME to the new/updated SYSnn, and run VTILT to determine if Shared Runtime Library conflicts must be resolved before loading the system. - Perform the post-installation steps shown below. - Perform these pre-installation steps. NONE. - Perform these post-installation steps. NONE. New Features: 1.
What Is in a Softdoc Initial PVU Softdoc Example 4. [G12] SYMPTOMS: When only some of the plot-entries were plotted, with TIME-BASE OFF and VERT-BASE OFF, the columns were not aligned properly in the report. (SOLN 10-040318-4338) Known Problems Remaining: 1. SYMPTOMS: The Device-Busy-Time counter of the OPDISK record (legacy-style OPDISK report) on D-series RVUs displays incorrect values. (SOLN 10-040318-4337) 2.
What Is in a Softdoc Successive PVU Softdoc Example Successive PVU Softdoc Example SOFTWARE RELEASE DOCUMENT Product Name: SPR ID: DATE: OSM SERVICE PROVIDER T2728G07^AAL 10AUG2004 Copyright Notice: HP CONFIDENTIAL: NEED TO KNOW ONLY Copyright 2004 Hewlett-Packard Development Company, L.P. Protected as an unpublished work.
What Is in a Softdoc Successive PVU Softdoc Example * When using DSM/SCM to install this SPR: - RECEIVE the SPR from disk or tape. - COPY the SPR to a new revision of the software configuration you want to update. - BUILD and APPLY the configuration revision. - Perform these pre-installation steps: 1. Issue the following commands in SCF: ABORT PROCESS $ZZKRN.#OSM-APPSRVR ABORT PROCESS $ZZKRN.#OSM-CONFLH-RD - Run ZPHIRNM to perform the RENAME step. - Perform these post-installation steps: 1.
What Is in a Softdoc Successive PVU Softdoc Example 6. [AAL] OSM provides basic health and monitoring support for the UPS model R5500 that has ConnectUPS-X Web/SNMP interface card installed. It also provides a link to the Web/SNMP interface card for detailed device information and configuration. (No SOLN) 7. [AAL] This SPR supports the automatic data collection of failed PMF, PMF2, IOMF, and IOMF2. This feature must be enabled in the OSMCONF file; see the OSM Migration Guide for details.
What Is in a Softdoc Successive PVU Softdoc Example 7. [AAL] OSM provider processes sometimes abend just after being started because of a delay in receiving the startup message from the CIMOM process. SOLN 10-040120-2546) 8. [AAL] OSM Service Connection display flickers many times when a state change occurs on a disk. (SOLN 10-040505-5773) Known Problems Remaining: 1. Redundant Power Scrub Test Failed alarm is not generated when MOSFET, DCC, and Main Rail voltages are out of acceptable limits.
What Is in a Softdoc Successive PVU Softdoc Example Managing Software Changes—427169-005 A-12
B What Is in an SPR Note SPR Notes provide detailed information about an SPR, and include: • • • SPR Introduction Document (SID) provides summary information about the SPR and is distributed by ExpressNotice. Softdoc is a copy of the softdoc for the SPR. DSV Information lists the files in the distribution subvolume (DSV) for the SPR. You can access SPR Notes through the NTL Support and Service Library. Note. Starting with June 2006, SPR Notes are no longer created.
What Is in an SPR Note SID Fields INSTALLATION IMPACT: coldload SID Fields ID and Product Name The unique product version update ID assigned to the SPR and the name of the product to which the SPR applies. Applicable to RVUs Lists the RVUs to which you can apply this SPR as of the specified date. Unless listed, the SPR is not applicable to RVUs shipped prior to that date.
What Is in an SPR Note SID Fields Changes Introduced in the SPR This section categorizes and summarizes each change introduced in the SPR. The number next to the description of the fix or feature corresponds to the number of the description of the fix or feature in the SPR’s softdoc. The categories include: • • • • Consider using this SPR to avoid possible outage . Consider using this SPR to avoid . Consider using this SPR to obtain .
What Is in an SPR Note Softdoc Softdoc The next portion of the SPR Note, from the Product Name field through the Known Problems Remaining field, is a copy of the SPR softdoc. See Appendix A, What Is in a Softdoc, for descriptions of the softdoc fields.
What Is in an SPR Note DSV Information DSV Information Following the text of the softdoc is a list of the files in the Y and R distribution subvolumes. • • Y indicates that the files are for CISC processors (for RISC also, if there is no R DSV list). R indicates that the files are for RISC processors only. Example B-1.
What Is in an SPR Note SPR Note Example SPR Note Example HEWLETT PACKARD SPRNOTE BEGIN SID ID: T8169 G06 AAN WANADCCP This SPR is applicable to G06.01 G06.03 G06.04 G06.10 G06.11 G06.12 G06.18 G06.19 G06.20 these RVUs (as of 2004-SEP-30) G06.05 G06.06 G06.07 G06.08 G06.13 G06.14 G06.15 G06.16 G06.21 G06.22 G06.23 G06.24 G06.09 G06.
What Is in an SPR Note SPR Note Example Requisite SPRs: T1228AAG (If using SWAN 2) T7953AAL (If using SWAN 2) T9088ADQ Required Hardware: NonStop S-series server 3880 ServerNet Wide Area Network (SWAN) concentrator (or) 3881 ServerNet Wide Area Network (SWAN 2) concentrator Required Firmware: T7953G01 SWAN FIRMWARE Required Software: T1228G06 T8365F40 T7925F40 T7922F40 T7909F40 T7899F40 T9050G03 T9088G05 T9338F40 Manuals: NOTE: 1. 2. 3. 4. SWAN BASE (If using G06.
What Is in an SPR Note SPR Note Example (SOLN 10-040727-8273) Known Problems Remaining: 1. When a WANADCCP line with an X.21 interface tries to receive more number of bytes than the configured MAXFRAME line modifier, clip dump occurs.
C SPR Research Form Current Product on My System Product on RVU-ID SUT Substitute or Recommended Product Current SPR on My System Included in SPR on RVU-ID SUT Included in Substitute SPR (Replaced) (Completed) Product T-number: Product Version: SPR Number: Product Name: Product Date: SPR Availability: Corrections: Features: SPR Status: (Circle one) (Pending) Requisite SPRs: (For substitute SPRs only) Managing Software Changes—427169-005 C- 1
SPR Research Form Managing Software Changes—427169-005 C- 2
D How to Use a Content File The Content file for an RVU shows whether the RVU accumulates the function of nonrecalled SPRs for the product versions distributed with and since the oldest RVU from which upgrading to the new RVU is supported. When you are researching the feasibility of moving to a new RVU, part of your analysis involves studying possible regressions and ensuring that features and corrections you obtained through individual SPRs for your current RVU are maintained with the new RVU.
How to Use a Content File Included SPRs Example D-1. Content File: Included SPRs G06.16 CONTENT Included SPRs SPR Change SPR Product in from Included Name Product Ver Updt G06.16 G06.15 in G06.
How to Use a Content File Excluded SPRs Included SPRs in This RVU The SPR entries marked with the letter I in the SPR Included in RVU-ID column have their complete fixes and features provided in this RVU in some form, although the SPRs themselves are not present.
How to Use a Content File Using the Content File to Research a New RVU Using the Content File to Research a New RVU When you are researching the feasibility of upgrading to a new RVU, examine Content files, Support Notes, and softdocs to ensure that the features and corrections from your current RVU are preserved when you upgrade to a new RVU.
How to Use a Content File Researching the Differences Between RVUs Step 2: Review Softdocs for New and Changed Product Versions Review softdocs for products you are interested in that have a plus (+) entry in the Change from RVU-ID column in the Content file for the new RVU. For example, suppose that you are running the DCE product on your current system. A search on DCE in the Content file for a newer RVU might reveal these entries: SPR Change SPR Product in from Included Name Product Ver Updt G06.
How to Use a Content File Researching SPR Regressions Researching SPR Regressions When you are evaluating the feasibility of moving to a new RVU, part of your analysis involves researching possible regressions and ensuring that features and corrections you obtained through SPRs for your current RVU are maintained with the new RVU. 1. Make a list of the SPRs that you have installed on your current RVU whose features and corrections you want to keep in the new RVU. 2.
E Independent Products Policy An Independent Product is a licensed product that is delivered individually on a CD-ROM rather than as part of an integrated release version update. An Independent Product can contain Nonstop operating system components, workstation components, or a combination of components for both platforms. The policy described in this section covers only Independent Products containing one or more NonStop operating system component products.
Independent Products Policy Independent Product Support Independent Product Support Support for Independent Products is determined by the Independent Product version containing the problem. Each Independent Product version has at least one Minimum Release Level (MRL), which is the earliest RVU on which the Independent Product version has received integration testing.
Independent Products Policy Example of Support Note Announcing Availability of an IP Example of Support Note Announcing Availability of an IP SUPPORT NOTE S04046 FCS NOTE - HEWLETT PACKARD NONSTOP XML PARSER VERSION 5.0 12MAY04 REVISION HISTORY: Initial Publication 12MAY04 SUMMARY: As of 12 May, 2004 Hewlett Packard NonStop NonStop XML Parser version 5.0 is available to order as an Independent Product.
Independent Products Policy Example of Support Note Announcing Availability of an IP Managing Software Changes—427169-005 E- 4
Glossary CA. See Controlled Availability (CA). conditional requisite. A requisite that is needed only under certain circumstances. Content file. A file listing the SPRs included in and excluded from a release version update (RVU). Controlled Availability (CA). Conditional release of a product that does not meet a published standard or which HP does not support under published policy.
Glossary firmware firmware. Code that is necessary for the power-up initialization and communication with the host or device. A ServerNet software component (for example, an adapter) is called firmware. Some firmware is downloaded when the system or component is booted. first customer shipment (FCS). The point at which HP begins revenue shipments to customers of a product set. The FCS can be declared for General Availability or for Controlled Availability. GA. See General Availability (GA).
Glossary obsolete SPR obsolete SPR. An SPR that is not defective and presents no risk but provides no future value to potential new users (for example, it might apply to an obsolete product). obsolete product. A product that is no longer supported, sold, or delivered in any release version update (RVU). Outage Prevention Notification (OPN).
Glossary requisite SPR requisite SPR. An SPR that either provides required function or data to enable a specific fix or feature in a requiring SPR to be fully functional (to use the requisite product). A requisite SPR is required when using the requiring SPR to maintain compatibility with another product. requiring SPR. An SPR that has one or more requisite SPRs. restricted SPR. An SPR that is made available only for a specific situation, as determined on a case-by-case basis.
Glossary Software Recall/Withdrawal message Software Recall/Withdrawal message. A type of Hotstuff message that indicates that an SPR has been recalled or withdrawn. software release document (softdoc). A document that describes revision-dependent information regarding a software or firmware SPR. Software Revision Notification.
Glossary withdrawn SPR Managing Software Changes—427169-005 Glossary- 6
Index A G Assessment of SPR 3-4 General Availability (GA) 1-10 C H Conditional requisite defined 3-8 researching 3-10 Content file defined 2-7 researching regressions D-6 using D-1 Controlled Availability (CA) 1-10 Hotstuff messages defined 2-2, 2-8 examples of 2-9 general 2-8 OPNs 2-8, 3-3 Recall 2-8 Withdraw 2-8 I D Direct requisite 3-8 Distribution subvolume (DSV) 2-7 DSM/SCM defined 2-5 product 4-4, 4-10, 5-3 reports 5-1 E Early Adopter Program (EAP) 1-9 Excluded SPRs D-3 ExpressNotice defined
Index O NTL Softdoc Archive 2-4 NTL Support and Service library defined 2-5 Hotstuff messages, viewing 2-8 OPNs, viewing 2-8 SPR Notes, viewing 2-12 SPR Recall messages, viewing 2-8 Support Notes, viewing 2-13 NTL User Documentation library 2-3 O Obsolete products D-3 Obsolete SPR 1-7 Outage Prevention Notification (OPN) content 3-3 defined 3-3 evaluating 3-3 example of 2-9 Outages, avoiding 3-1 P Planned product maintenance defined 1-4 delivery attribute of SPR 1-3 delivery of 1-1 Primary requisite 3-8
Index T Softdocs defined 2-13 installation considerations A-3, A-4 known problems remaining A-4 migration considerations A-3 new features A-4 problems corrected A-4 required firmware A-2 required hardware A-2 required software A-3 requisite PVUs A-2 summary A-2 superseded PVUs A-2 Software Product Maintenance List (SPML) document 1-7, 2-7 Software product revision (SPR) defined 1-3 delivered on SUT 4-5 evaluating 3-1, 4-2, 4-8, 4-9 for obsolete products 1-7 installing 4-4, 4-10, 5-3 log file 3-12, 4-4, 4-
Index W Managing Software Changes—427169-005 Index-4
