Draft Document for Review April 7, 2004 6:15 pm

6947ch08.fm

CBU deactivation

The process of deactivating CBU is simple and straightforward. The process starts by quiescing the added CPs (normally the highest numbered) from all the logical partitions, and varying them offline from the operating systems. Then from the HMC CBU activation panel, perform a concurrent CBU undo.

CBU testing

Testing of disaster/recovery plans is easy with CBU. Testing can be accomplished by ordering a diskette, calling the support center, or using the fast activation icon on the HMC.

Capacity BackUp operation example

Figure 8-10 on page 207 shows an example of a 2084-B16, software model 304 to a 2084-B16, software model 312 Capacity BackUp operation.

2084-B16

2084-B16 Model 312

Model 304

8 CBUs

+ 8 CPs

Capacity

 

Backup

Server

2084-B16 Model 312

Production

WorkloadServer Transfer

Target Model:

2084-B16 Model 312

CBU Activation

ESCD

Unplanned

Outage

Current Model:

ESCD

2084-B16

Model 304

 

 

with 8 CBU features

 

(FC 7800)

Control

Unit

Control

Unit

Control

Unit

Control

Unit

Control

Unit

Figure 8-10 Capacity BackUp operation example

The PUs associated with Capacity BackUp are reserved for future use with CBU features (FC 7800) installed on the backup server. In this example, there should be 8 CBU features installed on the backup server 2084-B16, software model 304. When the production server 2084-B16, software model 312 has an unplanned outage, the backup server can be temporarily upgraded to the target model planned, 2084-B16, software model 312, to get the capacity to take over the workload on the failed production server.

Furthermore, customers can configure systems to back each other up. For example, if a customer uses two 2084-A08, software model 303 for the production environment, both can have 3 CBU features installed (or even more). If one server has a disaster, the other one can be upgraded up to the approximately total original CP capacity.

Automatic CBU enablement for GDPS

The intent of the GDPS CBU is to enable automatic management of the reserved PUs provided by the CBU feature in the event of a server failure and/or a site failure. Upon detection of a site failure or planned disaster test, GDPS will concurrently add CPs to the

Chapter 8. Capacity upgrades 207

Page 220 Page 222
Page 221
Image 221
IBM 990 manual Capacity BackUp operation example, Automatic CBU enablement for Gdps, CBU deactivation, CBU testing
Page 220 Page 222

990 specifications

The IBM 990 series, often referred to in the context of IBM's pioneering efforts in the realm of mainframe computing, represents a unique chapter in the history of information technology. Introduced in the late 1960s, the IBM 990 series was designed as a powerful tool for enterprise-level data processing and scientific calculations, showcasing the company's commitment to advancing computing capabilities.

One of the main features of the IBM 990 was its architecture, which was built to support a wide range of applications, from business processing to complex scientific computations. The system employed a 32-bit word length, which was advanced for its time, allowing for more flexible and efficient data handling. CPUs in the IBM 990 series supported multiple instructions per cycle, which contributed significantly to the overall efficiency and processing power of the machines.

The technology behind the IBM 990 was also notable for its use of solid-state technology. This provided a shift away from vacuum tube systems that were prevalent in earlier computing systems, enhancing the reliability and longevity of the hardware. The IBM 990 series utilized core memory, which was faster and more reliable than the magnetic drum memory systems that had been standard up to that point.

Another defining characteristic of the IBM 990 was its extensibility. Organizations could configure the machine to suit their specific needs by adding memory, storage, and peripheral devices as required. This modular approach facilitated the growth of systems alongside the technological and operational demands of the business environments they served.

In terms of software, the IBM 990 series was compatible with a variety of operating systems and programming environments, including FORTRAN and COBOL, enabling users to access a broader array of applications. This versatility was a significant advantage, making the IBM 990 an appealing choice for educational institutions, research facilities, and enterprises alike.

Moreover, the IBM 990 was engineered to support multiprocessing, which allowed multiple processes to run simultaneously, further increasing its effectiveness in tackling complex computing tasks.

In summary, the IBM 990 series represents a significant advancement in computing technology during the late 20th century. With a robust architecture, versatile configuration options, and a focus on solid-state technology, the IBM 990 facilitated substantial improvements in data processing capabilities, making it a cornerstone for many businesses and academic institutions of its time. Its impact can still be seen today in the continued evolution of mainframe computing.
Top Page Image Contents