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

 

6947ch02.fm

 

Table 2-4 LPAR mode and PU usage

 

 

 

 

 

 

 

 

LPAR mode

PU type

 

Operating systems

PUs usage

 

 

 

 

 

 

 

ESA/390

CPs

 

z/Architecture operating systems

CPs DED or CPs SHR

 

 

 

 

ESA/390 operating systems

 

 

 

 

 

Linux

 

 

 

 

 

 

 

 

 

CPs and

 

z/OS (1.6 and later)

CPs DED and zAAPs DED, or

 

 

zAAPs

 

 

CPs SHR and zAAPs SHR

 

 

 

 

 

 

 

ESA/390 TPF

CPs

 

TPF

CPs DED or CPs SHR

 

 

 

 

 

 

 

Coupling

ICFs

 

CFCC

ICFs DED or ICFs SHR, or

 

Facility

and/or

 

 

CPs DED or CPs SHR, or

 

 

CPs

 

 

ICFs DED and ICFs SHR, or

 

 

 

 

 

ICFs DED and CPs SHR

 

 

 

 

 

 

 

Linux Only

IFLs or

 

Linux

IFLs DED or IFLs SHR, or

 

 

CPs

 

z/VM

CPs DED or CPs SHR

 

 

 

 

 

 

Dynamic Add/Delete of a logical partition name

The ability to add meaningful logical partition names to the configuration without a Power-On Reset is being introduced. Prior to this support, extra logical partitions were defined by adding reserved names in the Input/Output Configuration Data Set (IOCDS), but one may not have been able to predict what might be meaningful names in advance.

Dynamic add/delete of a logical partition name allows reserved logical partition 'slots' to be created in an IOCDS in the form of extra logical channel subsystem (CSS), Multiple Image Facility (MIF) image ID pairs. A reserved partition is defined with the partition name placeholder ‘ * ’, and cannot be assigned to access or candidate list of channel paths or devices. These extra logical channel subsystem MIF image ID pairs (CSSID/MIFID) can be later assigned an logical partition name for use (or later removed) via dynamic I/O commands using the Hardware Configuration Definition (HCD). The IOCDS still must have the extra I/O slots defined in advance since many structures are built based upon these major I/O control blocks in the Hardware System Area (HSA). This support is exclusive to the z990 and z890 and is applicable to z/OS V1.6, which is planned to be available in September 2004.

When a logical partition is renamed, its name can be changed from ’NAME1’ to ‘ * ’ and then changed again from ‘ * ’ to ‘NAME2’, the logical partition number and MIFID are retained across the logical partition name change. However, the master keys in PCIXCC that were associated with the old logical partition ‘NAME1’ are retained. There is no explicit action taken against a cryptographic component for this.

Attention: Cryptographic cards are not tied to partition numbers or MIFIDs. They are set up with AP numbers and domain indices. These are assigned to a partition profile of a given name. The customer assigns these "lanes" to the partitions now and continues to have responsibility to clear them out if he changes who is using them.

2.2.7 Model configurations

The z990 server model nomenclature is based on the number of PUs available for customer use in each configuration. Four models of the z990 server are available:

￿IBM 2084 model A08 - 8 PUs are available for characterization as CPs, IFLs, ICFs, zAAPs (up to 4), or additional SAPs

Chapter 2. System structure and design 61

Page 74 Page 76
Page 75
Image 75
IBM 990 manual Model configurations, Dynamic Add/Delete of a logical partition name
Page 74 Page 76

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