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 425018-001 N.A. December 1999 426723-001 N.A. July 2000 427169-001 N.A. November 2000 427169-002 N.A. August 2002 427169-003 N.A.
Managing Software Changes Glossary Index What’s New in This Manual vii Manual Information vii New and Changed Information Examples Tables vii About This Manual ix Who Should Read This Manual ix Purpose ix Organization of This Manual x Related Reading xi Your Comments Invited xii Notation Conventions xii Abbreviations xiii 1.
3.
4. Software Installation Planning Contents Keeping Track of SPRs 3-15 Using Software Change Research Tools 3-16 Identifying What Is Installed on Your System 3-16 4.
B. What Is in an SPRNOTE Contents B. What Is in an SPRNOTE SPR Introduction Document (SID) SID Example B-1 SID Fields B-2 SPR Requisites B-4 Softdoc B-5 DSV Information B-5 SPRNOTE 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.
Tables Contents Tables Table 2-1. Table 3-1.
Contents Managing Software Changes—427169-003 vi
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 Managing Software Changes—427169-003 viii
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 TIM User Documentation collection’s “Release and Migration Information” folder contain RVU and system-specific planning, configuration, and installation information. These manuals include: Scout for NonStop Servers User’s Guide Explains how to use the Scout for NonStop Servers tool to analyze and order SPRs. Interactive Upgrade Guide Available as of G06.
Your Comments Invited About This Manual Your Comments Invited After using this manual, please take a moment to send us your comments. You can do this by: • • • Completing the online Contact NonStop Publications form if you have Internet access. Faxing or mailing the form, which is included as a separate file in Total Information Manager (TIM) collections and located at the back of printed manuals. Our fax number and mailing address are included on the form.
Abbreviations About This Manual Abbreviations IP Independent Product OPN Outage Prevention Notification PV product version PVU product version update RV release version RVU release version update SID SPR Introduction Document SPR software product revision SUT site update tape TIM Total Information Manager See the Glossary for additional abbreviations used in this manual.
Abbreviations About This Manual Managing Software Changes—427169-003 xiv
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 Kernel 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) Sequence Initial The first PVU within a PV. Delivered in the RVU in which it was initially introduced. Successive Any PVU following the initial PVU within the same product version. Available through Scout for NonStop Servers and normally delivered in the RVU in which it was first introduced.
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 Release Series ID Release Release Version Version ID Update 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 The RVU identifier is a two-digit number from 00 to 99 appended to a release version ID and separated from it by a period. When a new RVU is created, the RVU identifier is incremented by one; for example, H02.01. Generally, new RVUs are created quarterly. Release Version Update Distribution A release version update is delivered on a site update tape (SUT) that is customized to contain only the products for which your system is licensed.
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 the 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 generates notices only for supported RVUs.) ExpressNotice also allows you to customize your information notification needs interactively online.
Resources for Managing RVUs and SPRs Support Web Site Support Web Site The NonStop Computing World Wide Web home page lets you navigate to information about products, service, and support. http://nonstop.compaq.com/view.asp?PAGE=CustomerSupport You can also contact the Customer Response Center (CRC) with support questions from Monday through Friday, 8:00 a.m. to 5:00 p.m. (EST) at: 1-800-282-6672.
Resources for Managing RVUs and SPRs Software Management and Installation Products TIM User Documentation Collection The User Documentation collection contains software and hardware manuals for NonStop servers and for the products that run on them. The Release and Migration Information Folder Of particular interest in terms of evaluating and managing RVUs and SPRs are the manuals in the “Release and Migration Information” folder.
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.
Resources for Managing RVUs and SPRs Content File Content File The Content file lists the SPRs included in the RVU and, in some cases, the SPRs excluded from an RVU (that is, available SPRs not delivered in the RVU). The Content File is available: • • In the TIM SOFTDOCs Collections On the site update tape in the RLSEDOC (Y9230) distribution subvolume Appendix D, How to Use a Content File, describes the Content file in detail.
Resources for Managing RVUs and SPRs SPRs for Special Consideration List Outage Prevention Notifications (OPNs) Outage Prevention Notifications (OPNs) are Hotstuff messages that describe a problem that is particularly likely to cause a system outage and that provide steps to avoid or prevent the problem. OPNs are also available through TIM Support Collections and Scout for NonStop Servers.
Resources for Managing RVUs and SPRs SPRs for Special Consideration List Example 2-1. Outage Prevention Notification (OPN) Hotstuff Message HOTSTUFF HS02727 NSK OPN T0470G06 AAF TCP/IP Monitor Process 07MAY02 PLATFORM: NSK PROBLEM DESCRIPTION: The TCPMON initialization code can write past the end of blocks allocated in QIO shared memory. This can induce halts in any QIO client that happens to own the affected memory. Release Version Updates affected: This problem occurs in G06.08 - G06.12.
Resources for Managing RVUs and SPRs SPRs for Special Consideration List Example 2-2. SPR Recall Hotstuff Message HOTSTUFF HS02717 NSK RECALL T8306G00 AAV and AAX OSS SOCKETS 06MAR02 PLATFORM: NSK SUMMARY: T8306G00 AAV and AAX (OSS SOCKETS) have been recalled. DETAIL: T8306G00 AAV and AAX (OSS SOCKETS) have been recalled because they can cause data corruption for AF_INET send operations if used with conventional TCP/IP.
Resources for Managing RVUs and SPRs SPRs for Special Consideration List Example 2-3. General Information Hotstuff Message HOTSTUFF HS02734 NSK: ABENDRETENTION Might Be Erroneously Applied to Entire VOLSET 05JUN02 PLATFORM: NSK SUMMARY: When a process that is writing the second or subsequent tape file to a tape volume set fails, ABENDRETENTION might erroneously be applied to all tape files of the volume set. This situation can cause premature expiration of tape files.
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) Softdocs provide 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 G06.xx Release Version Update Compendium (Technical Documentation page) X G06.xx Software Installation and Upgrade Guide X G-Series Highlights and Migration Planning Guide X Hotstuff messages (including OPNs) X X X X Interactive Upgrade Guide (Technical Documentation page) X Scout for NonStop Servers User’s Guide X nonstop.compaq.
Resources for Managing RVUs and SPRs Release Documentation Distribution Matrix Managing Software Changes—427169-003 2-14
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 SPRs for Special Consideration Evaluating Requisite SPRs Keeping Track of SPRs Using Software Change Research Tools You will use these procedures and tools during the tasks described in Se
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 SPRs for Special Consideration list Content file Outage Prevention Notifications (OPNs) Other Hotstuff messages (such as SPR recalls) SPR Introduction Documents (SIDs) Support Notes Previously installed SPRs (from your records) SPRNOTEs README file for the RVU List of SPRs usable with the RVU (from
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 What Information Is in an OPN Example 3-1. Outage Prevention Notification (OPN) HOTSTUFF HS02727 NSK OPN T0470G06 AAF TCP/IP Monitor Process 07MAY02 PLATFORM: NSK PROBLEM DESCRIPTION: The TCPMON initialization code can write past the end of blocks allocated in QIO shared memory. This can induce halts in any QIO client that happens to own the affected memory. Release Version Updates affected: This problem occurs in G06.08 - G06.12.
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-15). 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.12 RVU and the SPR is usable only with G06.
Evaluating Software Changes SID Evaluation Examples SID Evaluation Examples SID Example 1: Fix Provides Significant Benefit ID: T9053 D46 AKM UNRESTRICTED DP2 - ENHANCED DISC PROCESS This SPR is usable with these RVUs (as of 1999-MAY-27) D46.00 D47.00 D48.
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 SPRs for Special Consideration Evaluating SPRs for Special Consideration SPRs for Special Consideration As part of your planning for the installation of a new system or an upgrade to a different RVU, you should evaluate additional individual SPRs that are usable with that RVU. You might decide to install SPRs that fix problems that you determine present a significant risk in your computing environment.
Evaluating Software Changes How SPRs for Special Consideration Are Categorized How SPRs for Special Consideration Are Categorized SPRs for Special Consideration lists are shown first for SUT-based products and then for Independent Products.
Evaluating Software Changes Where to Find the SPRs for Special Consideration List Where to Find the SPRs for Special Consideration List You can use Scout for NonStop Servers to obtain the most recent SPRs for Special Consideration list for the RVU to which you are upgrading. You can also view the list in the TIM Support collection. How to Evaluate the SPRs for Special Consideration List 1. Review the SPRs listed in the section “Install to avoid potential critical problems.” 2.
Evaluating Software Changes Evaluating Requisite SPRs Evaluating Requisite SPRs Note. Some SPRs have conditional requisites (see page B-4). 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-13 for detailed information. Reviewing Requisites 1. Review the SPR’s requisites.
Evaluating Software Changes Researching Conditional Requisites If either 4a or 4b is true, you might want to consider using the superseding, or later, SPR as an alternative to the cited minimum requisite SPR. You might decide to choose it because it fixes another defect that you conclude presents a risk in your environment.
Evaluating Software Changes Researching Conditional Requisites Note also that Scout’s requisite analysis requires that the SPRs be installed on the specified RVU as it is currently delivered.
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.
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 for Special Consideration and SPRs cited in Outage Prevention Notification (OPN) Hotstuff messages.
Software Installation Planning Task 3: Create an Installation Plan 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.
Software Installation Planning Task 6: Create an SPR Log File requisite, verify the order of installation. See the DSM/SCM User’s Guide for information on using the DSM/SCM product to install SPRs. Caution. Use the DSM/SCM product to properly install an SPR. Using other ways to install NonStop Kernel operating system software (for example, copying files into the SYSnn subvolume) can have serious consequences later.
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 Contain information about the impact of the new RVU on applications, databases, networks, installation, configuration, operations, and system management List, for each RVU, which products are new, obsolete, or not yet available, in addition to product versions that are not yet available for a specific RVU Provide an overview of the installation activities and changes for the planned RVU Step 2: Study the README File for the New RV
Software Installation Planning Task 3: Evaluate “Want to Keep” SPRs Perform Steps 3 and 4 for each of these “want to keep” SPRs. When you have finished researching all “want to keep” SPRs, continue with Task 4: Research Additional SPRs for the RVU. 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 through Scout for NonStop Servers, as documented in the Scout for NonStop Servers User’s Guide.
Software Installation Planning Task 3: Evaluate “Want to Keep” SPRs If the SPR Is for a Different Product Version From the One in the New RVU Normally, the initial PVU for a new product version incorporates all of the fixes and features of SPRs issued for previous product versions. However, the softdoc for the initial PVU does not necessarily describe every detail of that history.
Software Installation Planning Task 4: Research Additional SPRs for the RVU Task 4: Research Additional SPRs for the RVU Step 1: Determine Which SPRs Are Important to You Between the time an RVU is first shipped and the time you install it, additional SPRs 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 for Special Consideration and SPRs cited in Outage Prevention Notification (OPN) Hotstuff messages.
Software Installation Planning Task 5: Evaluate Requisite SPRs Step 3: Check to See if Any SPRs Have Been Superseded For each SPR on your “additional SPRs” list, use Scout for NonStop Servers to determine if the SPR has been superseded. If it has, decide which of the alternatives is best for your circumstances.
Software Installation Planning Task 8: Install the Release Version Update and Additional SPRs Task 8: Install the Release Version Update and Additional SPRs See the appropriate installation and migration guides and the README file for releasespecific information on installing new RVUs. See the DSM/SCM User’s Guide for information on using the DSM/SCM product to install new RVUs and SPRs. Caution. Use the DSM/SCM product to properly install an SPR.
Software Installation Planning Task 9: Create an SPR Log File Managing Software Changes—427169-003 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 (see the Scout for NonStop Servers User’s Guide) TIM SOFTDOCs Collections and TIM Support Collections (see page 2-3) HP strongly recommends that you monitor Hotstuff messages and SIDs published through ExpressNotice, at least once a week,
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, as described in the Scout for NonStop Servers User’s Guide. 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.
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 Considerations” section of the softdoc addendum. 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 Summary indicates the significant new features and defect repairs introduced since the first customer shipment of the previous revision of the product. For example: The LLC2ENABLED attribute is supported for LLC1 ports on PAM over Ethernet. The SCF Primary command can be used to switch CPU when the Line is in STARTED state. This release also fixes some problems related to trace, lobe wire fault and errors from SNAX.
What Is in a Softdoc • Softdoc Addendum Problems Corrected indicates what problem corrections, if any, have been made. Each item is prefaced by the PVU ID that corrected the problem; for example, [AAM] or [G05]. If a problem is associated with a Genesis solution, the solution number is listed after the item; otherwise, (No SOLN) is listed. • Known Problems Remaining describes problems that have not been fixed.
What Is in a Softdoc • • Softdoc Addendum Summary summarizes the features or fixes described. Superseded PVUs lists superseded SPRs in alphabetic order (for example, AAE, AAH, AAP, AAS). All of the distributed files and all fixes and features, except those that are officially withdrawn, that are in the superseded SPR will be in the superseding SPR. See also Superseded SPRs on page 1-5.
What Is in a Softdoc Softdoc Addendum This section also includes an installation impact statement that characterizes the impact of installing the SPR, including whether any specific or unusual considerations are involved.
What Is in a Softdoc Softdoc Example Softdoc Example SOFTWARE RELEASE DOCUMENT Product Name: PAK/UNPAK Product Number: T1255G06 Date: 04FEB2002 Copyright Notice: COMPAQ CONFIDENTIAL: NEED TO KNOW ONLY Copyright 2002 Compaq Computer corporation. Protected as an unpublished work.
What Is in a Softdoc Softdoc Example h. Complete syntax, including supported Backup and Restore options and qualified fileset syntax, is available in the PAK/UNPAK help. (SOLN 10-020205-6454) Problems Corrected: NONE Known Problems Remaining: 1) [G06] PAK cannot compress OPEN files if the files are EXCLUSIVELY opened. SHARE option can be used to PAK the files opened for WRITE, but the resulting PAK file might be corrupted. For example, you cannot PAK edit files opened in read/write mode by EDIT or TEDIT.
What Is in a Softdoc Softdoc Addendum Example Softdoc Addendum Example SOFTWARE RELEASE DOCUMENT ADDENDUM Product Name: GHOST FTP CLIENT Product Number: TT1234G06 Date: 17SEP2002 PVU Number: T1234AE Copyright Notice: COMPAQ CONFIDENTIAL: NEED TO KNOW ONLY Copyright 2002 Compaq Computer Corporation Protected as an unpublished work.
What Is in a Softdoc Softdoc Addendum Example - Check "Manage OSS Files" option for the Target configuration. - 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: NONE - Run ZPHIRNM to perform the RENAME step. - Perform these post-installation steps: 1. On pre-G06.
What Is in a Softdoc Softdoc Addendum Example Managing Software Changes—427169-003 A-10
B What Is in an SPRNOTE SPRNOTEs 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 one or more softdoc addendums. DSV Information lists the files in the distribution subvolume (DSV) for the SPR. You can access SPRNOTEs through TIM Support Collections.
What Is in an SPRNOTE SID Fields SID Fields ID The unique identifier assigned to the SPR: Tnnnn product number Vnn product version aaa product version update ID Access Indicates the accessibility of the SPR, as described under SPR Attributes on page 1-4. Product Name 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 SPRNOTE • • SID Fields Install when convenient for fixes or new features that improve fault tolerance, availability, or problem diagnosis. Install if desired to avoid noncritical or highly unlikely problems or for new features. Changes Introduced in the SPR This section categorizes the changes 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.
What Is in an SPRNOTE • SPR Requisites No system impact SPR Requisites Direct Requisite A direct requisite is one that is cited in the softdoc addendum of the requiring SPR. Indirect Requisite An indirect requisite is a requisite of a requisite. Conditional Requisite A conditional requisite is one that is needed only under certain circumstances. For example, a conditional requisite might be required if: • • • You are using a certain RVU or set of RVUs. You are using a certain product version.
What Is in an SPRNOTE Softdoc Softdoc The next portion of the SPRNOTE, from the Product Name field through the Known Problems Remaining field, is a copy of the SPR softdoc addendum. An SPRNOTE for an unrestricted SPR contains all of the softdoc addendums appended to the initial PVU softdoc. See Appendix A, What Is in a Softdoc, for descriptions of the softdoc addendum fields. DSV Information Following the text of the softdoc addendum is a list of the files in the Y and R distribution subvolumes.
What Is in an SPRNOTE SPRNOTE Example SPRNOTE Example COMPAQ COMPUTERS INCORPORATED SPRNOTE BEGIN SID ID: T9208 D46 AAZ UNRESTRICTED DISK UTIL This SPR is applicable to these RVUs (as of 2002-AUG-30) D46.00 D47.00 D48.00 D48.01 D48.02 D48.03 G06.00 G06.01 G06.03 G06.04 G06.05 G06.06 G06.07 G06.08 G06.09 G06.10 G06.11 G06.12 G06.13 G06.14 G06.15 G06.16 NOTE: Applicable to pre-G06.12 only if not using New Features #1 and #2 introduced in T9208AAQ; applicable to pre-G06.
What Is in an SPRNOTE SPRNOTE Example Superseded PVUs: T9208AAO T9208AAP T9208AAQ T9208AAR T9208AAS T9208AAT T9208AAU T9208AAV T9208AAW T9208AAX T9208AAY Requisite PVUs: T9053AMH (See Note) Note: This SPR is required for Problem Corrected #1.
What Is in an SPRNOTE SPRNOTE Example The installation database is now updated properly, and INSTALL will later behave just as if you had continued with SYSGEN. 2. Manually replace and secure the SYSnn subvolume files that are the target of this SPR: a. b. c. d. e. f. > - FUP VOLUME $SYSTEM.SYSnn INFO /OUT $S/ * RENAME FCHECK, PURGEME.* DUP $.ZUTIL.
What Is in an SPRNOTE SPRNOTE Example contain different data patterns. LIKELIHOOD: Unlikely WORKAROUNDS: Close the affected file to force cache blocks to disk. SIDE-EFFECTS: CMFILE will flush the affected cache blocks. (SOLN 10-020820-1176) 2. [AAZ] SYMPTOMS: FILES command displays no file names. CONDITIONS: contains lower-case letters or VOLUME command specified with lower-case letters. LIKELIHOOD: Will occur. (SOLN 10-020820-1177) 3.
What Is in an SPRNOTE SPRNOTE Example Managing Software Changes—427169-003 B-10
C SPR Research Form Current Product on My System Product on RVU-ID SUT Substitute or Recommended Product Included in SPR on RVU-ID SUT Included in Substitute or Special Consid.
SPR Research Form Managing Software Changes—427169-003 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 you are running the DCE product on your current system. A search on DCE in the Content file for a newer RVU might reveal the following 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 Kernel 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 Kernel 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 NonStop Kernel 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 S02071 FCS NOTE - COMPAQ NONSTOP TUXEDO(R6.5) V3,UPDATE 3 27JUN02 SUMMARY: As of 26 June, 2002 Compaq NonStop Tuxedo (R6.5) V3, Update 3 is available as an Independent Product. DETAIL: The following products are available to order as Independent Products (IP): SPR ID: AAR SR62V3/SR63V3 - Compaq NonStop TUXEDO (R6.
Independent Products Policy Example of Support Note Announcing Availability of an IP Managing Software Changes—427169-003 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 ExpressNotice ExpressNotice. An automatic information delivery system that provides Software Revision Notifications regarding SPRs, Hotstuff messages, and Support Notes for a customer’s products and release version update (RVU). FCS. See first customer shipment (FCS). 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.
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 release document (softdoc) software release document (softdoc). A document that describes revision-dependent information regarding a software or firmware SPR. Software Revision Notification. A message announcing the availability of time-critical fix SPRs, Hotstuff messages, and Support Notes and that provides enough information to help you decide whether to research the SPRs further. SPR. See software product revision (SPR). SPR Introduction Document (SID).
Glossary Total Information Manager (TIM) Total Information Manager (TIM). A software product used to search and view product and support information contained within document collections on local CD-ROMs and online, Internet-accessible servers. unconditional requisite. A requisite that is needed if you use the requisite’s product and your software configuration does not already contain the needed function. unrestricted SPR. An SPR that is available to all customers to select and install individually.
Index A G Assessment of SPR 3-5 General Availability (GA) 1-10 C H Conditional requisite defined B-4 researching 3-13 Content file defined 2-6 researching regressions D-6 using D-1 Controlled Availability (CA) 1-10 Hotstuff messages defined 2-2, 2-6 examples of 2-8 general 2-7 OPNs 2-7, 3-3 Recall 2-7 Withdraw 2-7 I D Direct requisite B-4 Distribution subvolume (DSV) 2-5 DSM/SCM defined 2-4 product 4-4, 4-11, 5-3 reports 5-1 E Early Adopter Program (EAP) 1-9 Emergency overlay (EO) 1-7 Excluded SPR
Index P P Planned product maintenance defined 1-4 delivery attribute of SPR 1-3 delivery of 1-1 Primary requisite B-4 Product Maintenance Level (PML) 1-7 Product version update (PVU) defined 1-2 in an RVU 1-9 relationship to product version 1-3 Product version (PV) defined 1-2 listing 3-16, 4-5 Products delivered on SUT 4-5 obsolete D-3 PVU See product version update (PVU) R README file 2-6, 4-6, D-1 Recalled SPR 1-7 Release and Migration Information folder 2-4 Release Highlights guide 2-5 Release series
Index T Software product revision (continued) initial attribute 1-5 installing 4-3, 4-11, 5-3 log file 3-15, 4-4, 4-11, 5-1, 5-4 obsolete D-3 obtaining 4-3, 4-10, 5-3 planned product maintenance 1-4 recalled 1-7 requisite 1-6, 4-3, A-4, B-4 reviewing requisites 3-12 successive attribute 1-5 superseded 1-5, 4-3, 4-7/4-8, 4-10 time-critical fix 1-4 usable with an RVU 3-16, 4-2, 4-9 withdrawn 1-7 Software Revision Notifications contents 2-11 defined 2-2 delivery method 1-3 SPML 2-6 SPR See Software product r
Index U U Unconditional requisite B-4 Unrestricted SPR 1-4 W Withdrawn SPR 1-7 Managing Software Changes—427169-003 Index-4
