Availability Guide for Change Management Abstract This manual explains how to maximize system and application availability while successfully implementing changes to your NonStop system. It describes typical changes and their causes, explains how to change your NonStop system while it is still operational, and shows you how to reduce the time required for planned outages. Product Version N.A. Supported Releases This manual supports G01.
Document History Part Number Product Version Published 103394 N.A. December 1994 119224 N.A. December 1995 125506 N.A. December 1996 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .99 site update tape (SUT). Ordering Information For manual ordering information: domestic U.S.
New and Changed Information The Availability Guide for Change Management manual has been revised to reflect changes for G01: Product/Feature/Enhancement Sections Affected CMI and CMP are replaced by SCF on G-series systems: • Where CMI and CMP are described, replace with SCF descriptions. • Where CMI and CMP examples are shown, replace with SCF examples. • Remove CMI and CMP from list of change management tools.
New and Changed Information Product/Feature/Enhancement Sections Affected Install is replaced by DSM/SCM (Delphi) on G-series: • Where Install is described, replace with DSM/SCM. • Where Install examples are shown, replace with DSM/SCM. • Add DSM/SCM to the list of change management tools, and remove Install. Sections 1, 3, and 6 NonStop Net/Master and RDF will not be in G01: • Where NonStop Net/Master and RDF are described, remove references.
Contents New and Changed Information iii About This Manual xi Notation Conventions xv 1.
Contents 4. Making Application Subsystem Changes Online Installing an IPM 3-2 Hardware Changes 3-2 Performing Common Hardware Changes Online 3-2 Online Changes That Require Tandem Assistance 3-3 Adding and Upgrading Processors Online 3-3 Adding and Upgrading Processor Memory Online 3-4 ServerNet Adapters 3-4 Adding, Upgrading, and Moving Disk Drives Online 3-5 Updating Firmware Online 3-6 Where to Find More Information 3-7 4.
6. Reducing the Time Required for Planned Outages Contents Expand 5-3 Device-Specific Connections 5-3 SNA Network Connections 5-3 OSI Network Connections 5-3 LAN Connections 5-4 TCP/IP Network Connections 5-4 Common Communications Subsystem Changes 5-4 Changes You Can Perform Online 5-4 Communications Subsystem Tool 5-4 Communications Subsystems Summary 5-5 Where to Find More Information 5-7 6.
Glossary Contents Where to Find More Information 7-9 NonStop TS/MP Management Tools 7-9 NonStop TS/MP Management Interfaces 7-10 How the NonStop TS/MP Management Interfaces Work 7-10 Considerations and Limitations of the NonStop TS/MP and Pathway/TS Management Interfaces 7-11 PATHCOM Command Example 7-11 Where to Find More Information 7-12 NonStop SQL/MP Management Tools 7-12 NonStop SQL/MP Management Interfaces 7-12 How SQLCI Works 7-12 Considerations and Limitations of SQLCI 7-13 SQLCI Example 7-13 Wher
Contents Table 1-1. Table 3-1. Table 3-2. Table 4-1. Table 4-2. Table 4-3. Table 4-4. Table 4-5. Table 4-6. Table 4-7. Table 4-8. Table 5-1. Table 6-1. Table 6-2. Table 6-3. Table 7-1.
Contents Availability Guide for Change Management–125506 x
About This Manual The Availability Guide for Change Management explains how to maximize system and application availability while successfully implementing changes to your NonStop system.
What’s in This Manual? About This Manual What’s in This Manual? This manual is organized in seven sections and a glossary. The glossary defines technical terms and acronyms. • • • • Section 1, “Introduction to Change Management,” describes the factors that cause change, defines change management in the Tandem environment, describes the goals of change management, explains how Tandem measures outages, and shows how change management relates to the operations management (OM) model.
Where to Find More Information About This Manual Where to Find More Information The following manuals contain information that may also be of interest to readers of this manual: • • • • • • • The Introduction to NonStop Operations Management introduces managers to NonStop system operations.
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 returning a Reader Comment Card or by sending an Internet mail message. A Reader Comment Card is located at the back of printed manuals and as a separate file on the Tandem User Documentation disc of the Tandem Information Manager (TIM) product. You can either FAX or mail the card to us. The FAX number and mailing address are provided on the card.
Notation Conventions General Notation Boldface type is used to set off definitions of technical terms and acronyms. Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply.
Syntax Notation Notation Conventions Availability Guide for Change Management–125506 xvi
1 Introduction to Change Management Overview Businesses today are facing an ever-increasing rate of change worldwide. To succeed in this rapidly changing environment, businesses must develop a risk-driven strategy where change is assessed, mastered, controlled, and used to improve the competitiveness of the business. Change should no longer be viewed as something that should be minimized or avoided—it should be seen as a process that can be used to succeed.
Introduction to Change Management Increasing Availability by Effectively Managing Change Offering services around the clock requires computer and network services that are available all the time. The cost of downtime, even a few minutes, can be dramatic in lost revenue, lost consumer confidence, and lost productivity. The following are some examples of lost revenue caused by computer downtime: • • When an airline’s reservation system went down, thousands of travel agents had to book flights manually.
Introduction to Change Management Controlling the Introduction of Change Evaluating System Performance and Growth Evaluating system performance and growth involves tracking and anticipating growth and then establishing plans to accommodate that growth. Tandem provides a wide variety of tools that provide data useful for your growth forecasts. These tools, and performance-management tasks, are described in the Introduction to NonStop Operations Management.
Introduction to Change Management Installing and Implementing Changes Installing a New Operating System Release Tandem currently requires that you shut down your NonStop system to install any major operating system release. You use the Distributed Systems Management/ Software Configuration Manager (DSM/SCM) program to install a new version of the operating system.
Introduction to Change Management Meeting the Goals of Change Management Installing and Reconfiguring Communications Subsystems In the Tandem environment, a software product that provides users with access to a set of communications services is called a communications subsystem. Making changes to a communications subsystem can involve adding new communications lines or devices to accommodate business growth, connecting new systems to the network, or reconfiguring certain configuration attributes.
Introduction to Change Management Reducing the Time Required for Planned Outages Reducing the Time Required for Planned Outages An outage is time during which your NonStop system is not capable of doing useful work. From the end-user’s perspective, an outage is any time an application is not available.
Measuring Outages by Outage Minutes Introduction to Change Management ability to access the service, the quality of the service provided, and the acceptability of the response time to the user. While major changes—such as installing a new operating system release—obviously affect availability, the effect of other types of changes may be less apparent but can also affect end-user availability.
Introduction to Change Management Change Management and the OM Model supplement its measure of downtime by keeping records of the number of transactions it normally processes by minute and by day of the week. If an outage occurs, for example, at 10 a.m. on Tuesday morning and lasts for 15 minutes, the site can calculate the average number of transactions that would normally be processed during that period. Subsequently, the site pays a corresponding penalty to its customer.
Introduction to Change Management • Change Management and the OM Model The Availability Guide for Performance Management describes how to manage the performance of your NonStop system.
Introduction to Change Management Change Management and the OM Model Availability Guide for Change Management–125506 1- 10
2 Change Control Overview Making changes to your system and application environment can increase the effectiveness of your operations—or can result in confusion and problems. The difference between success and failure depends on how well your organization manages change. By establishing a formal change-control process, you can ensure that change proceeds smoothly and with minimal impact on system and application availability.
Implementing Change Control Successfully Change Control Implementing Change Control Successfully Change control is most effective when the following prerequisites are met: • • A single point of control exists in the form of a person or group with overall authority to implement change. Making a person or group responsible for change control prevents unauthorized personnel from accessing and changing the system. The person or group responsible for implementing the change has received the proper training.
Phase 1—Definition and Documentation Change Control Phase 4—Verification. In this phase, the person or group responsible for change control makes sure that the system is running correctly and reviews the change-control process to make any necessary improvements. The following paragraphs provide guidelines for accomplishing each phase of the change-control process.
Phase 1—Definition and Documentation Change Control • • • • The estimated duration of the outage. (Tandem recommends that you measure outages in minutes. Section 1, “Introduction to Change Management,” describes how to measure outages in minutes.) The reason for the outage. The name of the person or group requesting the outage. Applications affected by the outage. Figure 2-1 shows an example of a planned outage request form. Note. The maximum times on the following form are only examples.
Phase 1—Definition and Documentation Change Control Figure 2-1. Planned Outage Request Form Planned Outage Request Form REQUESTED BY DATE REQUEST FORM SUBMITTED DATE OF OUTAGE TRACKING NUMBER Application/system shutdown Maximum (Minutes) 60 Requested (Minutes) Actual (Minutes) Downtime work (move files, add hardware, SQL compiles, etc.
Phase 2—Change Planning Change Control Phase 2—Change Planning One of the most difficult tasks in change control is determining how the change affects your system and application availability. If the change affects availability, you also need to determine how to minimize system or application downtime when implementing the change. Thoroughly assessing the impact of change, determining what resources are required to implement the change, and creating a plan for the change help minimize planned outage time.
Phase 2—Change Planning Change Control If the change was requested by another person or group (other than the person or group responsible for change control), the person or group responsible for change control should perform the following tasks: • • Verify that the information provided about the proposed change is correct. Submit a list of requirements to the person or group that requested the change. Requirements usually include the following: • • • • All changes should pass user-acceptance testing.
Phase 2—Change Planning Change Control Determining When to Make the Proposed Change You can use the following check list to determine when to schedule the proposed change: • • • • • • • Can you, or should you, combine the proposed change with other planned outages to minimize planned downtime? Which days of the week or time periods are or are not available for planned downtime? Are there certain days in the month that must be avoided? What are the resource availability constraints and deadlines? When is
Phase 3—Implementation Change Control Testing the Change Plan All procedures should be tested before the change plan is implemented. Make sure that time is allowed to modify the plan based on the test results. Test activities should include: • • • Testing the plan on a “crash and burn” system (ideal), or walking through the plan with the implementation staff (next best alternative). Testing outage minute estimates.
Process Flow Diagram Change Control After the change is successfully implemented and tested, the person or group responsible for change control should maintain records of the changes that took place, including all forms and signatures, and should document the results of the change. Process Flow Diagram Figure 2-2 is a high-level process flow diagram of how a change plan is implemented.
Process Flow Diagram Change Control Figure 2-2.
Process Flow Diagram Change Control Availability Guide for Change Management–125506 2- 12
3 Making System Software and Hardware Changes Online Overview Being able to make changes to your system software and hardware online is one way you can reduce—or even eliminate—planned outages. Changing your system software and hardware can involve installing a new operating system release, expanding your system to include a new system component, upgrading a system component to take advantage of a new technology, or simply moving an existing system component.
Making System Software and Hardware Changes Online • Installing a New Operating System Release SCF is Tandem’s online configuration and management tool used for configuring system objects or monitoring their status. Making changes to communications subsystems is discussed in Section 5, “Making Communications Subsystem Changes Online.” SCF is also described in Section 7, “Tools for Online Change.
Making System Software and Hardware Changes Online Online Changes That Require Tandem Assistance Online Changes That Require Tandem Assistance With the proper planning, your Tandem CE or SE may be able to help you perform the following hardware changes online: • • • Adding, upgrading, and moving I/O expansion cabinets Adding, upgrading, and moving system cabinets Adding, upgrading, and moving external cabinets If you would like more information on performing these types of hardware changes, contact you
Making System Software and Hardware Changes Online • Adding and Upgrading Processor Memory Online If you are upgrading processors 0 and 1 in the base cabinet, you must shut down the system. Adding and Upgrading Processor Memory Online To add or upgrade processor memory online, you install either a memory board or a processor board, depending on the type of NonStop system that you have. No softwareconfiguration changes are necessary. Actual hardware installation steps are system-specific.
Making System Software and Hardware Changes Online Adding, Upgrading, and Moving Disk Drives Online Adding, Upgrading, and Moving Disk Drives Online Adding, upgrading, or moving a disk drive online involves the following steps: 1. Using SCF to add a disk 2. Physically installing the disk drive 3. Preparing the new disk drive after installation Using SCF To Add a Disk You use the SCF command to add disks to the system configuration database.
Making System Software and Hardware Changes Online Updating Firmware Online Considerations for Adding, Upgrading, and Moving Disk Drives The following list describes considerations and limitations you should be aware of when adding, upgrading, and moving disk drives online: • • • The $SYSTEM disk and any alternate system volume must be configured by SYSGENR. You cannot make changes to the system disk online.
Making System Software and Hardware Changes Online Where to Find More Information Online Firmware Update Procedure Updating firmware online consists of three steps: 1. Checking the firmware status 2. Updating any firmware that is out-of-date 3. Checking the firmware status again to make sure that all of the firmware is up-todate You can perform all three steps using TSM, which is described in the TSM Configuration and Management Guide. An overview of TSM is provided in Section 7, “Tools for Online Change.
Making System Software and Hardware Changes Online Where to Find More Information Table 3-2. Where to Find Additional Configuration Information Manual What it explains DSM/SCM User’s Guide How to plan for, manage, and install software on distributed Tandem systems. Subsystem Control Facility (SCF) Reference Manual for G-Series Releases How to alter the configuration of communications subsystems online.
4 Making Application Subsystem Changes Online Overview The Tandem application environment enables you to develop and run high-performance, high-volume, and highly available online transaction-processing (OLTP) applications. Making changes in your application environment can involve adding requester and server programs to handle new types of transactions, reorganizing a database to accommodate business growth, or simply reconfiguring certain configuration attributes.
Making Application Subsystem Changes Online • • • • The Transaction-Processing Application Environments The Tandem NonStop Kernel, the operating system that provides low-level functions such as interprocess message management, file management, memory management, and so on. The operating system provides two operating environments: • • Open System Services (OSS) environment Guardian environment A device and transaction control system that supports complex applications in a network environment.
Client/Server Computing and the Tandem Application Environment Making Application Subsystem Changes Online Figure 4-1.
Making Application Subsystem Changes Online Client/Server Computing and the Tandem Application Environment Users typically request information from server programs through an easy-to-use graphical user interface (GUI) provided by the client program. The client/server architecture is usually linked together by a local area network (LAN). You can design client/server implementations of Tandem’s application environment using products provided by Tandem.
Making Application Subsystem Changes Online Making Changes to NonStop TS/MP Online Making Changes to NonStop TS/MP Online You may need to change your transaction-processing environment to accommodate new application requirements or new users or to satisfy new transaction throughput and response time requirements. Tandem designed its transaction-processing services to expand easily as OLTP operations evolve and business needs change.
Making Application Subsystem Changes Online NonStop TS/MP Changes You Can Perform Online NonStop TS/MP Changes You Can Perform Online Making changes to NonStop TS/MP does not require the NonStop system to be shut down, and most changes can be made without affecting the availability of the transaction-processing application. The following subsections describe common transaction-processing environment changes.
Making Application Subsystem Changes Online NonStop TS/MP Changes You Can Perform Online Table 4-1. PATHMON Object Changes Object must be stopped? Type of change Object Changing backup processors and dump files PATHMON TCP* X X Exchanging primary and backup processors PATHMON TCP* X X Deleting objects TCP* TERM* PROGRAM* SERVER X X TCP* TERM* PROGRAM* SERVER X X Altering object attributes Yes No X X X X * TCP, TERM, and PROGRAM are Pathway/TS objects managed by the PATHMON process.
Where to Find More Information Making Application Subsystem Changes Online Summary of NonStop TS/MP Changes Table 4-2 summarizes the NonStop TS/MP changes described in this subsection. Table 4-2. Summary of NonStop TS/MP Changes Impact on Availability Type of change NonStop system Application Adding or replacing hardware Available Available. Adding or deleting objects controlled by PATHMON Available Available.
Making Application Subsystem Changes Online Making Changes to NonStop SQL/MP Online Making Changes to NonStop SQL/MP Online You may need to change your NonStop SQL/MP database to accommodate business growth or to add new capabilities. Tandem designed NonStop SQL/MP to accommodate growth easily—you can change data definitions as your database changes and grows. NonStop SQL/MP includes utilities that make database growth possible and easy.
Overview of NonStop SQL/MP Making Application Subsystem Changes Online • • • • SQLCI commands—SQLCI commands enable you to set and display the SQLCI environment. Report Writer—A full-function report-writing facility that formats custom reports. Utilities—A full set of utilities that provide quick access to information about the database, the data dictionary, and the application programs. Programmatic SQL—The NonStop SQL/MP application programming interface.
Making Application Subsystem Changes Online NonStop SQL/MP in the Client/Server Environment NonStop SQL/MP in the Client/Server Environment In the client/server environment, the client (a PC, Macintosh, or workstation) accesses NonStop SQL/MP by sending SQL statements to Tandem gateway software. The gateway software retrieves information from the NonStop SQL/MP database, which resides on the server (a NonStop system).
Making Application Subsystem Changes Online NonStop SQL/MP Changes You Can Perform Online NonStop SQL/MP Changes You Can Perform Online When you make changes to a NonStop SQL/MP database, you do not need to shut down the NonStop system, and most changes can be made without affecting NonStop SQL/MP application availability.
Making Application Subsystem Changes Online NonStop SQL/MP Changes You Can Perform Online can move all or part of a partition to other disk volumes while allowing full update access to the data in the partition. Reducing the Frequency of Database Reorganizations Another way you can reduce the impact of database reorganizations on application availability is to reduce their frequency.
Making Application Subsystem Changes Online NonStop SQL/MP Changes You Can Perform Online that reference the objects, providing the SQL object has its SIMILARITY CHECK option set to ENABLE. Two objects are considered to be similar if the same execution plan can be used to access either object. An operable plan is semantically correct and can execute correctly without SQL recompilation (although it might not be optimal) while an inoperable plan must be recompiled to execute correctly.
Where to Find More Information Making Application Subsystem Changes Online Summary of NonStop SQL/MP Changes Each of the changes described in this subsection can have some impact on application availability. Determining the impact of a specific change on application availability requires a thorough understanding of NonStop SQL/MP database management as well as the customer application. None of the changes described in this subsection affect system availability.
Making Application Subsystem Changes Online Making Changes to NonStop TM/MP Online Making Changes to NonStop TM/MP Online You may need to change your NonStop TM/MP configuration to accommodate business growth or to respond to changing business factors requiring an increased or decreased level of protection for your database. This subsection: • • Provides a brief overview of NonStop TM/MP Describes the changes you can make to NonStop TM/MP online Note.
NonStop TM/MP in the Client/Server Environment Making Application Subsystem Changes Online Database Tables and Files When configuring your NonStop TM/MP environment, you must identify all disk volumes that will be protected by the TMF subsystem. These disk volumes are called data volumes. Online dumps are copies of audited files residing on data volumes. If the database is damaged, the TMF subsystem can restore the online dump files to disk and apply the audit-trail images to reconstruct the files.
Making Application Subsystem Changes Online TMF Subsystem Changes You Can Perform Online can be fully protected by NonStop TM/MP regardless of whether transactions are initiated by a client (a PC, Macintosh, or workstation) or by a requester on a NonStop system. TMF Subsystem Changes You Can Perform Online Making changes to the TMF subsystem does not require the NonStop system to be shut down, and most changes can be made without affecting the availability of applications that use the TMF subsystem.
TMF Subsystem Changes You Can Perform Online Making Application Subsystem Changes Online Changing the Data-Volume Configuration Data-volume configuration changes can have various effects on the TMF subsystem. For example, adding a data volume can potentially increase the number of audit records generated. You can perform data-volume configuration changes while the TMF subsystem is running. Depending on your application, some changes may require application access to the data volume to be stopped.
Making Application Subsystem Changes Online TMF Subsystem Changes You Can Perform Online Table 4-6.
Where to Find More Information Making Application Subsystem Changes Online Table 4-8. Summary of TMF Changes Impact on Availability Type of change NonStop system Application Changing the audit-trail configuration Available Adding an entire audit trail or resetting the audit-trail file size requires the TMF subsystem to be stopped and the TMF configuration to be deleted; other changes do not affect availability.
Making Application Subsystem Changes Online Making Changes to Transaction-Processing Monitoring Environments Online Making Changes to Transaction-Processing Monitoring Environments Online Although originally developed to optimize the performance and availability of OLTP applications running on mainframe systems, transaction-processing (TP) monitors perform the same functions for client/server OLTP applications.
The NonStop TUXEDO Environment Making Application Subsystem Changes Online Figure 4-5.
Making Application Subsystem Changes Online The NonStop TUXEDO Environment Because the NonStop TUXEDO system uses the Tandem core services, however, there are administrative tasks that are unique to the NonStop TUXEDO system. These tasks are described later in the subsection “Administration of the Core Services.” This section and the subsections following provide an overview of the NonStop TUXEDO administrative environment. For more detailed information, see the NonStop TUXEDO System Administration Guide.
Making Application Subsystem Changes Online The Pathway Environment The NonStop TM/MP core service must be started, monitored, and maintained as a separate subsystem. Usually, the Tandem system administrator performs these tasks. (Each NonStop system includes one—and only one—instance of the NonStop TM/MP product, which is used by many subsystems.
The Pathway Environment Making Application Subsystem Changes Online Figure 4-6.
Making Application Subsystem Changes Online The Pathway Environment RSC The RSC product enables PC, Macintosh, or workstation applications to access Pathway servers and other Tandem NonStop servers on the Tandem host system. RSC resides in both the client and server environments. The workstation is the client; the Tandem host system, with its Pathway transaction-processing software, is the server.
Making Application Subsystem Changes Online • The Pathway Environment Intelligent Device Support (IDS) Facility—A facility that increases the number of device types that can be handled by the TCP, thereby extending access to Pathway server classes to a wide range of intelligent devices. IDS is part of the TCP.
Making Application Subsystem Changes Online The Pathway Environment For more information about managing the Pathway environment using the management programming interface, see the following manuals: • • NonStop TS/MP and Pathway Management Programming Commands Manual NonStop TS/MP and Pathway Management Programming Messages Manual RSC Changes You Can Perform Online Administrators configure and control the TDP and the RSC environment by using the Remote Server Call command interface (RSCCOM).
Making Application Subsystem Changes Online Availability Guide for Change Management–125506 4- 30 The Pathway Environment
5 Making Communications Subsystem Changes Online Overview In the Tandem environment, a software product that provides users with access to a set of communications services is called a communications subsystem. Because connectivity is an important part of online transaction processing (OLTP), Tandem offers a variety of communications products. These products extend the OLTP power of your NonStop system by supporting a wide range of application and networking configurations.
Making Communications Subsystem Changes Online I/O Processes To use any device or communications line, other processes send requests to the I/O process that owns the device or line. The I/O process, in turn, calls its own procedures to handle the protocols of the devices or lines it controls and to achieve the physical transfer of data. Figure 5-1 illustrates how calls are passed from a user process to an I/O process, and then to physical devices or communications lines: 1.
Making Communications Subsystem Changes Online Overview of Communications Products Overview of Communications Products The communications products provided by Tandem can be organized in the following categories: • • • • • • The Expand network Device-specific connections SNA network connections OSI network connections (including X.25) Local area network (LAN) connections TCP/IP network connections Note.
Making Communications Subsystem Changes Online LAN Connections LAN Connections LAN connections include products that allow NonStop systems, workstations, and other systems and devices to communicate across LANs. Tandem offers LAN interface products based on standard and de facto standard LAN protocols. Tandem LAN connectivity allows NonStop systems and Expand networks to be integrated with existing LANs.
Making Communications Subsystem Changes Online Communications Subsystems Summary Depending on the communications subsystem, you may be able to use SCF commands to perform the following changes online: • • • Add communications lines, devices, and subdevices Delete communications lines, devices, and subdevices Alter the characteristics of communications lines, devices, and subdevices SCF cannot modify I/O processes while they are running—the I/O process must be stopped, altered, and then restarted.
Making Communications Subsystem Changes Online Communications Subsystems Summary Table 5-1.
Making Communications Subsystem Changes Online Where to Find More Information Where to Find More Information The following table lists the manuals that describe the commands and procedures used to perform the online changes described in this section. For information on this topic Read these manuals Making changes with SCF Subsystem Configuration Facility (SCF) Reference Manual for G-Series Releases Each communications subsystem that can be changed with SCF also has its own SCF manual.
Making Communications Subsystem Changes Online Where to Find More Information Availability Guide for Change Management–125506 5 -8
6 Reducing the Time Required for Planned Outages Overview Your NonStop system is designed so that most changes can be performed while the system is still operational. However, certain changes must be done offline. Offline change is any change that requires your NonStop system to be shut down. Offline changes are usually performed during a planned outage. A planned outage is system or application downtime that is planned or scheduled.
Reducing the Time Required for Planned Outages Anticipating and Planning for Change Table 6-1. Performance-Management Tasks Task What it involves Application sizing Forecasting the effects of new applications on your system through the use of models to determine how well new applications will handle their intended workloads. Application sizing helps you plan for growth in system workloads caused by new applications.
Reducing the Time Required for Planned Outages Anticipating and Planning for Change Providing Adequate Computer Room Resources Some changes, such as adding new hardware, can require more power and air conditioning. You can avoid unnecessary downtime by providing adequate physical space and ensuring that you have enough power and cooling capacity for additional equipment.
Can the Change Be Performed Online? Reducing the Time Required for Planned Outages Can the Change Be Performed Online? You can perform many changes to your NonStop system online. Online change is any change that can be performed while your NonStop system is still operational. Sections 4, 5, and 6 of this manual are designed to help you determine whether the changes you want to make can be performed online. Table 6-3 describes the contents of these sections. Table 6-3.
Reducing the Time Required for Planned Outages Writing Efficient Startup and Shutdown Command Files You can improve the efficiency of your startup and shutdown command files by applying the following simple techniques: • • • Use command file syntax that executes quickly. Make sure that command files execute without manual intervention. Set up command files to execute in parallel. Command File Syntax The syntax used in command files affects the time it takes for them to execute.
Reducing the Time Required for Planned Outages Using Parallel Processing Avoiding Manual Intervention Write your startup and shutdown files so that they execute correctly without requiring manual intervention. Any time an operator must intervene, startup and shutdown time is lengthened. In addition, operator intervention increases the possibility of introducing unwanted errors that could further delay startup or shutdown.
Reducing the Time Required for Planned Outages Product-Specific Techniques Example 2: Starting a Transaction-Processing Application in a PATHMON Environment You can reduce the time required to start a transaction-processing application in a PATHMON environment by using multiple startup command files in different processors. To implement this technique, you must divide your PATHMON configuration into convenient and related units.
Reducing the Time Required for Planned Outages Reducing Downtime When Installing a New Operating System Reducing Downtime When Installing a New Operating System Tandem currently requires that you shut down your NonStop system to install any major operating system release and some critical IPMs. Using DSM/SCM minimizes your system down time in the following ways: • By requiring you to stop only applications being updated.
Reducing the Time Required for Planned Outages Reducing Application Downtime With DSM/SCM Reducing Application Downtime With DSM/SCM DSM/SCM is a Windows-based graphical user interface product that simplifies the process of installing, configuring, and managing software for a single NonStop server or a network of NonStop servers. With DSM/SCM, most installation and management tasks can be performed without disrupting other activities on the server.
Reducing the Time Required for Planned Outages Availability Guide for Change Management–125506 6- 10
7 Tools for Online Change Overview Tandem provides a variety of tools to enable you to make changes to your hardware and software online. Online change is any change that can be performed while your NonStop system is still operational. In some situations, online changes may temporarily affect application availability. This section describes the features and capabilities of the online change tools referred to in previous sections of this manual.
How SCF Works Tools for Online Change Table 7-1. SCF Online Reconfiguration Commands Command What it does ADD Adds an object to a communications subsystem. ALTER Changes the value of one or more attributes of a communications subsystem object. DELETE Removes an object from a communications subsystem. START Starts the operation of an object after it has been added or altered. STOP Stops the operation of an object. Usually an object must be stopped before it can be altered or deleted.
SCF Subsystems for G-Series Releases Tools for Online Change SCF Subsystems for G-Series Releases The following subsystems are supported by SCF for G-Series releases. Of these subsystems, the KERNEL, SLSA, STORAGE, and WAN subsystems are controlled by generic process management processes that support persistent configuration that survives a system load. Generic processes are described in the SCF Reference Manual for the Kernel Subsystem.
Considerations and Limitations of SCF Tools for Online Change • • • Tandem TELSERV WAN* X25AM * This subsystem is controlled by a generic process management process that supports persistent configuration, which can survive a system load. Generic processes are described in the SCF Reference Manual for the Kernel Subsystem. Note. Not all the objects described in this manual are available with the current release of the operating system.
SCF Command Example Tools for Online Change Changes made with older SCF subsystems do not survive a system load or a reload of a processor pair. You can bypass this limitation of SCF by setting up a command file that contains all of your SCF changes. Invoke this command file when the system is loaded (or have the command file execute from a system startup file) so that SCF changes are reentered.
TSM Interface Tools for Online Change TSM Interface TSM consists of software components that run on your Himalaya S-series server and on a PC-compatible workstation. The TSM software on the workstation features an easyto-use GUI that contains extensive online help.
TSM Components Tools for Online Change service processors (MSPs). (The workstation can also communicate directly with the MSPs on the Himalaya S-series server when the NonStop Kernel operating system is running.) A service processor (SP) is a physical component of the Himalaya S-series server that controls environmental and maintenance functions. The MSPs provide basic service processor functions as well as a TSM workstation port, the modem port for remote support functions, and system-load control.
Incident Reports Tools for Online Change Notifications Notifications are messages that indicate the state of resources on the Himalaya S-series server. There are two types of notifications: • • TSM application notifications Service processor (SP) event messages TSM Application Notifications TSM application notifications are generated by the TSM server software on the Himalaya S-series server.
TSM EMS Event Viewer Tools for Online Change Text and alarm attachments can also be included with a problem incident report. A text attachment is a file that you add to the incident report; it could include special information that you want to give to your service provider. An alarm attachment is a log of the alarms related to the problem being reported. Problem incident reports are forwarded only to the TSM Notification Director running on the TSM workstation configured as the primary dial-out point.
NonStop TS/MP Management Interfaces Tools for Online Change The NonStop TS/MP product provides a central control process, PATHMON, and interfaces to this process that manage both the NonStop TS/MP core service and the optional Pathway/TS software for terminal requesters. Together, these products are referred to as the Pathway environment.
Considerations and Limitations of the NonStop TS/MP and Pathway/TS Management Interfaces Tools for Online Change Figure 7-2 shows how PATHCOM and the NonStop TS/MP and Pathway/TS management programming interface send commands and instructions to PATHMON. Figure 7-2.
Where to Find More Information Tools for Online Change Where to Find More Information The PATHCOM interface is described in the NonStop TS/MP and Pathway Management Reference Manual. The NonStop TS/MP and Pathway Management Programming Commands Manual describes the token-oriented management programming interface to NonStop TS/MP and Pathway/TS. NonStop SQL/MP Management Tools NonStop SQL/MP is a relational-database-management system that supports high-speed access and updates to distributed data.
Considerations and Limitations of SQLCI Tools for Online Change Figure 7-3. How SQLCI Works SQLCI SQL Statements Command Terminal Commands Database Host Language Program Utilities Report Writer CDT 012 Considerations and Limitations of SQLCI Section 4, “Making Application Subsystem Changes Online,” describes the changes you can make to NonStop SQL/MP online, including which types of changes can affect system and application availability.
NonStop TM/MP Management Tools Tools for Online Change NonStop TM/MP Management Tools The NonStop TM/MP product protects databases in OLTP environments using its main functional component, the TMF subsystem. The TMF subsystem manages database transactions, keeps track of database activity through audit trails, and provides database recovery methods. The NonStop TM/MP product is one of the core services that make up the Tandem application environment.
Considerations and Limitations of the TMF Management Interfaces Tools for Online Change Figure 7-4. TMFCOM and Management Application Program Interfaces TMFCOM Management Application Process TMFSERVE TMFSERVE Command terminal TMP Considerations and Limitations of the TMF Management Interfaces Section 4, “Making Application Subsystem Changes Online,” describes the changes you can make to NonStop TM/MP online, including which types of changes can affect system and application availability.
Tools for Online Change Where to Find More Information Availability Guide for Change Management–125506 7- 16
Glossary This glossary includes a selection of terms used in this manual. Definitions of application and communications subsystem terms are brief and not very detailed; they are intended only to make this manual more meaningful than it would otherwise be to readers unfamiliar with Tandem’s application and communications subsystems. active audit trail. The set of audit-trail files that reside on an active audit volume. active audit volume. The disk volume configured to contain audit-trail files.
auxiliary audit trail Glossary auxiliary audit trail. An audit trail configured in addition to the master audit trail. availability. Tandem is using this term to describe end-user availability. End-user availability is the amount of time an application running on a Tandem system can be used effectively by the user of that application. catalog. A set of tables containing the descriptions of SQL objects such as tables, columns, indexes, views, files, and partitions. change control.
CONFTEXT file Glossary CONFTEXT file. An EDIT file containing a series of statements that define the hardware and software components of your NonStop system. The CONFTEXT file is an input file to the SYSGEN program. CRU. See customer-replaceable unit (CRU). customer-replaceable unit (CRU). A term used to describe certain system components that can be installed and removed by Tandem customers while the NonStop system is operating. data definition language (DDL).
entry-sequenced file Glossary entry-sequenced file. A file in which each new record is stored at the end of the file in chronological sequence and whose primary key is a system-generated record address. environmental outage class. An outage class that includes failures in power, cooling, network connections, natural disasters (earthquake, flood), terrorism, and accidents. Expand.
interim product modification (IPM) Glossary interim product modification (IPM). An interim software release that may include one or more fixes to Tandem code or may contain code that adds function to a Tandem software product. You receive an IPM on a BACKUP tape that contains the updated program and documentation files in one or more distribution subvolumes (DSVs). invalid object.
Glossary NonStop Open Database Connectivity (ODBC) Server NonStop Open Database Connectivity (ODBC) Server. A client/server product that allows client applications that use either the ODBC interface or the SQL Server interface to access NonStop SQL/MP databases. ODBC is a database connectivity standard developed by the SQL Access Group (SAG). SQL Server is a de facto standard. NonStop SQL/MP.
online transaction processing (OLTP) Glossary online transaction processing (OLTP). A method of processing transactions in which entered transactions are immediately applied to the database. The information within the database is readily available to all users through online screens and printed reports. online transaction-processing application. A set of programs that perform online transaction-processing (OLTP) tasks on behalf of the user.
partial SYSGEN phase Glossary partial SYSGEN phase. A procedure that may be able to help you to reduce the impact of interim product modification (IPM) installation on system and application availability. The partial SYSGEN phase does not require a system load and may also eliminate the need to stop your applications. partition. The portion of a table or index that resides on a particular disk volume. PATHCOM.
phantom device Glossary phantom device. A device that is configured but that is not physically present. You can make a phantom device operational without having to bring your NonStop system down. Configuring phantom devices is one way you can plan for future growth. physical outage class. An outage class that includes physical faults or failure in the hardware. Any type of hardware component failure belongs in this category. planned outage.
report writer Glossary (the client) to a Pathway application running on a NonStop system (the server) using a supported communications protocol. report writer. The SQLCI component used to produce specially formatted reports from queries. requester server approach. An approach to application design that divides the tasks of data input, data manipulation, and data output between two basic processes, requesters and servers. requesters.
SQL object Glossary SQL object. A NonStop SQL/MP database entity that is created, manipulated, or dropped by SQL statements and that is described in an SQL catalog. Tables, views, indexes, collations, and constraints are SQL objects. SQLCI (NonStop SQL/MP conversational interface.
Tandem application environment Glossary Tandem application environment. An environment that enables you to develop and run high-performance, high-volume, online transaction-processing (OLTP) applications on NonStop systems. NonStop Transaction Services/MP (NonStop TS/MP), NonStop SQL/MP, and NonStop Transaction Manager/MP (NonStop TM/MP) are the three key products that make up the Tandem application environment. Tandem DAL Server. See Tandem Data Access Language (DAL) Server.
unplanned outage Glossary unplanned outage. Time during which the system is not capable of doing useful work because of an unplanned interruption. Unplanned interruptions can include failures caused by faulty hardware, operator error, or disaster. view. A table derived by projecting a subset of the columns, restricting a subset of the rows, or both, from one or more other tables and views.
wild-card character Glossary Availability Guide for Change Management–125506 Glossary -14
Index A C Active audit trail 4-16 Active audit volumes 4-16 Adding communications lines and devices 5-5 disk controllers 3-5 disk drives 3-5 hardware 1-4, 4-6 memory 3-4 PATHMON-controlled objects 4-6 processors 3-3 Air conditioning capacity 6-3 Altering input/output processes 5-5 PATHMON environment owner and security attributes 4-7 PATHMON owner attribute 4-7 PATHMON-controlled objects 4-6 Anchor partition 4-14 Application subsystems, reconfiguring See NonStop SQL/MP, NonStop Transaction Manager/MP, Non
D Index Remote Server Call 4-27 Tandem Data Access Language Server 4-11 Command files 6-4/6-6 Communications lines, starting 6-6 Communications Management Interface communications products supported by 5-5 definition 3-1 Communications products 5-3/5-4 Communications subsystems changes you can make online to 5-4/5-5 definition of 5-1 device-specific connections 5-3 Expand 5-3 functions of 5-1 Local area networks 5-4 manuals for 5-7 Open Systems Interconnections (OSI) network 5-3 products 5-3 reconfiguring
E Index upgrading 3-5 Disk utilization 6-1 Distributed Systems Management 5-4, 7-10, 7-14 Distributed Systems Management/Software Configuration Manager 1-4, 3-2, 6-9 DML statements See Data manipulation language statements Downtime, cost of 1-2 DSM/SCM See Distributed Systems Management/Software Configuration Manager Dynamic System Configuration adding controllers with 3-5 communications subsystems supported by 5-5 definition 3-1 Graphical user interfaces 4-3 Growth forecasts 6-1 Guardian Performance Ana
M Index M Master audit trail, TMF 4-16 Master service processors (MSPs) definition of 7-6 MAT See Master audit trail Measure 6-2 Measuring outages 1-6, 1-7 Memory, adding 3-4 MODIFY DICTIONARY (NonStop SQL/MP) 4-14 Moving disk drives 3-5 MSPs See Master service processors (MSPs) N Networking See Communications subsystems, products NonStop NET/MASTER Management Services 5-3 NonStop ODBC See NonStop Open Database Connectivity Server NonStop Open Database Connectivity (ODBC) server 4-11 NonStop SQL/MP chang
O Index definition 4-2 management tools 7-9/7-12 manuals for 7-12 PATHCOM interface to 7-10 SPI interface to 7-10 NonStop TS/MP See NonStop Transaction Services/MP NonStop TUXEDO environment changes you can make online to 4-23 definition 4-2 dynamic reconfiguration 4-24 overview 4-22 tmadmin 4-24 tmconfig 4-24 NOREGISTER option 4-14 Notifications 7-8 NSX See Tandem Network Statistics Extended O Objects NonStop SQL/MP 7-12 PATHMON-controlled 4-6, 7-10 Subsystem Control Facility 7-1 ODBC See NonStop Open D
R Index Pathway/TS 4-27 Performance management 6-1 Performance measurement 6-2 Periodic incident reports definition of 7-9 Phantom devices 6-3 Phantom disk drives 3-5 Phantom processors 3-3 Physical outage class 1-6 Planned outage request form 2-3 Planned outages anticipating and planning for 6-1 definition of 1-6, 6-1 minimizing the frequency of 6-1 request form for 2-3 Power capacity 6-3 Problem incident reports 7-8 Problem management 1-8 Processors adding 3-3 configuring phantom 3-3 installing 3-3 upgr
T Index SCUP See SCREEN COBOL Utility Program Security management 1-8, 2-1 Server class 4-4 Server programs 4-4 Server software, TSM 7-6 Service processors (SPs) 7-7 Shutdown processes, distributing 6-6 SHUTDOWN2 command 6-7 Shutdown, system 6-6 SNA network connections 5-3 SNAX product family 5-3 Software and Services Directory 2-3, 7-1 Software components, TSM ??/7-9 SP event messages 7-8 SPI See Subsystem Programmatic Interface SQL statements 4-9, 4-10 SQLCI features of 4-9, 7-12 limitations of 7-13 Sta
U Index Third-party tools 2-3 tmadmin, NonStop TUXEDO environment 4-24 tmconfig, NonStop TUXEDO environment 4-24 TMF catalog 4-20 TMF subsystem 4-16, 7-14 See also NonStop Transaction Manager/MP TMFCOM 4-17, 7-14 TMFSERVE 4-17, 7-14 TMP 7-14 Tools Communications Management Interface 3-1 Dynamic System Configuration 3-1 Guardian Performance Analyzer 6-2 Measure 6-2 NonStop SQL/MP management 4-9, 712 NonStop Transaction Manager/MP management 7-14 NonStop Transaction Services/MP management 4-5 performance me
Special Character Index $SYSTEM disk, and SYSGENR 3-6 Availability Guide for Change Management–125506 Index- 9
Special Character Index Availability Guide for Change Management–125506 Index -10
