This paper describes the concept, architecture, and implementation of the hardware configuration module within the support element of the IBM eServer z900. For the z900 project, this base system firmware component has been redesigned to obtain a software structure with a clear, simple, and scalable architecture that is suitable for future extensions to the z900. To achieve the desired flexibility, an object-oriented framework has been developed which supports the autosensing and configuration of hardware components as well as their status representation and management. The new configuration concept is based on a rule approach in which, for each sensed physical part in the system, a configuration rule specifies the object hierarchy to be instantiated upon it, including attributes and interconnections to other system parts. Furthermore, the concept and architecture of the framework are built upon a hardware object model (HOM) that has been designed to allow for further integration of key business logic of the z900 service subsystem and hardware support code.

The IBM zEnterprise A Unified Resource Manager support for the IBM zEnterprise BladeCenter A Extension (zBX) hardware management and operational controls was established as an extension of the z196 system. System z hardware control design principles of concurrency, security, and automatic configuration were mainstays for the extended and new support for the zBX hardware and controls. This paper describes the hardware integration approach and different aspects of management: change, problem, serviceability, configuration, operations, performance, and business. In addition, included in this paper are details of the zBX firmware, components within the zBX blades, and the automation interfaces used between the hardware management console, Support Element, and the zBX components.

No abstract

This paper describes a fully redundant clock generation and distribution approach with a fully dynamic switchover capability and concurrent repair. It highlights the challenges as the design evolved from a single source, to a ''cold '' standby backup, and finally to a fully redundant transparent switchover with no interruption of the workloads running on an IBM System z9e. The function split between hardware and the various levels of firmware is described, including the methods to determine the defect component in the clock distribution paths. Finally, we describe the joint effort with a major chip technology vendor to design and develop the necessary circuitry, according to the z9e requirements, for clock synchronization and switching.