Running Mainframe z on Distributed Platforms 1st Edition Kenneth Barrett

Running Mainframe z on Distributed Platforms 1st
Edition Kenneth Barrett - PDF Download (2025)
https://ebookultra.com/download/running-mainframe-z-on-
distributed-platforms-1st-edition-kenneth-barrett/
Visit ebookultra.com today to download the complete set of
ebooks or textbooks

Here are some recommended products for you. Click the link to
download, or explore more at ebookultra.com
Design and Analysis of Distributed Algorithms Wiley Series
on Parallel and Distributed Computing 1st Edition Nicola
Santoro
https://ebookultra.com/download/design-and-analysis-of-distributed-
algorithms-wiley-series-on-parallel-and-distributed-computing-1st-
edition-nicola-santoro/
Developing Mainframe Java Applications 1st Edition Lou
Marco
https://ebookultra.com/download/developing-mainframe-java-
applications-1st-edition-lou-marco/
Jog On How Running Saved My Life 1st Edition Bella Mackie
https://ebookultra.com/download/jog-on-how-running-saved-my-life-1st-
edition-bella-mackie/
Mobile Intelligence Wiley Series on Parallel and
Distributed Computing 1st Edition Laurence T. Yang
https://ebookultra.com/download/mobile-intelligence-wiley-series-on-
parallel-and-distributed-computing-1st-edition-laurence-t-yang/

Core and Metro Networks Wiley Series on Communications
Networking Distributed Systems 1st Edition Alexandros
Stavdas
https://ebookultra.com/download/core-and-metro-networks-wiley-series-
on-communications-networking-distributed-systems-1st-edition-
alexandros-stavdas/
Stroke 1st Edition Kevin M. Barrett
https://ebookultra.com/download/stroke-1st-edition-kevin-m-barrett/
Smart SOA Platforms in Cloud Computing Architectures 1st
Edition Ernesto Exposito
https://ebookultra.com/download/smart-soa-platforms-in-cloud-
computing-architectures-1st-edition-ernesto-exposito/
Running Anatomy 1st Edition Joseph Puleo
https://ebookultra.com/download/running-anatomy-1st-edition-joseph-
puleo/
Silent Running 1st Edition Mark Kermode
https://ebookultra.com/download/silent-running-1st-edition-mark-
kermode/

Running Mainframe z on Distributed Platforms 1st
Edition Kenneth Barrett Digital Instant Download
Author(s): Kenneth Barrett, Stephen Norris (auth.)
ISBN(s): 9781430264316, 1430264314
Edition: 1
File Details: PDF, 8.92 MB
Year: 2014
Language: english

Kenneth Barrett & Stephen Norris
CA Press

For your convenience Apress has placed some of the front
matter material after the index. Please use the Bookmarks
and Contents at a Glance links to access them.

iii
Contents at a Glance
About the Authors
��xv
Foreword��xvii
Acknowledgments��xix
Preface��xxi

Chapter 1: Understanding the Mainframe Environment, Technologies,
■
■
and Methodologies ��1

Chapter 2: Creating a Mainframe Virtualized Environment:
■
■
Requirements and Choices ��13
Chapter 3: Building the Hypervisor Host
■
■ ��31
Chapter 4: Creating a Base Environment
■
■
��53
Chapter 5: Constructing the z/VM Environment
■
■ ��69
Chapter 6: Establishing a DASD Repository for a Multi-Server Environment
■
■ ��95
Chapter 7: Staging for z/OS Optimization
■
■
��109
Chapter 8: Migrating to Mainframe zEnterprise DASD
■
■ ��127
Chapter 9: Customizing the z/OS Environment with Symbols
■
■ ��161
Chapter 10: Updating the Environment
■
■ ��189
Chapter 11: Preparing for Recovery
■
■ ��201
Chapter 12: Deploying Virtualized Mainframe Environments
■
■
��213
Appendix A: Software Licensing
■
■ ��231

■ Contents at a Glance
iv
Appendix B: Setting the Standards and Conventions
■
■ ��233
Appendix C: IEASYS Member Example
■
■ ��245
Appendix D: LOAD Member Example
■
■ ��249
Glossary
■
■
��251
Index��257

1
Chapter 1
Understanding the Mainframe
Environment, Technologies, and
Methodologies
This chapter provides a cursory review of the aspects of mainframe technology that are commonly practiced and
implemented on the zPDT environment. It serves to orient readers toward the in-depth information on mainframe
and distributed technologies we present in the subsequent chapters. Although we assume that most of our readers
have prior knowledge of mainframe technologies, we couch our descriptions of it so that non-mainframers and even
novices can follow along.
The IBM Mainframe Virtualization Technology
zPDT is an IBM technology whose full name is the IBM System z Personal Development Tool. IBM offers this product to
qualified and IBM-approved Independent Software Vendors (ISVs) as a development tool. For non-ISVs, IBM offers the
IBM Rational Development and Test Environment for System z, which is based on zPDT.1
The solutions developed in this book are premised on the ability of the zPDT technology to run one or more
emulated System z processors and provide emulation for many input/output device types. The zPDT has a machine
type designation of 1090 and can run on x86 processor-compatible platforms.
Note
■
■ Servers installed with the zPDT technology will be referred to in various ways throughout this book, including
server, PC-based server, distributed server, and distributed platform server. Whenever you encounter such a reference,
you may make the tacit assumption that zPDT technology is installed on the server unless specified otherwise.
1
Details of both programs are available on various IBM websites. Please refer to IBM websites or contact IBM directly to get the latest
updates and options that may fit the requirements of your company. IBM licensing and approval are required.

Chapter 1 ■ Understanding the Mainframe Environment, Technologies, and Methodologies
2
Understanding the zPDT 1090
The zPDT 1090 consists of the two following components:
• The software: Provides the processor function and emulation. It also has built-in utilities.
• The USB key (dongle): Determines the number of System z processors to be emulated on the
server and authenticates the environment. A process is performed with IBM or its partners to
certify the USB key. The USB key will provide the authentication for running the 1090 software.
Once the 1090 software is installed, a virtual System z environment is possible. Figure 1-1 is an illustration of
steps toward creating a System z environment once the server and Linux host have been configured.
Step 1
• Purchase zPDT Components (Emulator and software)
Step 2
• Download and Install IBM zPDT Emulator
• Download and Install IBM Software
Step 3
• Certify Dongle
• Insert the USB Key (Dongle)
Step 4
• Start Systems
• Develop and Test
• Access via Individual Laptop/Desktop
Figure 1-1. Steps to implement zPDT software and base systems
zPDT Capabilities
This section discusses the capabilities of the zPDT. The purpose is to convey some of the technology capabilities of
this environment that make the distributed server configuration appear more closely linked to the mainframe than
just running emulated software and hardware.
Multi-User Capability
The implicit premise of a Personal Development Tool (PDT) is that it is for a single person. When the systems are set
up in an environment with network connectivity, multiple users may sign onto the systems concurrently. While this
may seem a simple concept when dealing with mainframe environments, the concept can be lost when dealing with a
distributed environment running mainframe operating systems.

3
Cryptographic Processor
Depending on the nature of the development or usage of the mainframe environment, security may be needed to
protect data or may be required for testing of security products. A feature that is provided (but which must be set up)
is the ability to utilize a virtualized cryptographic processor.
Mainframe Look and Feel
To a developer or tester who has signed onto a system installed with zPDT technology, the server environment has the
look and feel of any mainframe system, including the following properties:
The system is multi-system capable.
•
The system is multi-user capable.
•
The environment looks the same as the mainframe.
•
The software service levels are the same as the mainframe.
•
Although a mainframe environment has far greater capabilities than a distributed server running mainframe
software, the end user performing normal functions notices no differences between the two.
Knowing the Mainframe Platform
The IBM zEnterprise System is an integrated system of mainframe and distributed technologies. The zEnterprise has
three essential components:
• System z Server: Examples include the zEC12 or z196 enterprise class server or mainframe.
• BladeCenter Extension (zBX): This infrastructure includes blade extensions for Power Blades,
Data Power Blades, and x86 Blades.
• Unified Resource Manager (zManager): All systems and hardware resources are managed from
a unified console.
Note
■
■ References in this book to the zEnterprise will be based on the System z enterprise class server only.
A System z server comprises many parts, including the following:
General purpose processors
•
Specialty processors
•
Logical partitions (LPARs)
•
LPARs can be created to run native operating systems such as z/OS, z/VM, z/VSE, and z/Linux. Figure 1-2 is a
depiction of a mainframe with many LPARs:

4
In Figure 1-2, LPARs 1, 2, and 3 are running native operating systems. Each of them serves a singular purpose.
LPAR 15, which is running z/VM, is hosting multiple virtual z/OS guests for development purposes. This allows many
different individual z/OS instances to execute differently from and independently of each other. There are other
LPARs not listed that perform various functions.
A zPDT server can create an environment similar to LPAR 15—for example, a z/VM environment with multiple
virtual z/OS guests running underneath. Several configurations can be established:
• The z/OS systems are fully independent of each other. There is no need for data sharing, but
there is a need for independence.
• The z/OS systems are connected to each other via a coupling facility. This configuration allows
the systems to share data in a Parallel Sysplex. This environment permits data sharing among
multiple systems with data integrity.
• A combination of systems sharing data and systems that are independent of each other.
Input and Output Definitions
A System z server has a configuration of devices. All of these devices must be defined to the operating system in order
to utilize them. A precise hardware configuration must be defined using IBM utilities and processes.
To support product development and testing, it is necessary to manipulate the input/output definitions. There
are many requirements for the diverse products and product-development teams. Understanding how to manipulate
and update the input/output configuration is essential. A few items that may require adding or updating include:
Devices such as
• direct access storage devices (DASDs) and terminals
Channel paths
•
Processors
•
Switches
•
System z Server LPAR View
LPAR 3
Native
z/OS
Use:
Development
LPAR 2
Native
z/Linux
Use:
Production
LPAR 1
Native
z/OS
Use:
Testing
……
……
……
LPAR 15
Use:
Development
Native
z/VM
Multiple
Virtual z/OS
Systems
Figure 1-2. LPAR view of a System z server

5
Direct Access Storage Devices
DASD volumes are used for storage. They come in different architectures and can be allocated in different sizes. Each
volume has a volume table of contents (VTOC) that contains information about each data set, including its location on
the volume.
Note
■
■ The following discussion of DASDs is based on IBM 3390.
A volume may contain many different types of data, including the following:
Operating system
•
Subsystem
•
Products
•
Temporary data
•
Program executables
•
Figure 1-3 depicts examples of DASD volumes and their associated content. The figure shows that DASD volumes
can be configured in different sizes, depending on DASD usage requirements.
DASD Volume:
VOL001
Contents:
Operating
System
DASD Volume:
VOL002
Contents:
Subsystems
DASD Volume:
VOL003
Contents:
Infrastructure
Products
DASD Volume:
VOL004
Contents:
Test Data
Size:
27 Gigabytes
Size:
18 Gigabytes
Size:
9 Gigabytes
Size:
54 Gigabytes
Figure 1-3. DASD volumes of various sizes and usages
As the requirements for larger data grow each year, enhancements are continually made to DASDs. For example,
the 3390 DASD’s limitation to 65,520 cylinders was lifted as IBM created larger 3390 volumes known as extended
address volumes (EAVs). The extra space conferred by the EAVs is called extended addressing space (EAS). Before
implementing EAVs, it is necessary to certify that the products have the capability to access the EAS for reading,
writing, and updating.

6
For product development and testing purposes, there are a number of considerations that require more DASD
than provided in the base configuration. Examples include the following:
Large work spaces
•
Large databases
•
Many volumes and sizes for certification
•
Large amounts of testing data
•
Data Sets
Data that reside on DASD are stored in a data set. Each data set on a DASD volume must have a unique name. A data
set typically contains one or more records.
There are many types of data sets and access methods. Two commonly distinguished types of data sets are
sequential and partitioned:
• Sequential data sets: The data-set records are stored one after the other.
• Partitioned data sets: These data sets have individual members and a directory that has the
location of each member, allowing it to be accessed directly.
Data sets can be permanent or temporary:
• Permanent data sets: The resident data are permanent, such as payroll.
• Temporary data sets: Such data sets are exemplified by a data set created in one step of a job
that is passed to another step for manipulation and output.
Data sets can be cataloged or uncataloged:
• Cataloged data sets: Such data sets may be referred to only by name, without specifying where
the data set is stored, because a catalog contains the data-set attributes and the location.
• Uncataloged data sets: Such data sets must be specified by both name and location.
Virtual storage access method (VSAM) applies both to data sets and to an access method for accessing and
maintaining various types of data. VSAM maintains records in a format that is not recognizable by other access
methods, such as those used for data sets in the preceding bulleted list. VSAM can define data sets in the following
ways, which differ in respect of the ways in which the respective data sets store and access records:
Keyed sequential data set (KSDS)
•
Entry sequence data set (ESDS)
•
Relative record data set (RRDS)
•
Linear data set (LDS)
•
Catalogs
A catalog keeps track of where a data set resides and its attributes. Most installations utilize both a master catalog
and one or more user catalogs. Each catalog regardless of its type can be shared and provides a seamless means for
accessing data sets across multiple systems without needing to keep track of each data set’s location.

7
Master Catalog
Every system has at least one catalog. If a system is utilizing only one catalog, then it is using the master catalog.
Using only the master catalog would be inefficient, however, as it would be maintaining information about all data
sets on the system. Figures 1-4 depicts a system with a single catalog. In this case, all data sets on the system are fully
cataloged and maintained by a single catalog.
To provide a better separation of data, user catalogs are used, as discussed in the next section.
User Catalog
In large environments, data sets are generally separated by the first part of the data-set name, known as a high-level
qualifier (HLQ). By way of a simple example, the HLQs are just the first levels of the following data-set names:
• USER1.TEST.DATA
• USER2.TEST.DATA
• USER3.JOB.CONTROL
• USER4.DATABASE.BACKUP
The HLQs USER1, USER2, USER3, and USER4 have an alias defined in the master catalog with a reference to the
user catalog. The user catalog in turn tracks the data set.
System using only the Master Catalog
Master
Catalog
All system
data sets
All user
data sets
All
production
data sets
All testing
data sets
Figure 1-4. Master catalog configuration with no user catalogs

8
The user catalogs and associated HLQs are normally further separated on a system, as in the following examples:
User Catalog 1: All user data sets
•
User Catalog 2: Production data sets for Payroll
•
User Catalog 3: Production data sets for Finance
•
The separation of data sets by functionality creates efficiency in the sense that each user catalog defines specific
data sets for specific functions. This provides ease of management and greater flexibility.
The process of linking a user catalog to a master catalog consists of the following steps:
1. The master catalog is defined as part of the system.
2. A user catalog is defined.
3. The user catalog is connected to the master catalog.
4. An alias (HLQ) is defined to the master catalog relating it to a user catalog.
5. The user catalog now tracks the data sets with the HLQ defined in step 4.
A simple view of a master catalog linked with four user catalogs is depicted in Figure 1-5.
Shared Master Catalog
In a multisystem environment where systems are connected and sharing data, you should consider sharing a master
catalog. In a large shop with many systems and master catalogs, just keeping the alias pointers and user catalogs in
sync at all times can be cumbersome. A shared master catalog eliminates duplication of effort across systems and
System Using Multiple User Catalogs
Master
Catalog
User
Catalog
Testing Data
User
Catalog
Financial
Applications
User
Catalog
Production
Applications
User
Catalog
Testing
Applications
Figure 1-5. Master catalog and user catalog relationships

9
concerns that a catalog is not in sync. Moreover, when a new application, product, or user is introduced into a shared
environment with a shared master catalog, the efforts to add the new facility or function are simpler and more flexible.
The process of linking each user catalog and each alias can be performed just once.
Learning How to Share z/OS Parameters and Symbols
To create a pristine, easy-to-update multiple system z/OS environment, first create a shared parameter library
(PARMLIB) data set to maintain all system- and subsystem-related parameters. This allows all systems to share the
same commands to start each system independently without the need to maintain multiple PARMLIB data sets and
parameters.
Part of sharing system startup parameters involves the use of symbols that are used within PARMLIB members
to differentiate the systems and other components when starting a virtual system, as discussed in Chapter 9 in
connection with techniques and methodology to facilitate an environment that is easily updated with new operating
systems versions and other software.
Mainframe Practices in a Distributed Environment
This section discusses methods for translating common mainframe practices and services into the distributed
environments.
Network-Attached Storage for Backups
To provide backup and recovery, a backup plan needs to be put into place that is easily maintained and serviceable
for providing proper support for the systems. A network-attached storage (NAS) solution suffices for this requirement.
To ensure that your backup plan provides multiple levels of recovery depending on the need, you need to perform
regular backups and incremental backups at critical points of development and system setup.
Figure 1-6 illustrates the possible backups for a single server.
• Initial backup -
• Server is ready for use
• Incremental backup -
• After products are installed
• Scheduled backup -
• All ancillary updates are now backed up
• Incremental backup -
• After new testing tools are introduced
• Scheduled backup -
• All ancillary updates are now backed up
Figure 1-6. Backup scenarios for a server

10
Backups serve the following purposes:
Recovery in the event of a hardware failure
•
Recovery in the event of software or product-related system corruption
•
Ability to restore the systems to a known environment
•
Backups on local NAS devices provide peace of mind and a methodology for restoring a server to a point in time.
Depending on the use of the systems, you may need to regularly restore a system to a point in time, as illustrated by
the following example.
Example
■
■ A group of developers is learning the proper installation and setup of a product. They require a base system
setup and two infrastructure products before beginning the training. This part of the setup is not considered part of the
training, but will be the starting point for each developer. As each person completes his or her training, a restore is
performed so that the next person begins at the same point without a need to rebuild the system environment.
Figure 1-7 shows some of the many advantages of using the NAS devices for backups.
Network-
Attached
Storage
Backups
Across
Devices
Dual
Backups
Protected
Safeguard
Scripted
Backups
Remote
Restores
Possible
Scripted
Restores
Disaster
Recovery
Figure 1-7. Network-attached storage server
Remote Network-Attached Storage
Another step to providing peace of mind and better recovery is placing NAS devices in a remote location, allowing
another layer of backup and better recoverability in the event of a localized incident, such as damage to the lab.
Figure 1-8 represents the different layers of backups:

11
Using Network File Systems as Repositories
You can gain the benefits of a network file system server for storing frequently used software—such as operating
systems, subsystems, and integration/infrastructure products—by using NAS devices. The use of the network file
system servers located in the same lab as the other servers creates a means for warehousing a lot of software in a
common place. Having the warehoused data in the same location reduces the transfer times between the repository
and the servers, in contrast to the much longer transfer time to a distant mainframe. This solution also eliminates
the need to copy all the software to the individual development servers and frees up storage on the server that can be
better utilized for product development and testing. Figure 1-9 is a conceptual representation of a repository.
Server
Local
NAS
Backup
Remote
NAS
Backup
Figure 1-8. Server backups to multiple locations
Repository
Quarterly
Service
Level
Updates
Supported
Operating
Systems
Integration
Products
Supported
Subsystems
Figure 1-9. Repository for software stored on a network file system

12
Maintaining multiple service levels for each generally available operating system and subsystem provides flexibility
for various development teams as special circumstance or needs arise, as illustrated by the following example.
Example
■
■ A product developer has been working at the most current operating system service level when a customer
reports a problem at the previous level. The developer can request the previous service level and attempt to recreate the
customer’s problem. The transfer can be performed quickly and easily.
Recognizing the Potential for Cloud Enablement
The potential for cloud enablement is tremendous, especially with respect to remote servers and mobile laptop devices.
Cloud enablement of the sharing of the repositories and NAS backups with remote distributed platform servers and
laptops allows the latter to download any software or recover their systems to a known instance (Figure 1-10).
Repository
NAS
NAS
NAS
NAS
zPDT
zPDT
zPDT
zPDT
zPDT zPDT
Figure 1-10. Cloud Enablement
Note
■
■ Readers should assume throughout the remainder of this book that all the servers utilizing the zPDT technology
are in a single lab setting, such that cloud enablement does not come into consideration unless specifically mentioned
Summary
This chapter provided insight into some common concepts of a mainframe environment and brief descriptions of
how they are implemented in a distributed platform. Chapter 2 describes the many concerns and considerations you
face in implementing a small one-system personal computer or a larger environment of servers.

13
Chapter 2
Creating a Mainframe Virtualized
Environment: Requirements
and Choices
Several factors that drive the configuration of the mainframe virtualized environment need to be taken into account
when you define the requirements for virtualized systems. The most salient requirement is the use case—the objective
that is to be achieved by utilizing the virtual systems. Once you define the use case, you can finalize the other
requirements. These include access to the systems, the number of systems, hardware specifications, and data sharing.
After the environment has been built, another important consideration is how software updates and upgrades
will be deployed. After you have made those decisions and created those processes, you need to resolve one last set of
issues concerning downtime for the environment. You must investigate and prepare for potential problems, such as
hardware errors, a prolonged environment outage, or complications that might prevent a virtual system from starting.
Configuring and deploying a virtualized environment entails a significant investment, and it is incumbent on you to
undertake a detailed recovery discussion and plan.
A thorough analysis of all these topics is essential to constructing a comprehensive and successful design.
Use Cases
The most important step in creating a virtualized mainframe environment is defining the use case. With the flexibility
and scalability that are available, numerous configurations can be implemented. It is imperative to scope how
the environment will be utilized in order to identify the most appropriate options. The project objective must be
accurately identified to ensure that the mainframe environment is correctly generated. Figure 2-1 identifies several
use cases based upon commonly defined goals.

Chapter 2 ■ Creating a Mainframe Virtualized Environment: Requirements and Choices
14
Determining the type of access required to the emulated mainframe environment is another critical step in the
creation of the lab. How many users will require access? What level of access will be needed? With the tools that are
provided by both Linux and the emulator, there are several possible methods to access the virtualized systems. One
possibility is to create a solution that is accessible by a single user using a local keyboard. This would allow for the
protection of the physical hardware in a secure location and the control of access through physical security.
Another possibility is to create network connectivity so that the hardware can be protected in a secure location,
but the users have the ability to log in remotely and physical access to the hardware is not required. Using the network
and the software tools provided, the environment can be configured for multiple users accessing the system. User
requirements and security policies must be reviewed to provide the optimal solution for both users and corporate
security. The possibilities available are shown in Figure 2-2.
Concurrency
Asynchronous Concurrent
Access
Local Access Remote Access
Number of Users
Single User Multiple Users
Figure 2-2. Variables in configuring virtual system access
Software Development
QA Testing of Newly Developed Software
System Testing of New Software Updates
Product Demonstrations
Integration Testing of New Products
Figure 2-1. Possible use cases for emulated mainframe environment system access
Once the purpose and usage of the virtualized mainframe environment have been established, the number of
systems necessary to satisfy the requirements needs to be decided.
Can a single system accomplish the specified goals?
•
Will two or more systems be necessary?
•
Is a host/guest configuration essential?
•

15
What mainframe operating systems are required?
•
How many systems will be active at the same time?
•
If only a single system is needed, then a basic configuration of a single first-level OS would suffice. However, even
if only a single system is required, there are several advantages to creating a zVM host and running the required virtual
systems as guests. If multiple mainframe systems are critical, then a VM host is highly recommended. Depending on
the performance requirements for the virtual environment specified in the use case, it is possible to start multiple
first-level systems on the Linux host, but it introduces additional complexities. Your choice of configuration will
depend on the system requirements for the specific virtual environment that you are creating (as suggested by the
examples in Figure 2-3).
Linux
z/OS
z/OS
Linux
z/VM
z/OS z/VM
Linux
z/OS
z/OS
z/OS
Figure 2-3. Possible emulated mainframe configurations. (Left) A first-level z/OS system. (Middle) Three first-level
systems, each independent of each other. (Right) A z/VM host with three z/OS guest systems
Hardware Considerations and Options
The hardware requirements of a virtualized mainframe environment must be generated based upon the use case,
access needs, and total number of systems previously defined. The main configuration options to consider are
CPU specifications, memory usage, storage demands, and network connectivity. Before creating the hardware
specifications for the physical machine, you must answer several questions:
How many CPUs are required to support the host operating system and the emulated
•
mainframe systems?
What are the memory demands of the Linux host and the virtual systems?
•
What are the hard drive space requirements of the virtualized systems?
•
What are the hard drive I/O demands of the required virtual environment?
•

16
If network connectivity is required:
•
What network transfer rates are desired?
•
Are dedicated networks required?
•
These specifications need to be identified and quantified to construct a complete configuration of the hardware.
CPU Requirements
The CPU provides the power to perform calculations, drives I/O through the memory and hard drives, and is
a determining factor in the capacity of the virtual environment that is being created. The driving factor behind
performance of the virtualized environment is the number of CPUs available for use by the virtualized systems.
Although the speed of the CPU is important, the cost of the processor is a contributing factor in the specific model
that is selected. The requirements of the virtualized environment need to be considered when determining the model
of the CPU purchased. The number of cores may be more of a factor than the actual speed of the CPU. When you
purchase your licenses from a vendor, you will select an option for the number of CPUs that can be licensed for your
emulated mainframe environment.
The recommendation for a minimum number of CPUs for the physical hardware is the number of CPUs licensed
for the virtual systems +1 for the host operating system. Practical experience has shown that better performance can
be obtained by providing a minimum configuration of the number of the CPUs licensed for the virtual systems +2.
This provides extra capacity for the host operating system to perform work for the emulator and background tasks,
without using the CPUs for the emulator and taking cycles away from the virtual systems. For example, if three CPUs
are licensed, the minimum recommended configuration would be five CPUs. This is not a valid configuration with the
current offerings from hardware vendors. With current manufacturing processes, the number of CPUs is restricted to a
multiple of two. For example, a configuration could be ordered with six processors, or eight processors, but not seven.
Given this constraint, our recommendation is to round up to six or eight CPUs. This will ensure the best performance
from the CPUs that are allocated to the virtual systems.
An example how the CPUs of an eight CPU host might be utilized is shown in Figure 2-4.
Memory Usage
In production IT systems, use of a swap or a paging file needs to be minimized. In a virtualized mainframe
environment, swapping/paging needs to be nonexistent for the virtualized systems. Any time data is swapped
or paged out, I/O is required to a nonmemory data storage device. On a production system in which performance
is critical, this can lead to degradation in responsiveness. In the virtualized environment that is being designed,
a substantial amount of paging would lead to an unresponsive system that would quickly become unusable.
CPU1 CPU2 CPU4 CPU5
CPU3 CPU7
CPU6 CPU8
Virtual System(s) Linux and Emulator
CPUs for additional functions
(system monitor, printing, etc)
Figure 2-4. Sample CPU distribution workload for 3 CP dongle and 8 processor PC

Other documents randomly have
different content

CHAPTER X
“THE THUNDERBOLT IS SWIFTER THAN THUNDER”
IWA wished to make the secret entrance to
the crater known to Kaanaana, and they
both thought it should not be disclosed to
any one else. So he accompanied her on her
return, the night after her arrival, having
first given orders that no one should follow
them under pain of death.
They found Aelani awake. “Keike,” said Hiwa, “this is your father. His
spearmen await your commands.”
Then Kaanaana kneeled before his son and kissed his feet. But
Aelani raised him from the ground and put his arms about him and
kissed him.
“My father,” he said, “I love you because my mother loves you better
than her own life, and has talked to me about you every day since I
was a little child. While the homage due the moi cannot be omitted
in public, between us three I am not a god among men, but only
your son.”
Then Kaanaana embraced Aelani, and the two ate together, Hiwa
sitting not far off, for it was contrary to the commands of Ku for men
and women to eat together. After the moi and his father had eaten
by themselves, and Hiwa had eaten by herself, Aelani slept in the
grass hut, and Hiwa and Kaanaana slept under the great koa tree,
for the moon had gone behind the mountains, and it was not safe to

attempt taking the fisherman’s boat through the passage in pitchy
darkness.
It was easy, however, in daylight, for there were three of them and a
calm sea. So they set forth early in the morning and went to Niulii.
But there were fishermen from Waipio fishing opposite the cliff who
fled home in terror, and reported that they had seen the Spirit of
Hiwa issuing from the depths of the sea, and with her the Lord of
Kohala and a young man whom they knew not, and that the three
had a boat provided by the God of the Ocean, exceeding light and
swift, in which they sped down the coast. The tale was taken
straightway to Aa, and it greatly troubled him.
Meanwhile rumors had gone forth through all of Kohala round about
Niulii, and, when Aelani arrived, wearing the royal mamo, thousands
of people had assembled to do him homage. They were cooking a
great feast for him in an umu or underground oven of hot stones—
fatted dog and pig which he had never tasted, and taro and bread-
fruit, and many kinds of lawalu fish. Also they had prepared many
kinds of delicate raw fish, flavored with kukui nuts, and crabs and
shrimps and mosses. There were also fruits and berries, both from
the lowlands and from the mountains. Neither was there any lack of
awa that all might drink and be merry.
But Aelani, as soon as he had received the homage of the people,
called a council of war, for time was precious, and the thought that
Manoa was in the power of his enemy was like a hot coal in his
breast.
It was only a dozen miles from Niulii to Waipio by water; but
Kaanaana had not war canoes wherewith to fight Aa on the sea,
neither had he canoes of any kind to carry a sufficient force of
fighting men. Therefore, an attack on the coast side would have
been madness; but the Saw-Teeth were impassable, and the trail
around them was long and difficult.

“My Lord of Kohala,” inquired Aelani, “how many spearmen can you
have at daylight to-morrow morning, with provisions to cross the
mountains?”
“Not more than eight hundred,” replied Kaanaana. “But I will have
five thousand on the fourth day.”
“Eight hundred to-morrow,” said Aelani, “are better than five
thousand on the fourth day. If Aa depends on Kaaahu, Lord of
Honokaa, he leans on a fern that will sway back and forth as the
wind blows. Yet the ahupuaa of Honokaa is the nearest of the great
lordships, and the only one from which Aa can muster many spears
before the fourth day. We should strike before any of the great
chiefs can come to his help from the south, for we are few at best,
and only a small part of the kingdom.”
Kaanaana fell upon his knees and bowed his head to the ground.
“Child of the gods,” he said, “shall I speak my manao?”
“Rise and speak!” exclaimed Aelani. “Thou art the greatest and
wisest of my nobles. Thy moi will ever listen to thy manao.”
“My manao is that the great chiefs will not hasten from the south.
They do not love Aa, and will stand aloof if they dare, or side with us
if we seem the stronger. Moreover, Aa has twelve hundred fighting
men at Waipio, and Kaaahu can bring him a thousand more before
we can get there. Our way is over steep and difficult mountains,
among sharp rocks and utter desolation, where mice would die of
hunger and thirst, and even lizards cannot live. Our spearmen,
exhausted with the journey, must fight men strong with rest and
sleep. If we start to-morrow, we shall also be greatly outnumbered,
and if we lose the battle not one of us will ever return. If we wait till
the fourth day, and only one or two chiefs come against us from the
south, we can meet Aa with equal numbers. Yet it shall be as the
moi kane says. His word is as the word of Ku.”
“Kaanaana, Lord of Kohala,” said Aelani, “I thank thee for honest
counsel, and I would also have the lesser chiefs freely speak their

manao.”
Thereupon the lesser chiefs fell upon their knees and bowed their
heads to the earth, and the foremost of them spoke for all and said:
“The way is most difficult, and eight hundred spearmen are not
many, yet what the Child of the Gods says that we will do, whether it
be life or death. His word is as the word of Ku.”
Then Hiwa spoke, as was her right in the royal councils, being equal
in birth and rank to the moi kane himself, although not in power. And
she said: “The Lord of Kohala is the wisest and greatest of the
nobles. He and the lesser chiefs have spoken well; but fear now
dwells in the heart of Aa and in the hearts of his followers. My
manao is to strike before it passeth away, that the hearts of the
chiefs in the south may also become like white wax of cocoanuts,
and that they may turn from him in the beginning.”
“As Hiwa hath said, so be it!” exclaimed Aelani. “We march to-
morrow at break of day. The thunderbolt is swifter than the thunder.”
Instantly fast runners were sent forth to summon the spearmen and
get supplies of food. Then Aelani ate and drank, and the chiefs were
merry, but Aelani’s merriment was feigned, for he greatly feared for
Manoa’s safety, and was impatient for battle because she was in the
power of his enemy.

CHAPTER XI
OVER THE MOUNTAINS
IGHT hundred and nineteen men, armed and
provisioned, were on hand at daybreak the
next morning. Aelani made a stirring speech,
telling them that Ii was dead, and that Aa
was preparing to invade Kohala to slaughter
all the men and give their wives and
kuleanas to strangers. And Kaanaana told
them of their new moi, rainbow-covered and
heaven-born.
The spearmen raised a great shout and cried: “His word is as the
word of Ku, and we will follow Kaanaana, our high-chief, where
spears are thickest, even unto death!”
Hiwa accompanied them. When Kaanaana privately remonstrated,
she replied: “Hardships and hunger and thirst are heaven with you,
my lover, and so are wounds and death; but without you, all the
world is hell to me. What mortal man can do and suffer, that surely
can I, daughter of the gods. Moreover, if the chiefs do not see me,
whom they know, they will say that Aelani, whom they do not know,
is but an impostor. My love, I must go with you.”
So she went to the war, and was ever by Kaanaana’s side, save at
meals, which their religion forbade. Although Ii was now dead,
Kaanaana did not seek to be Hiwa’s husband, for he loved her too
unselfishly to wish her to demean herself, being goddess-born, by
marriage to a mortal. And she did not propose marriage to him,

which would have been her place by custom, she being the higher of
rank, because she would not involve him in the wrath of Ku. She
counted the coming days of suffering and battle as precious—every
moment, because they were spent with him, for she knew that as
soon as they were over she must leave him and die on the altar of
Ku.
Aelani marched with elastic steps at the head of his little army. He
ate plain fish and poi like the meanest soldier, drank tepid but
precious water as sparingly, and bore the withering midday heat of
the lava-flows and the cold night winds of the mountains as if they
were the eternal June of the lowlands. So also did Hiwa and
Kaanaana, knowing that where leaders share all hardships cheerfully
their followers do not lose heart.
On the evening of the second day they had crossed the mountains,
and were within half a dozen miles of Waipio. They could not take
the enemy entirely unawares, for those fleeing before them had
carried the news. Nor were they in a condition to fight that night, for
they were utterly exhausted. Nearly fifty had dropped of fatigue by
the way, and three, falling over a precipice, had been dashed to
pieces on the rocks a thousand feet below. The little army camped in
a wood hard by and slept till morning.
Hiwa slept two hours. Then she awoke Kaanaana with a kiss and
said: “I have wakened you, my love, that you might not awake later
and miss me from your side. I am going to the enemy. Our scouts,
as you know, report the gleam of spears on the heights of
Kukuihaele. It is Kaaahu and his thousand men come to the help of
Aa. Our men are outnumbered three to one, and so worn out they
can hardly stand. Some of them are dying of fatigue, and some have
already died.”
“And you, my love,” interrupted Kaanaana, “will also die unless you
sleep this night.”

“No,” replied Hiwa, “I shall not die of fatigue, nor yet of spear-thrust
from mortal man. I shall live until our son is unquestioned moi. A
goddess gave me life, and only through a god shall it be taken from
me. My fate is unalterable. It is in the hands of Ku. Pau! My love,
you know that your spearmen, exhausted as they are, cannot fight
two thousand men. They will be slaughtered like swine in to-
morrow’s battle, and our cause will be lost unless I put fresh fear in
the hearts of the enemy.”
Kaanaana made no further objection, knowing that her words were
true, and that, unless she succeeded in her mission, they must all
die together. When she had gone, although his heart was heavy on
her account, he turned over and slept soundly that he might have
strength for the morrow’s battle. So Hiwa went forth and descended
the heights to the Waipio River, which, even at that distance from
the sea, was then deep enough for swimming. The water and the
change of motion greatly refreshed her bruised and bleeding feet
and aching limbs. She passed the hostile sentinels, swimming
noiselessly under water, and kept on down the river to the midst of
Aa’s army.
Then Aa’s spearmen, sleeping on their arms, were awakened by a
well-known voice proceeding from the water, and it said:—“Listen!
The Spirit of Hiwa bids you save your lives. Why should you die?
Behold, the rightful moi kane, Aelani, The Pledge from Heaven, The
Chosen of the Gods, cometh to his own! Ku thundered at his birth,
and the rainbow covered him; therefore none shall be able to stand
before him. Yet he is just and merciful. He will slay those who are
taken with arms in their hands, fighting against him. He will spare
those who stand aloof. But Aa shall die a pig’s death, and his bones
shall be put to shame.”
Then Hiwa swam down-stream under water so softly that not a
splash was heard or a ripple seen, and an hour past midnight the
same voice and words were heard on the heights of Kukuihaele.

At dawn Kaanaana awoke and looked upon Hiwa sleeping at his side.
She was covered with blood, and great, ragged rents were torn in
her flesh, for she had slipped and fallen while descending from the
heights of Kukuihaele in the darkness of the night. Her eyes were
sunken, her face was gaunt with toil and pain, and she slept like one
dead. Kaanaana forbade all noise in that part of the camp, and made
it silent as the grave, so that Hiwa might sleep until the men were
ready to go forth to battle. Then he awoke her gently, and she arose
and took her place beside him at the head of the warriors, armed as
a warrior, and so she marched to the fight.

CHAPTER XII
THE BATTLE
A was brave as well as cruel. He did not doubt
that Hiwa’s spirit had appeared in his camp
and on the heights of Kukuihaele; but,
although it troubled him greatly, he hoped it
was a lying spirit. Did not the whole nation
know that the moi wahine had committed the
unpardonable sin and had died from Ku’s
implacable wrath, which descends from
parent to child even unto the third and fourth generation? How,
then, could her claimant to the throne enjoy Ku’s favor? And how
could he be of the sacred race which the gods had sent from heaven
to rule men? Yet Hiwa’s spirit had thrice proclaimed him as heaven-
born, The Chosen of Ku, and living witnesses had seen him and
Hiwa and Kaanaana issue from the depths of the sea, where mortals
unaided by the gods would have perished. Superstition balanced
superstition. Men were afraid to support Aelani, and afraid to fight
against him, lest the heavy wrath of Ku should fall upon them.
It was not so with the spearmen of Kohala. Kaanaana had always
believed that Aa invented the story of Hiwa’s sin as a pretext for
hunting her to death, and what the high-chief believed was accepted
in his own domains without question. Had it not proved true? Was
she not now with them in living flesh and blood? Was not the story
of her rescue by Ukanipo, God of Sharks, reasonable and in accord
with the sacred meles that had come down from the wise men of

old? Most convincing of all, would Ku have permitted her to live if
she had committed damning sin?
Before the spearmen of Kohala arrived, Aa succeeded in persuading
most of his immediate followers, and also himself, that Hiwa was a
lying spirit. He even won over Kaaahu, Lord of Honokaa, who was
swaying between opposing opinions like a fern in the wind, and set
him and his men in the front of battle, where they could not easily
run away.
The old men, the women, and the children had collected in the
puuhonua. This was a city of refuge corresponding to those of
ancient Israel. These sanctuaries, some of them very large and with
accommodations for many people, were scattered throughout the
Hawaiian Islands. Their gates stood always open, and the
vanquished warrior, the rebel, the red-handed murderer, the violator
of tabus, the vilest criminal, or the bitterest enemy of the moi or of
the priesthood, was safe when once within their sacred walls. There
he offered thanks to the gods for his escape, and, after a few days,
was free to depart under their protection. It is said that, in the latter
part of the fifteenth century, long after the period of this story,
Hakau, The Cruel, proposed to slaughter the followers of his half-
brother, Umi, within the sanctuary, and was deterred by the
threatening vengeance of the gods—incidentally, also, by his own
death, and the complete triumph of Umi. Where did these people, so
remote and isolated, get this and so many other of the customs
described in the Jewish scriptures?
It was past noon when the conflict began—less than eight hundred
tired men attacking twenty-two hundred fresh ones. But as the
spearmen of Kohala advanced, amazement paralyzed the ranks
opposing them. The moi wahine, or her spirit, marched in front, and
beside her strode a youth, wearing the royal mamo, who was the
living image of Papaakahi, The Mighty, in his younger days, but of
more gigantic stature, and handsomer, and more regal in his
bearing, than even that great conqueror.

Kaaahu and his men, crying that the dead had come to life, and that
Aelani must be The Chosen of the Gods, broke and fled without
throwing a spear. They made their way with no great loss to the
heights of Kukuihaele, and watched the battle in safety. But, in the
confusion, Aa and his spearmen were forced back, and were hedged
in with the cliffs of Kukuihaele at their left, and the river at their
right, and the sea behind them. They could not run away, and, as
they expected no quarter, they fought with desperation. The odds,
too, seemed greatly in their favor, for they were picked warriors,
many of them nobles, and were fresh, and far outnumbered their
assailants.
But doubt and superstitious fear were with them, while the
spearmen of Kohala were confident of victory, and forgot their
weariness in the blood-frenzy of battle. Their moi kane was at their
head, and beside him the moi wahine, and Kaanaana, their high-
chief, the foremost warrior in the land. So, although they fell thick
and fast before Aa’s skilled spearmen, they pressed on and slew and
slew and slew. The moi kane and the moi wahine and the Lord of
Kohala, excelling all others in deeds of strength, and skill and valor,
were ever in advance, their spears, dripping with blood, yet they
received no hurt so that men said that Ku went before them. They
continually strove to reach Aa and kill him, for his death would end
the war; but his spearmen, knowing the rout and slaughter that
would follow, protected him with dense ranks of spears.
Then Aelani did a marvellous thing, one that was told in after ages,
which no man could have done without long and patient training. He
hurled a spear over the heads of Aa’s men, fully seventy yards, so
that it struck Aa below the waist and passed through his body. Aa
fell, and his warriors, supposing that he was dead, became panic-
stricken, and, being hemmed in by the cliffs and the sea and the
river, were slaughtered without mercy.
Just as the fighting changed into a butchery, Aelani plunged into the
river and swam across, and ran with all his speed towards Aa’s
palace. He had heard a shriek, and, looking that way, saw Manoa

rush from the palace in the direction of his army, pursued by three
men armed with spears. So he hastened to her rescue. As he drew
near to the men, they flung their spears at him at the same
moment. He evaded one of the spears, and caught the other two in
his hands as he had been taught to do in his childhood. Then he
flung the two spears back, killing two of the men with them, and the
third he killed with a stone. Thus he saved Manoa’s life.
The thing was the wickedness of Aa, for, knowing that Lilii and
Manoa were of the divine blood of Wakea and Papa in the female
line, he had commanded that they should be killed if the battle went
against him, so that the victor might have no goddess-born wife. He
had assigned the murder to the three men he trusted most, and
they killed the mother before the daughter escaped.
The slaughter ended when darkness came. A few of Aa’s men scaled
the heights of Kukuihaele; a few swam out to sea and got away; a
few score swam across the river and reached the puuhonua and
were safe, but many more were speared in attempting it. The
greater part perished. A fourth of Kaanaana’s men perished also. In
all more than a thousand men lay dead and dying on the field. The
victorious survivors, worn out with marching and slaughter, sank on
the ground beside them and slept until morning.
Hiwa and Kaanaana slept from dark till dawn; but the young moi
kane, who had that day won his kingdom, lay awake many hours,
and when sleep came to him he dreamed of love, and not of glory.

CHAPTER XIII
THE SACRIFICE
N the morning after the battle word was
brought to the palace that Aa had been
found on the field still alive. Aelani
commanded that he should be taken to the
heiau, or temple, to be sacrificed, and that
the spearmen should be assembled there to
witness the sacred rites. So Aa was taken to
the heiau, and awaited the coming of Aelani
and Hiwa and Kaanaana and the spearmen of Kohala.
Then Aelani’s servants put on him the great mamo that had been
the state robe of moi kanes of the blood of Wakea and Papa time
whereof the memory of man ran not to the contrary. It reached from
his shoulders to his ankles, and enveloped his whole body. It was
made entirely of the yellow feathers of the mamo, and, as the mamo
was a small bird, and lived in the mountains, and was wild and
scarce, from being constantly hunted, and, moreover, had but few of
the sacred feathers, the collection of feathers for that cloak had
been the life-work of nine generations of hunters. Aelani also wore a
helmet of the still more priceless feathers of the oo. The niho palaoa
was on his neck, and in his hand he carried spears red with the
blood of his enemies.
Hiwa wore a mamo like Aelani’s, broad and long, extending to her
feet, priceless as the crown jewels of England. Upon her head was a
lei, or wreath of yellow ilima and dark-green maile, and, crowning
all, a lei of the fluffy, yellow feathers of the oo, feathers worth many

times their weight in gold. Kaanaana, too, was richly clad, as
became a mighty high-chief. A cloak of yellow and red feathers, only
less rare and costly than the mamo, covered him from head to foot,
and a yellow and red helmet adorned his head.
Before they left the palace Hiwa embraced Aelani and Kaanaana,
kissing them and shedding tears, as if she were parting from them
forever, so that they greatly wondered, not dreaming of what was in
her mind. Then, when the chiefs had assembled—all who had the
right to stand in presence of the moi—Hiwa made a signal that
Kaanaana should kneel before her. So he kneeled before her, and
she, in presence of them all, took the feather lei from her head and
twined it around his helmet.
“Mighty konohiki,” she said, “thou art greatest of the chiefs, noblest
among men, my own and only love, the father of my child. Thy rank
shall be above all other men not goddess-born, and, in token
thereof, thou and the konohikis of thy line shall have the right to
deck their helmets with the yellow feathers of the oo as long as the
sun shines and water flows. I, Hiwa, daughter of the gods, have said
it, and my son, The Chosen of Ku, confirms this royal honor.”
The occasion of the sacrifice was a great one, for Aa was of the
blood of Wakea and Papa. Never before in the solemn and bloody
rites of consecrating a new moi had such an offering been made to
Ku. The heiau was an immense, irregular, stone parallelogram, open
to the sky. The interior was divided into terraces, the upper one
paved with flat stones. The south end was an inner court, the most
sacred place, corresponding to the Holiest of Holies of the Jews.
Here were the idols, great and small. Here was the high-priest’s
station. Here the gods were consulted, and their oracles made
known. At the entrance to this court was the sacrificial altar of Ku.
When Aelani and Hiwa and Kaanaana and the chiefs and warriors
had gathered in the temple, and Aa, grievously wounded, was
brought before the altar where he had long officiated as high-priest,
his proud and cruel spirit flashed forth, and he said:—“If I had won

the battle I would have gone to Kohala and put every man, woman
and child to the spear, save Aelani and Hiwa and Kaanaana and all of
noble birth, whom I would have kept for the sacrifice; I would have
made Kohala fat with slaughter; I would have drenched Ku’s altar
with the blood of the goddess-born. Then Ku would have had more
cause for rejoicing than in the sacrifice of one old man. Yet, although
my bones will be put to shame, I am content, knowing that Ku’s
heavy wrath will fall upon my enemies, and that I shall glory in their
destruction, and mock them in the other world. If Hiwa had been
slain when she committed the unpardonable sin against Ku his anger
might have been appeased; but now that it has been growing these
sixteen years, the whole people are doomed, for they are her people
and her son’s. Behold I, Aa, high-priest of Ku, proclaim that his
implacable wrath rests upon the whole kingdom, and shall eat up its
inhabitants. My revenge is sure. Therefore I rejoice, and shall return
rejoicing to the gods from whom I came!”
As the high-priest ceased speaking Kaanaana sprang towards him,
crying “Aa, you lie! You invented this damning lie as a pretext for
slaying the moi wahine! Now, in the hour of her triumph, you repeat
it to ruin her before gods and men!”
Hiwa restrained him with a gesture, and said in a loud, clear voice
that all might hear: “Aa does not lie. Sixteen years ago I forgot the
law which almighty Ku gave to Wakea and Papa—the law creating
the sacred tabu, which our nation has kept age after age, and I ate
of the fruit of which Ku has declared, ‘In the day a woman eateth
thereof she shall surely die.’”
Upon hearing this confession, the high-priest burst into a fierce,
mocking laugh, and the spearmen shrank back aghast, and
Kaanaana hung his head in shame and sorrow.
But Hiwa mounted the altar and stood above them, tall, straight and
proud, crowned with ilima and maile, clothed with the royal robe
that only a moi might wear and live, holding a spear in her hand.

“Sixteen years ago,” she said, “I committed the unpardonable sin,
and now the hour of my atonement has come. Ku spared my life.
Kneeling under the rainbow, beside my new-born babe, I confessed
my sin to him, and bound myself by an irrevocable vow that, if he
would let me train the boy to lead the chiefs in battle for his throne,
I, Hiwa, goddess-queen, with my own royal hand, would shed my
sacred blood upon his altar. Ku heard the vow, and answered me
with thunder from the mountains. He has kept faith with me. Now I
must keep faith with him, or else his heavy wrath will fall on all I
love, on all who follow me. Therefore, to save my son, Aelani, The
Pledge from Heaven, to save his father, my lover, Kaanaana, who is a
thousand times dearer to me than life, to save my people, whom I
would not have destroyed, I keep my oath and lift the curse of Ku.”
With a swift stroke she buried the spear in her own heart.
Kaanaana leaped upon the altar, crying: “Eternal Ku, although I am
not goddess-born, I am a great noble. Accept my life also in
atonement for her sin!” He stabbed himself, and, falling on Hiwa,
died kissing her dead lips.
Then Laamaikahiki, wild with grief and rage, thrust Aa through the
throat. So the high-priest died a pig’s death, and his bones were put
to shame.
Hiwa’s bones and Kaanaana’s were hidden in a cave, at dead of
night, by Aelani himself, for he would not intrust this pious duty to
meaner hands, that touch of mortal might not profane them so long
as the world should endure. Hiwa had made such atonement, lifting
Ku’s curse from all the people, that they revered her memory and
worshipped her as a goddess even as if she had not committed that
great sin.
Aloha, Hiwa! She was nobler than a goddess-queen, for she was one
of God’s noblest creatures—a noble woman. Her frailties were those
of human nature and of the remote and barbarous land in which she

lived. Her virtues were those of a brave, generous, and lovable
people.
Aloha, Hiwa! Aloha, nui!

GLOSSARY
The spelling of Hawaiian words is in the main phonetic, according to
what is known as the continental method, with the limitation that
there are only twelve letters, instead of twenty-six, in the alphabet.
Hiwa, for example, is pronounced, approximately, Hé-vä, and Aelani,
I-lä´-ny.
The following rules for pronunciation are taken from Prof. William D.
Alexander’s Brief History of the Hawaiian People:
The original Hawaiian alphabet, adopted by the first missionaries,
contained but twelve letters, five of which were vowels, and seven
consonants, viz.: a, e, i, o, u, h, k, l, m, n, p, and w. The number of
distinct sounds are about sixteen.
No distinction was formerly made between the sounds of k and t, or
between those of l and r. In poetry, however, the sound of t was
preferred to that of k. The letter w generally sounds like v between
the penult and the final syllable of a word.
A is sounded as in father, e as in they, i as in marine, o as in note, u
as in rule, or as oo in moon.
Ai, when sounded as a diphthong, resembles the English ay, and au,
the English ou in loud.
Besides the sounds mentioned above, there is in many words a
guttural break between two vowels, which is represented by an
apostrophe in a few common words, to distinguish their meaning, as
Kina’u.
Every word and every syllable must end in a vowel, and no two
consonants occur without a vowel sound between them.

The accent of about five-sixths of the words in the language is on
the penult. A few of the proper names are accented on the final
syllable, as Paki´, Kiwalao´ and Namakeha´.
Aa—the word has a variety of meanings, among which are a spiteful
person, a raging flame, a rock of rough broken lava.
Ae, keike—yes, child.
Aelani—the pledge from heaven, a promise from the skies. Lani,
heavenly, heaven-born, is a common termination of the names of
Hawaiian men and women, especially those of exalted rank.
Ahupuaa—a large tract of land under the control of a single person, a
lordship.
Aialo—those who eat at the king’s court.
Akela—a berry much like the American raspberry.
Alii-niaupio, tabu moi wahine—freely translated, goddess-queen, a
female sovereign of divine or semi-divine lineage, unapproachable,
sacred, absolute.
Aloha—Aloha, more appropriately, perhaps, than any other one
word, may be taken as typical of the Hawaiian race. It is the first
native word the stranger learns, the common salutation on the
street, and the last he hears at parting. It signifies kindly feeling,
good-will. It is also used to express love.
Aloha nui—great good-will.
Au-we—an exclamation of sorrow, a wailing cry, alas.
Awa—an intoxicating liquor made from the roots of a plant of the
same name. It is very stupefying, and, when drunk to excess, causes
the skin to turn a dirty-brown color, and to crack and flake off.
Eaeakai—the word, sometimes used as a proper noun, means,
covered with the spray of the sea.

E moe o—the customary exclamation or command to lie prostrate on
the approach of royalty.
Haleakala—the House of the Sun, an extinct volcano ten thousand
feet high on the Island of Maui. Its crater, over thirty miles in
circumference and two thousand feet deep, is the largest in the
world.
Hamakua—the name of a district in the northern part of the Island of
Hawaii.
Haole—a foreigner. The term is applied to white persons, whether of
Hawaiian or foreign birth, and is not often used in speaking of
Asiatics.
Hawaii—the large island, twice the size of all the others combined,
from which the group takes it name. It is the second in industrial
and commercial importance, and probably the first in undeveloped
resources.
Heiau—a temple.
Hilo—the name of two districts, North and South Hilo, on the
northeastern side of the Island of Hawaii and of the chief town of
the island; also of the first night in which the new moon can be
seen, as it is like a twisted thread (from the verb to twist, to spin, to
turn). The new moon, a crescent, indicates the outline of Hilo Bay.
Hiwa—the precious one.
Hula hula—a dance, dancers, dancing, and music. The Hawaiian hula
is not necessarily immodest, but certain lascivious hulas have won a
world-wide and unenviable notoriety.
Ihe—a war-club.
Ii—a word that has a variety of meanings, among which are: a
selfish person, a cruel person, a sour person, a collection of small

Welcome to our website – the ideal destination for book lovers and
knowledge seekers. With a mission to inspire endlessly, we offer a
vast collection of books, ranging from classic literary works to
specialized publications, self-development books, and children's
literature. Each book is a new journey of discovery, expanding
knowledge and enriching the soul of the reade
Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.
Let us accompany you on the journey of exploring knowledge and
personal growth!
ebookultra.com

Running Mainframe z on Distributed Platforms 1st Edition Kenneth Barrett

More Related Content

Similar to Running Mainframe z on Distributed Platforms 1st Edition Kenneth Barrett (20)

Recently uploaded (20)

Running Mainframe z on Distributed Platforms 1st Edition Kenneth Barrett