x86 - This term is used to reference the Intel
hypervisors (KVM, VMWare, Xen) on which Virtual HMC can be
installed. Note: Note: HMC V11 release for x86 is not
supported on bare metal (7042 hardware appliances). HMC V11 is also
not supported on 7063-CR1 hardware appliance.
ppc64 or ppc64le - describes the Linux code that is compiled
to run on Power-based servers or LPARS (Logical Partitions)
HMC V11 R1 M1110 Recovery Media - for 7063-CR2 Hardware only
This package represents the Recovery image that can be used to
install HMC V11 R1 M1110 on the 7063-CR2 machine type. This Recovery
image can be used to upgrade to HMC V11 R1 M1110 from a minimum
level of HMC V10 R2. You can reference the Recovery image by APAR
MB04495 and PTF MF71730.
Starting with HMC V11 R1 M1110, 7063-CR1 models are not
supported.
Before upgrading an HMC connected to an FSP-based managed
system with FW1050 to V11 R1 M1110, you must update the
system firmware to at least MH1050_058 (FW1050.20) or
higher. Otherwise, the system might end up in No Connection
state with the reason as 'Version Mismatch' after the HMC is
upgraded.
The minimum HMC level required to perform install or
upgrade to HMC V11 R1 M1110 is HMC V10 R2.
Minimum memory supported for vHMC is 16GB and disk size is
500GB.
HMC V11 R1 M1110 provides support for managing Power11,
Power10 & POWER9 processor-based systems.
Management of POWER8 and older servers is not supported by
HMC V11. Attempts to manage POWER8 and older servers will
result in a connection state of Version Mismatch and
connection_error_code "Connection not allowed
0009-0008-00000000".
HMC V11 R1 M1110 supports the following HMC models:
If two HMCs manage the same server, both HMCs must be at
the same version, release and maintenance level.
It is recommended to have all connected VIOS servers on
the latest level i.e., Virtual I/O Server (VIOS) level
3.1.4.x or 4.1.1.x. To use all the new features available in
V11 HMC ensure all Virtual I/O Servers are at level 3.1.4.0,
or 4.1.1.x later.
All running partitions (AIX, Linux, and VIOS) should be at
Reliable Scalable Cluster Technology (RSCT) version 3.2.0.0,
or later. It is recommended to have AIX 7.1 TL4 or higher
and AIX7.2 TL0 or higher; these levels contain RSCT 3.2.1.0.
If the partitions are using TLS for RMC communication, then
the RSCT version should be 3.3.2.0 which is the default
version available in AIX7.3 TL2.
Enhancements and new function
Support for Power11 processor-based systems and I/O adapters
Support for new Energy Efficient power mode
Management, virtualization, serviceability and support of
repair for the new Power11 9080-HEU, 9043-MRU, 9824-22A,
9824-42A, 9824-41B, 9824-22B, 9856- 42H and 9856-22H model
systems.
Resource groups: A resource group is a collection of
processors that can exclusively be used by the partitions that
are assigned to the resource group. Each Power11 system has a
default resource group, and you can configure other resource
groups. The processors in a resource group are not shared with
the default resource group or any other resource group. Each
resource group can have up to 64 shared processor pools.
Partition minimum affinity scores and actions supported on
Power11 systems: Support for configuring a minimum affinity
score for partitions and whether to fail partition activation
or warn on partition activation when the minimum affinity
score cannot be met.
Energy monitoring for partitions: Real-time monitoring and
reporting of energy and carbon emissions is now available at
the partition level.
Create serviceable events supported on Power11 systems:
Reduce problem resolution time with the ability to create a
service case and upload service data files from a single
interface. Note: for partition migration problems, both the
source and target systems must be managed by the same
HMC.
Supplemental documentation:
Automated platform update/upgrade: Experience seamless
platform updates with an advanced one-touch solution, designed
for both evacuation and return or in-place updates. Each
has automatic operational recovery and resiliency. Allows
system firmware, VIOS and IO adapter updates to be done in a
single flow. Includes validation of VIOSs for
update/upgrade, validation of partitions for migration, and
options to migrate partitions to a different system and bring
them back after the updates/upgrades are complete. Note:
The new update function is available only for Power11 systems,
but the target system for Live Partition Mobility (LPM) can be
a Power10 or Power9 system.
Power mode scheduling: Added the ability to schedule the
setting of power modes for systems. Note: the time zone
used for the scheduled times on the new Power mode GUI page is
UTC. This will be changed to the HMC time zone in a
future release. The time zone used for the scheduled
times in the Schedule Management GUI is already the HMC time
zone.
Support for increased maximum partition Platform KeyStore
(PKS) size of 128 KB along with the ability to decrease the
PKS size for a partition on Power11 systems.
Secure boot for IBM i partitions is supported on Power11
systems.
LLDP: The Link Layer Discovery Protocol (LLDP) agent can now
be enabled on the HMC network interfaces to broadcast HMC
network device information.
New and improved User Experience and usability enhancements
for:
Overall GUI performance
Data tables
HMC network topology
System power modes
Serviceable events, which now includes the Events Manager
for Call Home functions
Security Enhancements:
New GUI interface for certificate management functions
such as Trust store management and import certificates
need for the services such as rsyslog, powersc, etc. MFA
allow list is also enabled on this interface.
Rest API access via port 12443 is disabled. Use port 443
instead for accessing HMC Rest APIs.
Support Notes:
Access to the old GUI dashboard has been removed.
Support for FTP is not available in the GUI. There
is still support for FTP in some commands. Use of
SFTP or NFS is recommended instead of FTP.
Partitions with vTPM 1.2 cannot be created on Power11
systems and live partition mobility for partitions enabled
with vTPM 1.2 will fail if the target system is a Power11
system.
Starting with HMC V11 R1 M1110, support for some
languages and locales has been discontinued. Refer
to the National Language Support section
below for details.
Fixed a rare issue where an Enterprise BMC-based managed
system can be left on the permanent flash side after writing
new firmware during a system firmware update, which causes
the HMC to consider the update failed.
Added a console event log entry for a partition migration
operation performed via the GUI.
Enhanced partition migration GUI task log entries to
include the partition name, source managed system name, and
resource details.
Fixed an issue where HMC 1060.3 and later disabled Server
Name Indication (SNI) for call home connections.
This can cause call home to fail when used with a proxy or
firewall that requires SNI.
Fixed an issue that caused the deferred level to not be
shown for Enterprise BMC-based managed systems on the
"Firmware > View system firmware levels" panel in the
GUI.
Fixed an issue with PowerVC deployments resulting in a
timeout error. Additional messages received may
include VIOS is busy, no RMC active and ssp_cluster timeout
errors.
Fixed an issue that causes SRC E3550046 to be reported
when a user without permission to view VIOS images navigates
to the "VIOS images" panel in the GUI.
Fixed an issue that causes setting an SR-IOV adapter to
shared mode to fail with the error "HSCL3670 There was an
error accessing the management console persistent storage
area." This issue occurs only on FSP-based
managed systems that have more than 9 SR-IOV adapters
installed. After applying the fix for this issue,
profile data backups for affected systems need to be updated
manually.
Fixed a performance issue with the "Partitions" table in
the GUI.
Improved the HSCLC48E error message that is
received when there is insufficient free disk space in the
/home directory on the VIOS when upgrading the VIOS from the
HMC. Also changed the free disk space required in the
VIOS /home directory from 10 GB to 9.5 GB.
Added the "Recheck network communication between all MSPs"
option to the partition migration GUI wizard on the "Edit
configuration settings" page.
Fixed the VLAN ID displayed in the following error message
when mapped VLAN IDs are used during VM Recovery Manager
operations: "HSCLA355 The RMC command issued to partition
<partition> failed. This means that destination VIOS
partition <partition> cannot be used to provide a
bridge to the external network with VLAN ID <VLAN
ID>, which is needed by a virtual Ethernet adapter on
the partition. If a bridge to the external VLAN is not required, you
can specify the VSI override or VLAN bridge override
option to allow the management console to continue the
operation."
Fixed an issue that caused the user-specified boot mode to
be ignored during the current configuration activation of a
partition. This issue occurs only when the partition's
resource configuration state is "Not Configured" prior to
activation.
Fixed an issue that can cause SRC E355004D to be reported
when there are frequent logins via the REST API by a user
with a password that is close to expiration.
Fixed a timing issue that can cause some HMC operations to
hang after entering a Capacity on Demand code on the HMC for
a system that is also managed by NovaLink.
Fixed the updlic -o p command to purge any
firmware update files left over in the HMC /tmp/fwupdate
directory.
Fixed an issue that caused FSP Certificate Signing
Requests and Certificates exported using ASM on the HMC to
be downloaded as .pem files in HTML format instead of PEM
format.
Fixed a rare issue that can cause a partition migration
operation to appear to be successful even though it failed.
Fixed the "copy profile" operation to copy the HCN ID for
each migratable SR-IOV logical port to prevent new devices
in the OS from being created when the copied profile is
activated.
All HMC locales that end in @euro or @preeuro have been
removed. If your HMC is set to one of those locales, the
locale will be changed to the UTF-8 version of the same
locale when the HMC is upgraded to Version 11.
Security fixes
Addressed CWE-1275: Sensitive Cookie with Improper
SameSite Attribute.
Addressed CWE-1236: Improper Neutralization of Formula
Elements in a CSV File.
Addressed CWE-79: Improper Neutralization of Input During
Web Page Generation on some HMC GUI pages.
Addressed Product Documentation Pages Accessible without
Access Controls vulnerability.
Command Line Changes
The following commands have been enhanced to support
minimum affinity scores and actions for partitions: chsyscfg,
lssyscfg, and mksyscfg.
The following commands have been enhanced to support
resource groups: chhwres, lshwres, rsthwres,
mksyscfg, lslparmigr, migrlpar, lsrrstartlpar,
rrstartlpar, lsmemopt, optmem, and
lslparutil.
The chpwrmgmt and lspwrmgmt commands
have been enhanced to support the new Power11 Energy
Efficient power mode.
The mksyscfg command has been enhanced to
support copying a partition profile.
The cpviosimg and cpviosupd commands
have been enhanced to support importing from the HMC hard
disk.
NFS support has been added to the lslic and updlic
commands.
A new option has been added to the lslic command
to filter I/O adapter levels by operating system type.
A new option has been added to the chhmc command
to enable the Link Layer Discovery Protocol (LLDP) agent
on HMC network interfaces, and the lshmc command
has been enhanced to display the LLDP setting for each HMC
network interface.
The mksvcevent command has been enhanced to
support creating new serviceable events for Power11
systems.
The lshmcusr command has been enhanced to
display the number of days until a user's password
expires.
The lsprofspace command has been deprecated.
Known issues and Limitations
When setting a schedule for power mode changes for a
managed system, the time zone used for the scheduled
times on the Power mode GUI page is UTC. This will
be changed to the local HMC time zone in a future
release. The time zone used for the scheduled
times in the Schedule Management GUI is already the
local HMC time zone.
The Update system, VIOS, adapter levels task shows in
the Task log with a status of Completed but the progress
bar on the task’s GUI page may still show it is applying
updates. Refer to this document https://www.ibm.com/support/pages/node/7240073
for more information.
Several dconf related warning messages are displayed
when running the asmmenu command. Those messages
can be ignored.
When selecting a system and then Service->Create
serviceable event, you may be unable to collect the HMC
diagnostics file (pedbg). To work around this
issue, select a different problem type then select the
System problem type again.
The hscpe user is unable to collect the HMC
diagnostics file (pedbg) when creating a serviceable
event. To work around this issue, use the hscroot
user or another user with the required authority.
An HMC user with a custom resource role is unable to
launch the Create partition or Create VIOS task on the
GUI for a Power11 system.
Using the search function on the Partitions table on
the new GUI takes several seconds to update the table
when the HMC is managing many partitions.
Dates, times, and numbers on the GUI Performance
dashboard are shown in the format based on the HMC
language instead of the browser language.
For the optimal video resolution configuration for
HMCs connected to the "IBM Rack-Mounted Flat-Panel
Console Kit with Keyboard (ETF6)" see the article
- https://www.ibm.com/support/pages/node/7239295
Occasionally a Kerberos user login may fail even when
the credentials are valid. As a workaround, try logging
in again with the same credentials after a short delay
of 15 to 30 seconds.
How to Verify Downloaded HMC Drivers are Trusted and Code
Signed
This section highlights the process administrators can follow to
verify that downloaded drivers are authentic, trusted, and have
not been tampered with. HMC drivers are digitally signed to
ensure their integrity and origin. Verification ensures that the
artifacts originate from the official and trusted source and not
from an unauthorized third party.
Every driver package includes the following components:
- A digitally signed artifact (e.g., .tar.gz, .tgz)
- A respective signature file of every driver file that confirms
the authenticity of the artifact
- A public key file used to verify the driver
Administrators can use tools such as Cosign or OpenSSL to verify
the signature and validate the integrity of the driver files.
User sessions - The following best practices helps avoid
performance degradation gradually over a period of time due
to increased login sessions as well as security
vulnerabilities such as unauthorized access to the active
HMC sessions.
It is a best practice to logoff from HMC UI and then
close the browser tab instead of directly closing the tab
Set Idle session timeout for all the users and not leave
the timeout as '0' which leaves it as no timeout.
Web browser requirements
Learn about the requirements
your web browser must meet to monitor and control the HMC.
HMC web browser support for V11 R1 M1110 requires HTML 2.0,
JavaScript 1.0, Java™ Virtual Machine (JVM), and cookie
support in browsers that will connect to the HMC. Contact
your support personnel to assist you in determining if your
browser is configured with a Java Virtual Machine. The web
browser must use HTTP 1.1. If you are using a proxy server,
HTTP 1.1 must be enabled for the proxy connections.
Additionally, pop-ups must be enabled for all HMCs addressed
in the browser if running with pop-ups disabled.
The following browsers have been tested:
Google Chrome
HMC V11 R1 M1110 supports Google Chrome Version
138.0.7204.97 (Official Build) (64-bit).
Mozilla Firefox
MC V11 R1 M1110 supports Mozilla Firefox 139.0.4 (64-bit).
Safari
HMC V11 R1 M1110 supports Safari Version 18.5
(18614.2.9.1.12) .
Microsoft Edge
HMC V11 R1 M1110 supports Version 138.0.3351.55 (Official
build) (64-bit).
Clearing the Browser Cache
In Microsoft Edge
Open Microsoft Edge,
Select Menu (3 dots icon on top right corner of the
browser)
Click on Settings
On the left panel, under Settings, click on "Privacy,
search & services".
Under Clear browsing data, click on "Choose what to
clear".
Select "Cookies and other site data" and "Cached
images and files" check box
Click on “Clear now” button.
In Mozilla Firefox
1. In the top-right corner of the browser window click the menubutton
Choose History, and then Clear
Recent History.
In time range to clear, select "Everything"
In the Details section, select "Cookies"
and "Cache"
Click on "Clear now"
2. In the top-right corner of the browser window click the
menu button
Choose Options > Advanced >
Network >
In "Offline Web Content and User Data"
section click on "Clear Now"
In Google Chrome
1. In the top-right corner of the browser window, click the
Chrome menu
Choose History.
Click the button Clear browsing data.
A dialog will appear.
From the drop-down menu, select "the
beginning of time."
Check the boxes "Cookies, site, and
plug-in data" and "Cache"
Click the button Clear browsing data.
2. Open the following URL with the Chrome browser: chrome://appcache-internals/
If there is an entry related to the
target hmc, click the corresponding "Remove" link
Other web browser considerations
Session cookies need to be enabled in order for ASMI to work
when connected to HMC remotely. The ASM proxy code saves
session information and uses it.
Microsoft Edge
Open Microsoft Edge
Select Menu (3 dots icon on top right corner of the
browser).
Click on Settings > Cookies and site permissions.
Under “Cookies and data stored” click on “Manage and
delete cookies and site data”.
Turn on “Allow sites to save and read cookie data
(recommended)” to unblock cookies.
Mozilla Firefox
Click Tools > Options.
Click the Cookies Tab.
Select Allow sites to set cookies.
If you want to allow only specific sites, select
Exceptions, and add the HMC to allow access.
BMC Browser requirements
To access local console in OpenPower environment required
the following browser requirements with JRE Plugin Version 8
U144
Google Chrome Version 138.0.7204.97
Firefox Version 139.0.4
Microsoft Edge Version 138.0.3351.55
Safari Version 18.5
Installing HMC in the OpenPower Environment, 7063
Machine type
Download of the Power Hardware Management Virtual Appliance
(vHMC) install images for x86 hypervisors are available at the
Entitled Systems Support site (ESS): http://www-304.ibm.com/servers/eserver/ess/OpenServlet.wss
. You must be entitled to Product ID 5765-HMU in order to
download 5765-HMU from the ESS site.
Upgrade of 5765-VHX to 5765-HMU is supported. Check the Upgrade
Notes section above for further details.
Fixes, mandatory fixes and service packs for the vHMC are common
to the Power Hardware management console (HMC) and will be
available at IBM Fix Central.
Installation guidance for installing the vHMC into your
hypervisor is found in the IBM
Knowledge
Center. Installation procedures may vary depending on the
operating system you use and the hypervisor you use.
The splash panel information (lshmc -V output) for the vHMC will
be the same as for the vHMC recovery image that is documented in
the above description section.
A feature of the vHMC is the activation engine which allows you
to preconfigure the HMC Console by passing configuration
information to the HMC at the first boot of the HMC, when using
these images. Please look at the on-line Knowledge Center
documentation on using the Activation
Engine
feature.
Notes for the Virtual Appliance for x86 hypervisors
The supported hypervisors for x86 for BIOS firmware
are
VMWARE ESXi 7.0.2 or higher
KVM on Ubuntu 22.0 & 24.0 LTS, Red Hat RHEL8 and
RHEL9
Xen 4.10 or higher on SLES 15, Ubuntu 22.0 LTS
The supported hypervisors for x86 for secure boot EFI
firmware are
VMWARE ESXi 7.0.2 and 8.0
KVM on Ubuntu 22.0 LTS, Red Hat RHEL8 and RHEL9
The processor on the systems hosting vHMC for x86 must
have either Intel VT-x or AMD-V Hardware Virtualization
enabled.
Notices:
Download of the Power Hardware Management Virtual
Appliance (vHMC) install images for x86 hypervisors
are available at the Entitled Systems Support site
(ESS):
http://www-304.ibm.com/servers/eserver/ess/OpenServlet.wss
. Entitlement for Product ID 5765-HMU is needed to
download from the ESS site.
Fixes, mandatory fixes and service packs for this
product are common to the Power Hardware Management
Console Appliance (HMC) and will be available from
Fix Central site.
Names of the images with "UEFI" keyword are
enabled with secure boot.
Download of the Power Hardware Management Virtual Appliance
(vHMC) install images are available at the Entitled Systems
Support site (ESS): http://www-304.ibm.com/servers/eserver/ess/OpenServlet.wss
. You must be entitled to Product ID 5765-HMD in order to
download 5765-HMD from the ESS site.
Upgrade of 5765-HMB to 5765-HMD is supported. Check the Upgrade
Notes section above for further details.
Fixes, mandatory fixes and service packs for the vHMC are common
to the Power Hardware management console (HMC) and are available
at IBM Fix Central.
The splash panel information (lshmc -V output) for the vHMC will
be the same as for the HMC recovery DVD that is documented in
the above description section for the 7063 Machine type.
Installation guidance for installing the vHMC into your
hypervisor are found in the Online Knowledge Center.
Installation procedures may vary depending on the operating
system you use and the hypervisor you use.
Notes for the Virtual Appliance for PowerVM :
HMC Virtual Appliance for PowerVM can run in a partition
with POWER9 compatibility mode or later for this release.
The HMC Virtual Appliance for PowerVM does not provide
graphics adapter support for adapters assign to the
partition. Use a supported web browser to point to the HMC
for UI support.
DLPAR operations such as memory and processor moves for
HMCs running in an LPAR are supported.
Inactive partition migration and Simplified Remote Restart
operations are supported.
The virtual appliance for PowerVM requires a POWER9,
Power10, or Power11 server that is enabled for little endian
support.
You cannot manage the server that hosts the HMC virtual
appliance.
You cannot manage the server that hosts another HMC
virtual appliance which is managing the server that hosts
this HMC virtual appliance.
For example, HMC virtual appliance A is running on server A
and HMC virtual appliance B is running on server B. HMC
virtual appliance A cannot manage server B and HMC virtual
appliance B cannot manage server A at the same time. One of
the HMC virtual appliance can manage the other server, but
both HMC virtual appliance cannot manage each other at the
same time.
For HMC virtual appliances that are created on PowerVM,
enable LargeSend on the NetworkBridge of the corresponding
virtual network for better network bandwidth to the HMC
virtual appliance.
If your vHMC is running in a POWER8 server, upgrading to
V11 R1 M1110 is not supported.
Notice: Download of
the Power Hardware Management Virtual Appliance (vHMC)
install images are available at the Entitled Systems
Support site (ESS): http://www-304.ibm.com/servers/eserver/ess/OpenServlet.wss
. Entitlement for Product ID 5765-HMD is needed to
download from the ESS site. Fixes, mandatory fixes and
service packs for this product are common to the Power
Hardware Management Console Appliance (HMC) and will be
available from Fix Central site.
Virtual HMC Appliance can be deployed in your existing
POWER virtualized infrastructure. Virtual HMC Appliance
supports install into PowerVM LPARs.
Call home of serviceable events with a failing MTMS of the
HMC itself is disabled. Those serviceable events
should be manually reported to IBM software support.
To see if you are running on a virtual HMC use the lshmc
-v command. If it displays a UVMID field, then you are
running in a virtual machine.
When deploying a virtual HMC, if the mac address is not
specified, it will be generated by the hypervisor.
Network configuration on the HMC relies on the value of MAC
addresses. If you re-deploy a new virtual HMC and want to
restore critical console data previously taken on a virtual
HMC, ensure sure you are using the same MAC addresses.
When using Activation Engine to setup NTP configuration,
you must specify the NTP version value.
National Language Support (Supported languages)
Starting with HMC V11 R1 M1110, only the 10 languages in
the table below are supported. If the HMC is set to
one of the discontinued languages, it will automatically be
converted to English (UTF-8) during the upgrade.
Locales containing the ‘@’ symbol are no longer
supported. If the HMC is set to a locale with the ‘@’
symbol, it will automatically be converted to the UTF-8
variant of the same base locale during the upgrade.
This information was developed for products and services offered
in the US.
IBM may not offer the products, services, or features discussed
in this document in other countries. Consult your local IBM
representative for information on the products and services
currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply
that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does
not infringe any IBM intellectual property right may be used
instead. However, it is the user's responsibility to evaluate
and verify the operation of any non-IBM product, program, or
service.
IBM may have patents or pending patent applications covering
subject matter described in this document. The furnishing of
this document does not grant you any license to these patents.
You can send license inquiries, in writing, to:
IBM Director of Licensing IBM Corporation North Castle Drive, MD-NC119 Armonk, NY 10504-1785 US
For license inquiries regarding double-byte character set (DBCS)
information, contact the IBM Intellectual Property Department in
your country or send inquiries, in writing, to:
Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer
of express or implied warranties in certain transactions,
therefore, this statement may not apply to you.
This information could include technical inaccuracies or
typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new
editions of the publication. IBM may make improvements and/or
changes in the product(s) and/or the program(s) described in
this publication at any time without notice.
Any references in this information to non-IBM websites are
provided for convenience only and do not in any manner serve as
an endorsement of those websites. The materials at those
websites are not part of the materials for this IBM product and
use of those websites is at your own risk.
IBM may use or distribute any of the information you provide in
any way it believes appropriate without incurring any obligation
to you.
Licensees of this program who wish to have information about it
for the purpose of enabling: (i) the exchange of information
between independently created programs and other programs
(including this one) and (ii) the mutual use of the information
which has been exchanged, should contact:
IBM Director of Licensing IBM Corporation North Castle Drive, MD-NC119 Armonk, NY 10504-1785 US
Such information may be available, subject to appropriate terms
and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed
material available for it are provided by IBM under terms of the
IBM Customer Agreement, IBM International Program License
Agreement or any equivalent agreement between us.
The performance data and client examples cited are presented for
illustrative purposes only. Actual performance results may vary
depending on specific configurations and operating conditions.
Information concerning non-IBM products was obtained from the
suppliers of those products, their published announcements or
other publicly available sources. IBM has not tested those
products and cannot confirm the accuracy of performance,
compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be
addressed to the suppliers of those products.
Statements regarding IBM's future direction or intent are
subject to change or withdrawal without notice, and represent
goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are
current and are subject to change without notice. Dealer prices
may vary.
This information is for planning purposes only. The information
herein is subject to change before the products described become
available.
This information contains examples of data and reports used in
daily business operations. To illustrate them as completely as
possible, the examples include the names of individuals,
companies, brands, and products. All of these names are
fictitious and any similarity to actual people or business
enterprises is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source
language, which illustrate programming techniques on various
operating platforms. You may copy, modify, and distribute these
sample programs in any form without payment to IBM, for the
purposes of developing, using, marketing or distributing
application programs conforming to the application programming
interface for the operating platform for which the sample
programs are written. These examples have not been thoroughly
tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these
programs. The sample programs are provided "AS IS", without
warranty of any kind. IBM shall not be liable for any damages
arising out of your use of the sample programs.
Each copy or any portion of these sample programs or any
derivative work must include a copyright notice as follows:
If you are viewing this information in softcopy, the photographs
and color illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered
trademarks of International Business Machines Corp., registered
in many jurisdictions worldwide. Other product and service names
might be trademarks of IBM or other companies. A current list of
IBM trademarks is available on the web at Copyright and
trademark information at www.ibm.com/legal/copytrade.shtml.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel
Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel
SpeedStep, Itanium, and Pentium are trademarks or registered
trademarks of Intel Corporation or its subsidiaries in the
United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United
States, other countries, or both.
Microsoft is a trademarks of Microsoft Corporation in the United
States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.