IBM Tivoli Key Lifecycle Manager for z/OS V1.0 manages encryption keys for storage, helping simplify deployment and maintaining availability to data at rest
IBM Europe, Middle East, and Africa Software Announcement ZP09-0022February 10, 2009
|
|
| At a glance |
The focus of IBM® Tivoli® Key Lifecycle Manager for z/OS® is to help:
- Manage your information risk by providing the capability to manage encryption keys used to secure information, help assure information integrity, implement encryption key retention policies, and ease data recovery
- Manage encryption keys for storage administrators
- Manage keys for self encrypting storage such as the DS8000
- Automate the rotation of keys for life cycle and compliance requirements
- Provide a key management facility for transparent encryption, initially supporting IBM tape drives
|
|
| Overview |
IBM Tivoli Key Lifecycle Manager for z/OS V1.0 addresses the dynamics that make key life-cycle management a vital initiative. These dynamics include:
- Supports storage management solutions - Encryption is a critical capability for storage management, and effective key life-cycle management should be a critical control point in a computing infrastructure.
- Helps reduce the cost of data loss - The costs associated with the loss of data can be significant. Clearly, investment now to develop a data security strategy can help avoid the much higher costs associated with cleaning up after a breach. To get ahead of this data breach risk, encryption and key life-cycle management should be high on customers' priority lists.
|
|
| Key prerequisites |
For details, refer to the Hardware requirements and Software requirements sections.
|
|
| Planned availability date |
March 6, 2009
See the complete letter for national language availability.
|
|
| Description |
IBM Tivoli Key Lifecycle Manager for z/OS V1.0 should help ease concerns about data loss and disclosure and the issues associated with reporting and compliance.
IBM Tivoli Key Lifecycle Manager for z/OS benefits include:
- Making the prospect of managing encryption, and the costs associated with encryption, a feasible reality in a standards-based approach to management
- Focusing on helping reduce the complexity of distributed key management from hundreds of pages of documentation into a handful of screen captures
- Helping customers manage their information risk by providing the capability
to secure information, address information integrity, implement information
retention policies, and ease data recovery through:
- Providing a platform independent, industry standards-based, and extendable key life-cycle management solution for small, medium, and large enterprise wide requirements
- Simplifying the key life-cycle management process including an intuitive interface that eases key creation, tracking, reporting, and removal
- Providing a base that can accommodate all forms of "data at rest" implementations
Accessibility by people with disabilities
A U.S. Section 508 Voluntary Product Accessibility Template (VPAT) containing details on accessibility compliance can be requested at
Value Unit-based pricing
Value Unit pricing for eligible IBM System z® IBM International Program License Agreement (IPLA) programs enables a lower cost of incremental growth and enterprise aggregation. Each System z IPLA product with Value Unit pricing has a single price per Value Unit and a conversion matrix, called Value Unit Exhibit, for converting from some designated measurement to Value Units. Most commonly, Millions of Service Units (MSUs) is the measurement designated by IBM to be converted to Value Units. Some other measurements are engines or messages. Since MSUs are the most common measurement, that measurement will be used for the remainder of this description.
Value Unit pricing offers price benefits for you. For each System z IPLA program with Value Unit pricing, the quantity of that program needed to satisfy applicable IBM terms and conditions is referred to as the required license capacity. Each of the various Value Unit Exhibits stipulate that the larger your required license capacity, the fewer Value Units per MSU you will need. Value Unit Exhibits are uniquely identified by a three digit code and referred to using the nomenclature VUExxx, where xxx is the three digit code.
Subsequent acquisitions of Value Unit priced programs offer additional price benefits. The quantity of each System z IPLA program that you have acquired is referred to as entitled license capacity. If you wish to grow your entitled license capacity for a System z IPLA program, the calculation to determine additional needed Value Units is based upon the number of Value Units already acquired.
For each System z IPLA program with Value Unit pricing, you should:
- Determine the required license capacity, in MSUs
- Aggregate the MSUs across the enterprise
- Convert the total MSUs to Value Units, using the applicable Value Unit Exhibit
- Multiply the price per Value Unit by the total number of Value Units to determine the total cost
To simplify conversion from the designated measurement to Value Units or vice-versa, use the Value Unit Converter Tool. For additional information or to obtain a copy of the Value Unit Converter Tool, visit the Value Unit Converter Tool Web site
Note that Value Units of a given product cannot be exchanged, interchanged, or aggregated with Value Units of another product.
To determine the required license capacity for the System z IPLA program you selected, refer to theTerms and conditions section.
|
|
| Product positioning |
IBM Tivoli Key Lifecycle Manager for z/OS provides encryption key serving and life-cycle management to help protect sensitive data encrypted using IBM tape drives and IBM OEM tape drives.
|
|
| Reference information |
- Software Announcement ZP08-0486, dated November 4, 2008
- Software Announcement ZG09-0158, dated February 10, 2009
|
|
| Product identification number |
Program Program Subscription and
PID number Support PID number
IBM Tivoli Key Lifecycle 5698-B35 5698-R38
Manager for z/OS V1.0
IBM Tivoli Key Lifecycle 5698-B42 5698-R33
Manager for Storage V1.0
|
|
| Program number |
Program Program number VRM name 5698-B35 1.0.0 IBM Tivoli Key Lifecycle Manager for z/OS 5698-B42 1.0.0 IBM Tivoli Key Lifecycle Manager for Storage
|
|
| Education support |
Comprehensive education for IBM Tivoli products is offered through Worldwide Tivoli Education Delivery Services. A wide range of training options are available, including classes led by instructors, learning on demand, on-site training, and blended learning solutions.
For additional information, visit
|
|
| Offering Information |
Product information is available via the Offering Information Web site
|
|
| Publications |
Displayable softcopy publications
The following English publications may be downloaded at general availability from the following Web site
English publications
- IBM Tivoli Key Lifecycle Manager Installation and Configuration Guide (SC23-9977)
- IBM Tivoli Key Lifecycle Manager Program Directory (for z/OS) (GI11-4300)
The IBM Publications Center
The Publications Center is a worldwide central repository for IBM product publications and marketing material with a catalog of 70,000 items. Extensive search facilities are provided. Payment options for orders are via credit card (in the U.S.) or customer number for 20 countries. A large number of publications are available online in various file formats, and they can all be downloaded by all countries, free of charge.
Translated copies in selected languages will be available for download within 60 days of the general availability date from the following Web site
|
|
| Technical information |
Specified operating environment
Hardware requirements
IBM Tivoli Key Lifecycle Manager for z/OS V1.0 hardware requirements
Minimum and recommended processor requirements for IBM Tivoli Key Lifecycle Manager for z/OS are:
- Processor IBM System z9® EC or z9 BC, z10 EC or BC
- For cryptographic support, a Crypto Express2 Coprocessor is required. This also requires ICSF Web deliverable, "Cryptographic Support for z/OS V1R8-V1R10 and z/OS.e V1R8". It can be downloaded from
IBM Tivoli Key Lifecycle Manager for z/OS V1.0 supports the following IBM Storage products:
Product Name Machine type Model
TS1120 Tape Drive 3592 E05
TS1130 Tape Drive 3592 E06/EU6
TS2900 Tape Autoloader 3572 S4H, S4E, S4R
3592 C20 Frame 3592 C20
TS1120 Tape Cntrl 3592 C06, J70
TS3100/3200 Tape Lib 3573 L2U, L4U
LTO-4-specific models: S42,
S44, E42, E44, F4S, S4S,
F4H, S4H
TS3310 Tape Library 3576 L5B, E9U
TS3500 Tape Library 3584 L32, L22, L23, L52, L53
3494 Tape Library 3494 L10, L12, L14, L22
TS3400 Tape Library 3577 L5U
3953 Library Mgr 3953 F05
DS8000 Storage Controller 2107 (1) 921, 922, 9A2, 931, 932, 9B2
DS8000 Storage Controller 2421 (1) 931, 932, 9B2
DS8000 Storage Controller 2422 (1) 931, 932, 9B2
DS8000 Storage Controller 2423 (1) 931, 932, 9B2
DS8000 Storage Controller 2424 (1) 931, 932, 9B2
(1) For additional information, refer to the IBM System Storage DS8000 announcements listed in the Reference information section.
Software requirements
IBM Tivoli Key Lifecycle Manager for z/OS supports the following:
- z/OS V1 Release 9, or later
- IBM System Services Runtime Environment for z/OS V1.1, with Service Update 1
- DB2® for z/OS 8.1,
or later
Note:DB2 must reside on the same z/OS system on which the IBM Tivoli Key Lifecycle Manager server runs. You must also install the DB2 JDBC driver, which is an optional FMID that comes bundled with the base DB2 package.
- Conditional operational requirement -- Cryptographic Support for z/OS V1R8-V1R10 and z/OS.e V1R8 requires a Crypto Express2 Coprocessor.
Note: On z/OS systems, SSRE and DB2 must already be installed on the system before you install IBM Tivoli Key Lifecycle Manager. Refer to the Program Directory for IBM Tivoli Key Lifecycle Manager on z/OS for information on installing SSRE and DB2.
Supported Web browsers
A supported browser is required in order to use IBM Tivoli Key Lifecycle Manager. The following table lists the browser and browser versions that are supported by IBM Tivoli Key Lifecycle Manager:
Browser Fix pack, Systems Sun Server Windows Red Hat SUSE
patch, and with no Solaris Server Enterprise Linux
maintenance supported (SPARC) 2003 Linux Enterprise
level browser AS Server
requirements
Microsoft Service No X
Internet Pack 1 browser
Explorer, is
Version supported
6.0.x on AIX
or z/OS
Microsoft None systems. X
Internet You must
Explorer, deploy a
Version remote
7.0 browser
on a
separate
computer.
For additional requirements regarding which operating system is used, refer to the IBM Tivoli Key Lifecycle Manager Installation and Configuration Guide for additional requirements depending on which operating system is used.
The program's specifications and specified operating environment information may be found in documentation accompanying the program, if available, such as a README file, or other information published by IBM, such as an announcement letter. Documentation and other program content may be supplied only in the English language.
Limitations
For additional information, refer to Usage restrictions in the Terms and conditions section of this announcement, or to the license information document that is available on the IBM Software License Agreement Web site
Planning information
Packaging
IBM Tivoli Key Lifecycle Manager for z/OS V1.0 is distributed with:
- International Program License Agreement (Z125-3301)
- License Information document (hardcopy and softcopy)
- Program Directory
- Tape
- Publications (refer to the Publications section)
This program, when downloaded from a Web site, contains the applicable IBM license agreement and License Information, if appropriate, and will be presented for acceptance at the time of installation of the program. For future reference, the license and License Information will be stored in a directory such as LICENSE.TXT.
Security, auditability, and control
IBM Tivoli Key Lifecycle Manager for z/OS V1.0 uses the security and auditability features of the operating system software. The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.
Global Technology Services
Contact your IBM representative for the list of selected services available in your country, either as standard or customized offerings for the efficient installation, implementation, or integration of this product.
IBM Tivoli Enhanced Value-basedPricing
IBM Tivoli software products are priced using IBM Tivoli Enhanced Value-basedPricing. The Enhanced Value-basedPricing system is based upon the IBM Tivoli Environment- Managed Licensing Model, which uses a managed-environment approach -- whereby price is determined by what is managed rather than the number and type of product components installed.
For example, all servers monitored with IBM Tivoli monitoring product (IBM Tivoli Monitoring) require entitlements sufficient for those servers. Other Tivoli products may manage clients, client devices, agents, network nodes, users, or other items, and are licensed and priced accordingly.
Unlike typical systems management licensing models that require entitlements of specific software components to specific systems, the IBM Tivoli Environment-Managed Licensing Model provides the customer flexibility to deploy its IBM Tivoli software products within its environment in a manner that can address and respond to the customer's evolving architecture. That is, as the architecture of a customer's environment changes, the customer's implementation of IBM Tivoli software can be altered, as needed, without affecting the customer's license requirements (as long as the customer does not exceed its entitlements to the software).
Under Enhanced Value-basedPricing, licensing and pricing of server-oriented applications are determined based upon the server's use in the customer's environment. Typically, such applications are licensed and priced in a manner that corresponds to each installed and activated processor of the server managed by the IBM Tivoli application to help correlate price to value while offering a simple solution.
Where a server is physically partitioned, this approach is modified. This partitioning technique is the approach used with systems that have either multiple cards or multiple frames, each of which can be configured independently. For servers capable of physical partitioning (for example, IBM System p® Scalable POWERparallel Systems® servers, Sun Ultra servers, and HP Superdome servers), an entitlement is required for each processor in the physical partition being managed by the Tivoli application. For example, assume that a server has 24 processors installed in aggregate. If this server is not partitioned, entitlements are required for all 24 processors. If, however, it is physically partitioned into three partitions, each containing eight processors, and Tivoli products were managing only one of the three partitions, then entitlements would be required for the eight processors on the physical partition managed by the IBM Tivoli application.
For servers with virtual or logical partitions, entitlements are required for all installed and activated processors on the server. For each IBM Tivoli application managing a clustered environment, licensing is based on the cumulative number of installed and activated processors on each server in the cluster. Where the cluster includes physically partitioned servers, the considerations described above concerning physically partitioned servers apply as well.
Enhanced Value-basedPricing recognizes the convergence of RISC and UNIX®, and Microsoft® Windows® and Intel® technologies, in order to simplify your licensing requirements, and to provide a smoother, more scalable model. Pricing and licensing does not differentiate between non-System z server platforms or operating systems. For some products, this platform neutrality extends to System z and other host servers as well.
IBM Tivoli Enhanced Value-basedPricing terminology definitions
Authorized user
An authorized user is one and only one individual (named or unnamed) within or outside your enterprise. A Proof of Entitlement (PoE) must be obtained for each individual user accessing the program in any manner. A program licensed under an authorized user PoE may be installed on a single computer or server, and accessed by multiple users, provided that a PoE has been obtained for each individual user accessing the program either directly or indirectly (via a multiplexing program, device, or application server) through any means on behalf of the user.
Note that authorized users have unique specific identity and IDs cannot be shared. An ID can establish one or more connections and count as a single authorized user. Specific information to security products are:
- An authorized user of IBM Tivoli Federated Identity Manager is any ID that accesses an application or service managed or protected by IBM Tivoli Federated Identity Manager.
- An authorized user of IBM Tivoli Directory Integrator is one whose identity can be synchronized by IBM Tivoli Directory Integrator or that can access a connected system that can be synchronized by IBM Tivoli Directory Integrator.
- An authorized user of IBM Tivoli Identity Manager is any ID whose identity is recorded in the IBM Tivoli Identity Manager identity store.
- An authorized user of IBM Tivoli Access Manager for e-business is any ID that accesses an application or service managed or protected by IBM Tivoli Access Manager for e-business.
- An authorized user of IBM Tivoli Identity and Access Manager is any ID whose identity is recorded in the IBM Tivoli Identity Manager identity store, and/or any ID that accesses an application or service managed or protected by IBM Tivoli Access Manager for e-business.
- An authorized user of IBM Tivoli Unified Single Sign-On is any ID that accesses an application or service managed or protected by IBM Tivoli Unified Single Sign-On.
- An authorized user of IBM Tivoli Access Manager for Enterprise Single Sign-On is any ID that accesses an application or service managed or protected by IBM Tivoli Access Manager for Enterprise Single Sign-On.
- Quantities of authorized users of IBM Tivoli Federated Identity Manager, Tivoli Access Manager for e-business, IBM Tivoli Access Manager for Enterprise Single Sign-On, IBM Tivoli Identity Manager, IBM Tivoli Identity and Access Manager, and IBM Tivoli Unified Single Sign-On Manager will only include users that have usable accounts. If their accounts have been made unusable, then those users do not have to count against the quantities of users that need to be licensed. Such accounts must remain unusable for a minimum of six months in order to not count against the quantities of users that need to be licensed.
Engine
An engine is also referred to as a central processor (CP) or processor. Engines for traditional workloads are called General Purpose CPs. Engines for Linux® workloads are called Integrated Facility for Linux (IFL) engines or Linux-only engines. Engines for Coupling Facility workloads are called Integrated Coupling Facility (ICF) engines.
Enterprise
An enterprise is a person or single entity and those subsidiaries with more than 50 percent ownership.
External user
An authorized user who is not part of the enterprise.
Internal user
An authorized user that is part of the enterprise.
Install
A copy or instance of the program in the Enterprise.
IBM Integrated Facility for Linux (IFL)
This optional facility enables additional processing capacity exclusively for Linux workload, with no effect on the model designation of a System z or OS/390® server. Consequently, executing Linux workload on the IBM IFL will not, in most cases, result in any increased IBM software charges for z/OS, OS/390, VM, VSE, or TPF operating systems and applications. There is, as indicated, a charge associated with the IFL, and there may also be a charge for applications which run on the IFL.
The IFL may be dedicated to a single Linux-mode logical partition or it may be shared by multiple Linux-mode logical partitions. Installations should note that the Linux workspace enabled by this facility will not support any of the traditional S/390® operating systems (OS/390, TPF, VSE, or VM). Only Linux applications or Linux operating in conjunction with the Virtual Image Facility, an environment that operates within a logical partition or in native S/390 mode and provides the capability to create multiple Linux images, are supported by IBM S/390 IFL.
Managed processor (charging under full capacity in the managed environment)
Managed processor charges are based on the active processors on the machines in the computing environment affiliated with the program rather than on the server where the program is run. The managed processors which require PoEs are defined in the License Information's program-unique terms.
Notes
- IBM defines a physical processor in a computer as a functional unit that interprets and executes instructions. A physical processor consists of at least an instruction control unit and one or more arithmetic and logic units.
- Multicore technology allows two or more processors (commonly called cores) to be active on a single silicon chip. With multicore technology, IBM considers each core to be a physical processor. For example, in a dual-core chip, there are two physical processors residing on the single silicon chip.
- The program may not run on some or all of the processors for which PoEs are required by the program's valuation method.
- In the System z IFL environment, each IFL engine is considered a single physical processor.
- Threading, a technique which makes a single processor seem to perform as two or more, does not affect the count of physical processors.
- Where blade technology is employed, each blade is considered a separate server and charging is based upon the total number of processors on the blades with which the program is affiliated.
- Not all processors require the same number of Value Unit entitlements. To determine the number of Value Unit entitlements required, refer to the processor Value Unit conversion table on the Passport Advantage® Web site
Terabytes (T/TB)
1 terabyte of managed storage = 2 to the 40th power bytes = 1,099,511,627,776 bytes.
Partitions
A server's resources (CPU, memory, I/O, interconnects, and buses) may be divided according to the needs of the applications running on the server. This partitioning can be implemented with physical boundaries (physical partitions) or logical boundaries (logical partitions).
Physical partitions are defined by a collection of processors dedicated to a workload and can be used with systems that have either multiple cards or multiple frames, each of which can be configured independently. In this method, the partitions are divided along hardware boundaries and processors, and the I/O boards, memory, and interconnects are not shared.
Logical partitions are defined by software rather than hardware and allocate a pool of processing resources to a collection of workloads. These partitions, while separated by software boundaries, share hardware components and run in one or more physical partitions.
Processor (per processor charging under full capacity)
In full capacity charging, PoEs must be acquired for all activated processors (available for use) that are on the server where the program or a component of the program is run.
Notes
- IBM defines a physical processor in a computer as a functional unit that interprets and executes instructions. A physical processor consists of at least an instruction control unit and one or more arithmetic and logic units.
- Multicore technology allows two or more processors (commonly called cores) to be active on a single silicon chip. With multicore technology, IBM considers each core to be a physical processor. For example, in a dual-core chip, there are two physical processors residing on the single silicon chip.
- In the System z IFL environment, each IFL engine is considered a single physical processor.
- Threading, a technique which makes a single processor seem to perform as two or more, does not affect the count of physical processors.
- Where blade technology is employed, each blade is considered a separate server and charging is based upon the total number of processors on the blade on which the program is run.
- When a server is shipped with six processors, but two of them are inactive, four processors are active for the customer.
- Not all processors require the same number of Value Unit entitlements. To determine the number of Value Unit entitlements required, refer to the processor value unit conversion table on the Passport Advantage Web site
Resource Value Unit (RVU)
A resource is the measurement for program license entitlements which is based upon the quantity of the specific designated measurement used for a given program. A Resource Value Unit (RVU) is a pricing charge metric of IBM Tivoli Enhanced Value-basedPricing, which uses a managed-environment approach whereby price is determined by what is managed. Whenever the designated measurement is a resource, not all resources require the same number of RVU. RVU schedules are located in the Pricing examples section.
Server
A server is a computer system that executes requested procedures, commands, or applications to one or more user or client devices over a network. A proof of entitlement (PoE) must be obtained for each server on which the program or a component of the program is run or for each server managed by the program. Where blade technology is employed, each blade is considered a separate server.
Stand-by or back-up systems
For programs running or resident on back-up machines, IBM defines three types of situations: cold, warm, and hot. In cold and warm situations, a separate entitlement for the copy on the back-up machine is normally not required and typically no additional charge applies. In a hot back-up situation, the customer needs to acquire other license or entitlements sufficient for that server. All programs running in back-up mode must be solely under the customer's control, even if running at another enterprise's location.
As a practice, the following are definitions and allowable actions concerning the copy of the program used for back-up purposes:
Cold: A copy of the program may reside, for back-up purposes, on a machine as long as the program is not started. There is no additional charge for this copy.
Warm: A copy of the program may reside for back-up purposes on a machine and is started, but is idling, and is not doing any work of any kind. There is no additional charge for this copy.
Hot: A copy of the program may reside for back-up purposes on a machine, is started, and is doing work. The customer must acquire a license or entitlements for this copy and there will generally be an additional charge.
Doing work includes, for example, production, development, program maintenance, and testing. It also could include other activities such as mirroring of transactions, updating of files, synchronization of programs, data or other resources (for example, active linking with another machine, program, database or other resource, and so on), or any activity or configurations that would allow an active hot switch or other synchronized switch over between programs, databases, or other resources to occur.
In the case of a program or system configuration that is designed to support a high availability environment by using various techniques (for example, duplexing, mirroring of files, or transactions, maintaining a heartbeat, active linking with another machine, program, database, or other resource), the program is considered to be doing work in the hot situation and a license or entitlement must be purchased.
Tivoli Management Points
A Tivoli Management Point is a metric used to compute license quantities and is program-specific.
Value Units
A Value Unit is a pricing charge metric for program license entitlements, which is based upon the quantity of a specific designated measurement used for a given program. Each program has a designated measurement. The most commonly used designated measurements are processor cores and MSUs. However, for select programs, there are other designated measurements such as servers, users, client devices, resources, and messages. The number of Value Unit entitlements required for your specific implementation of the given program must be obtained from a conversion table associated with the program. You must obtain a PoE for the appropriate number of Value Unit entitlements for your implementation. The Value Unit entitlements of a given program cannot be exchanged, interchanged, or aggregated with Value Unit entitlements of another program. Whenever the designated measurement is a processor core, not all processors require the same number of Value Unit entitlements. To determine the number of Value Unit entitlements required, refer to the processor value unit conversion table on the Passport Advantage Web site
User Value Units
A User Value Unit is a pricing charge metric for program license entitlements which is based upon the quantity of a specific designated measurement used for a given program. See Value Units definition. Users is a descriptive of one of the Value Unit charge metrics.
Processor (Value Unit)
A processor core is a functional unit within a computing device that interprets and executes instructions. A processor core consists of at least an instruction control unit and one or more arithmetic or logic unit. With multicore technology, each core is considered a processor. Not all processor cores require the same number of Value Unit entitlements. To calculate the number of Value Unit entitlements required, refer to the value unit table on the following Web site
With full capacity licensing, a PoE must be acquired for the appropriate number of value units based on all activated processor cores available for use on the server.
Product and licensing Web sites
A complete list of IBM Tivoli products is available at
IBM Tivoli product licensing documents are available at
Pricing examples
The following examples are provided to illustrate your licensing requirements.
References to non-processor-based metrics represent the actual number of entitlements required, unless other designated measurements are referenced or unless otherwise specified.
IBM Tivoli Key Lifecycle Manager for z/OS V1.0 requires entitlement for both the base product and any incremental resources managed (terabytes of storage disk and tape drive storage) above the two that are included with each base product entitlement.
The IBM Tivoli Key Lifecycle Manager for z/OS base product uses Value Unit Exhibit 007 (VUE007) for the purpose of calculating Value Units to order (based upon MSUs).
The IBM Tivoli Key Lifecycle Manager for Storage incremental resources managed (terabytes of useable encryption capable disk storage and encryption capable tape drive storage) uses Value Unit Exhibit 027 (VUE027) for the purpose of calculating Value Units to order.
The table associated with each Value Unit Exhibit is used to apply a factor to each tier as volumes (MSUs or Terabytes) increase specific to that program to determine Value Units to order. Each row (or tier) is filled in succession, summed, and rounded up to determine Value Units to order. As volumes increase through each tier, the number of Value Units required to entitle the incremental volumes decreases. The pricing examples below for the two products show how each tier is calculated individually, and summed up to determine total Value Units to order to entitle your environment. (Note: Value Unit totals are always rounded up to the next whole number for ordering purposes.)
Pricing examples for IBM Tivoli Key Lifecycle Manager for z/OS V1.0
IBM Tivoli Key Lifecycle Manager for z/OS base product is available at no charge and includes two Value Units (terabytes of disk and/or tape drive storage), but if support is needed, you are required to purchase a Subscription and Support (S&S) entitlement, (in addition to no-charge license entitlements). (For feature numbers, refer to the Ordering information section.)
IBM Tivoli Key Lifecycle Manager for z/OS V1.0 base product uses the following Value Unit exhibit 007 (VUE007) for the purpose of calculating Value Units to order (based upon MSUs).
Value Unit exhibit 007 (VUE007) Cumulative MSU Range Value Units per MSU 1 - 3 MSUs 1.00 VU/MSU 4 - 45 MSUs .45 VU/MSU 46 - 175 MSUs .36 VU/MSU 176 - 315 MSUs .27 VU/MSU 316+ MSUs .20 VU/MSU
Transaction 1
For customers ABC with a System z9 EC machine with 185 MSUs, they would require the following license and Subscription and Support (S&S) entitlements, if support is needed.
Value Units to order are calculated as follows:
Value Unit Metric Total Value Units Value Units
(VUE007) MSUs (A) per MSU (B) required
Tier 1 (1-3 MSUs) 3 1.00 3.000
Tier 2 (4-45 MSUs) 42 .45 18.900
Tier 3 (46-175 MSUs) 130 .36 46.800
Tier 4 (176-315 MSUs) 10 .27 2.700
Tier 5 (316+ MSUs) - .20 0.000
Total MSUs 185 Total Value Units 71.400
Total Value Units to order (rounded up) 72.0
Customer ABC would need to purchase 72 Value Units of S&S entitlements for their environment to go with their license entitlements if they wish to receive support.
Entitlements are also required for the incremental IBM Tivoli Key Lifecycle Manager for Storage V1.0 resources (terabytes of usable encryption capable disk storage and encryption capable tape drive storage) managed beyond the two terabytes of storage that comes with each base install.
Note: Each base product entitlement comes with two entitled resources (terabytes of disk and/or tape drive storage). Value Unit Exhibit 027 (VUE027) is used for the purpose of calculating Value Units to order (based upon terabytes of storage tape and/or disk drive storage).
Value Unit Exhibit 027 (VUE027) is shown in the table below.
Note: Value Units are rounded up to the next whole number for the purpose of ordering.
Value Unit Exhibit 027 (VUE027)
Cumulative Usage Level Value Units per terabyte
1 - 12 Terabytes 1 VU/Terabyte
13 - 32 Terabytes 0.8455 VUs/Terabyte
33 - 64 Terabytes 0.6137 VUs/Terabyte
65 - 100 Terabytes 0.4639 VUs/Terabyte
101 - 250 Terabytes 0.3870 VUs/Terabyte
251+ Terabytes 0.3097 VUs/Terabyte
Customers ABCare setting up their z/OS storage environment for both disk and tape drives. In Phase one, they plan to manage an additional 96 terabytes of disk drive storage and 92 terabytes of tape drive storage (in addition to the two that come with the base entitlement). The total incremental terabytes are added together to get the total terabytes in the environment to entitle. The total terabytes are entered into Value Unit table VUE027 to get Value Units to order. In this case, the 96 terabytes of disk storage data and the 92 terabytes of tape storage add up to a total of 188 terabytes of encryption capable storage.
Note: The two terabytes of tape and/or disk storage included with the base entitlement on the System z9 EC machine were not part of the calculation.
Customers ABC must purchase entitlements for the 188 terabytes of storage data.
The Value Units to entitle the incremental terabytes of storage data are determined as follows:
Value Unit metric Total Value Units Value Units
(VUE027) Value Units per terabyte required
(A) (B) (A) x (B)
Tier 1 (1-12 Value Units) 12 1.0000 12.0000
Tier 2 (13-32 Value Units) 20 .8455 16.9100
Tier 3 (33-64 Value Units) 32 .6137 19.6384
Tier 4 (65-100 Value Units) 36 .4639 16.7004
Tier 5 (101-250 Value Units) 88 .3870 34.0560
Tier 6 (251+ Value Units) -- .3097 0.0000
Total terabytes 188 Total VUs 99.3048
Total Value Units to order (rounded up) 100
Customers ABC would order 100 Value Units to entitle their environment for the 188 incremental resources (terabytes of tape and disk encryption capable storage) in Phase one (incremental to the two terabytes entitled with the base product entitlement).
Transaction 2
In Phase two, customers ABC want to increase the terabytes of encryption capable storage supported by their Phase one entitlements on the System z9 EC machine (with 185 MSUs). They want to add another incremental 64 terabytes of tape storage and another 100 incremental terabytes of disk storage. The new total terabytes of data storage in customers ABC's environment would be the previous 188 terabytes from Phase one, plus Phase two's 164 teerabytes for a new terabyte total of 352 terabytes of usable encryption capable disk storage and encryption capable tape drive storage.
The new total Value Units required to entitle their environment would be calculated as follows:
Value Unit metric Total Value Units Value Units
(VUE027) Value Units per terabyte required
(A) (B)
Tier 1 (1-12 Value Units) 12 1.0000 12.0000
Tier 2 (13-32 Value Units) 20 .8455 16.9100
Tier 3 (33-64 Value Units) 32 .6137 19.6384
Tier 4 (65-100 Value Units) 36 .4639 16.7004
Tier 5 (101-250 Value Units) 150 .3870 58.0500
Tier 6 (251+ Value Units) 102 .3097 31.5894
New Total terabytes 352 New total VUs required 154.8882
Total VUs required to entitle new environment (rounded up) 155.0
Previous/existing VU entitlements from first Transaction (100.0)
Total Incremental Value Units to order 55.0
Customers ABC would need to order an additional 55 Value Units to entitle their new total of 352 terabytes of encryption capable storage. No additional IBM Tivoli Key Lifecycle Manager for z/OS base purchases were required as Customer ABC originally set up their environment to handle the incremental terabytes in Phase one when they entitled their environment on the System z9 EC machine with 185 MSUs.
Note: Customers are required to purchase a Subscription and Support (S&S) entitlement, (in addition to the license entitlements), if support is needed. (For feature numbers, refer to the Ordering information section.)
|
|
| Ordering information |
Consult your IBM representative.
The z/OS programs in this announcement all have Value Unit-based pricing.
Program
number Program name Value Unit exhibit
5698-B35 IBM Tivoli Key VUE007
Lifecycle Manager
for z/OS
For each System z IPLA program with Value Unit pricing, the quantity of that program needed to satisfy applicable IBM terms and conditions is referred to as the required license capacity. Your required license capacity is based upon the following factors:
- The System z IPLA program you select
- The applicable Value Unit Exhibit
- The applicable terms
- Whether your current mainframes are full capacity or sub-capacity
Value Unit exhibit VUE007
MSUs MSUs
minimum maximum Value Units/MSU
Base 1 3 1.00
Tier A 4 45 0.45
Tier B 46 175 0.36
Tier C 176 315 0.27
Tier D 316 + 0.20
Value Units for mainframes without MSU ratings
Hardware Value Units/machine MP3000 H30 6 MP3000 H50 8 MP3000 H70 12 ESL models 2
Ordering example
The total number of Value Units is calculated according to the following example.
If your required license capacity is 1,500 MSUs for your selected System z IPLA product, the applicable Value Units would be:
Translation from MSUs to Value Units
MSUs * Value Units/MSU = Value Units
Base 3 * 1.00 = 3.00
Tier A 42 * .45 = 18.90
Tier B 130 * .36 = 46.80
Tier C 140 * .27 = 37.80
Tier D 1,185 * .20 = 237.00
Total 1,500 343.50
When calculating the total number of Value Units, the sum is to be rounded up to the next integer.
Value Unit exhibit VUE027
Cumulative usage Level Value Units per TB
1 - 12 TB 1.0 VU/TB
13 - 32 TB 0.8455 VUs/TB
33 - 64 TB 0.6137 VUs/TB
65 - 100 TB 0.4639 VUs/TB
101 - 250 TB 0.3870 VUs/TB
251+ TB 0.3097 VUs/TB
Ordering example
If your required license capacity for terabytes of usable encryption capable disk storage and/or encryption capable tape drive storage is 352 terabytes, the applicable Value Units to order would be:
Value Unit exhibit VUE027
Value Unit Metric Total Value Units Value Units
terabytes per terabyte required
(A) (B)
Tier 1 (1-12 Value Units) 12 1.0000 12.0000
Tier 2 (13-32 Value Units) 20 .8455 16.9100
Tier 3 (33-64 Value Units) 32 .6137 19.6384
Tier 4 (65-100 Value Units) 36 .4639 16.7004
Tier 5 (101-250 Value Units) 150 .3870 58.0500
Tier 6 (251+ Value Units) 102 .3097 31.5894
New Total terabytes 352 Total VUs required 154.8882
Total VUs to order (rounded up) 155.0
Note: For both VUE007 and VUE027, each row (or tier) is filled in succession, summed, and rounded up to determine Value Units to order.
Ordering z/OS through the Internet
ShopzSeries provides an easy way to plan and order your z/OS ServerPac or CBPDO. It will analyze your current installation, determine the correct product migration, and present your new configuration based on z/OS. Additional products can also be added to your order (including determination of whether all product requisites are satisfied). ShopzSeries is available in the U.S. and several countries in Europe. In countries where ShopzSeries is not available yet, contact your IBM representative (or IBM Business Partner) to handle your order via the traditional IBM ordering process. For more details and availability, visit the ShopzSeries Web site at
Single version charging
To elect single version charging, you must notify and identify to IBM the prior program and replacement program, and the machine the programs are operating on.
Current licensees
New licensees
Orders for new licenses will be accepted now.
Shipment will begin on the planned availability date.
Basic license
The programs in this announcement have Value Unit-based pricing.
Ordering information for the MSU-based z/OS product
To order, specify the program product number and the appropriate license or charge option. Also, specify the desired distribution medium. To suppress shipment of media, select the license-only option in CFSW.
Program name: IBM Tivoli Key Lifecycle Manager for z/OS V1.0
Program PID: 5698-B35
Entitlement
identifier Description License option/Pricing metric
S015887 Tivoli Key Lifecycle Mgr Basic OTC, per Value Unit
for z/OS V1.0
Orderable Distribution
supply ID Language medium
S015889 Multilingual 3480 Tape
Program name: IBM Tivoli Key Lifecycle Manager for Storage V1.0
Program PID: 5698-B42
Entitlement
identifier Description License option/Pricing metric
S015H4V Tivoli Key Lifecycle Mgr Basic OTC, per Value Unit
for Storage V1.0
Orderable Distribution
supply ID Language medium
S015H4X Multilingual 3480 Tape
Subscription and Support PID: 5698-R38
Entitlement
identifier Description License option/Pricing metric
S01588D Tivoli Key Lifecycle Mgr Basic ASC, per Value Unit
for z/OS S&S No charge, decline SW S&S
Orderable Distribution
supply ID Language medium
S01588C Multilingual Hardcopy publication
Subscription and Support PID: 5698-R33
Entitlement
identifier Description License option/Pricing metric
S015H4M Tivoli Key Lifecycle Mgr Basic ASC, per Value Unit
for Storage S&S v1.1.0 No charge, decline SW S&S
Orderable Distribution
supply ID Language medium
S015H50 Multilingual Hardcopy publication
Subscription and Support
Subscription and Support must be ordered to receive voice technical support via telephone during normal business hours, and future releases and versions, at no additional charge. The capacity of Subscription and Support (for example, Value Units or number of processors) must be the same as the capacity ordered for the product licenses.
To order, specify the Subscription and Support program product number and the appropriate license or charge option.
IBM is also providing Subscription and Support for these products, via a separately purchased offering, under the terms of the IBM International Agreement for Acquisition of Support Maintenance (IAASM). This offering:
- Includes and extends the support services provided in the base support to include technical support via telephone during normal business hours.
- Entitles customers to future releases and versions, at no additional charge. Note that the customer is not entitled to new products.
When Subscription and Support is ordered, the charges will automatically renew annually unless cancelled by the customer.
Basic machine-readable material
The distribution media feature in the following table applies to program numbers (list product program number and software maintenance program numbers). To order, select the distribution medium feature for the desired program number.
Feature Distribution
Language number medium
Multilingual 5802 Tape
Delivery services - Custom QuickShip Program
This product is eligible for the IBM Custom QuickShip Program.
Custom QuickShip combines flexible configurations with fast delivery. Customers and Business Partners are able to create product configuration of their choice by using a combination or standalone selection of hardware, software, and a menu of additional features, including the option for software preload. The inclusion of feature number 1748 will ensure Custom QuickShip delivery of the complete product configuration or standalone order. For the availability date of this product, and to find the list of countries where it applies, refer to
The committed response time under Custom QuickShip is six business days from order acceptance by IBM to customer delivery.
Future expansion or updates of eligible Custom QuickShip software products will be advertised at the European QuickShip Web site mentioned above.
Customized Offerings
Product deliverables are shipped only via Customized Offerings (for example, CBPDO, ServerPac, SystemPac®).
CBPDO and ServerPac are offered for Internet delivery, where ShopzSeries product ordering is available. Internet delivery of ServerPac may help improve automation and software delivery time. For more details on Internet delivery, refer to the ShopzSeries help information at
Media type for this software product is chosen during the Customized Offerings ordering process. Based on your customer environment, it is recommended that the highest possible density tape media is selected. Currently offered media types are:
- CBPDOs - 3480, 3480 Compressed, 3490E, 3590, and 3592*
- ServerPacs - 3480, 3480 Compressed, 3490E, 3590, and 3592*
- SystemPacs - 3480, 3480 Compressed, 3490E, 3590, and 3592*
*3592 is highest density media. Selecting 3592 will ship the fewest number of media.
Once a product becomes generally available, it will be included in the next ServerPac and SystemPac monthly update.
Production of software product orders will begin on the planned general availability date.
- CBPDO shipments will begin one week after general availability.
- ServerPac shipments will begin two weeks after inclusion in ServerPac.
- ServerPac shipments will begin three weeks after inclusion in ServerPac.
- SystemPac shipments will begin four weeks after inclusion in SystemPac due to additional customization, and data input verification.
|
|
| Terms and conditions |
The information provided in this announcement letter is for reference and convenience purposes only. The terms and conditions that govern any transaction with IBM are contained in the applicable contract documents such as the IBM International Program License Agreement, IBM International Passport Advantage Agreement, and the IBM Agreement for Acquisition of Software Maintenance.
Licensing
IBM International Program License Agreement including the License Information document and Proof of Entitlement (PoE) govern your use of the program. PoEs are required for all authorized use.
Agreement for Acquisition of Software Maintenance
The IBM Agreement for Acquisition of Software Maintenance (Z125-6011) applies for Software Subscription and Support (Software Maintenance) and does not require customer signatures.
These programs are licensed under the IBM Program License Agreement (IPLA) and the associated Agreement for Acquisition of Software Maintenance, which provide for support with ongoing access to releases and versions of the program. These programs have a one-time license charge for use of the program and an annual renewable charge for the enhanced support that includes telephone assistance (voice support for defects during normal business hours), as well as access to updates, releases, and versions of the program as long as support is in effect.
IBM System z Operational Support Services - SoftwareXcel is an option if you desire added services.
License information form number
L-LMOZ-7GZM3T IBM Tivoli Key Lifecycle Manager for z/OS V1.0 (5698-B35) and IBM Tivoli Key Lifecycle Manager for Storage V1.0 (5698-B42)
The program's license information will be available for review on the IBM Software License Agreement Web site
Limited warranty applies
Yes
Limited warranty
IBM warrants that when the program is used in the specified operating environment, it will conform to its specifications. The warranty applies only to the unmodified portion of the program. IBM does not warrant uninterrupted or error-free operation of the program or that IBM will correct all program defects. You are responsible for the results obtained from the use of the program.
IBM provides you with access to IBM databases containing information on known program defects, defect corrections, restrictions, and bypasses at no additional charge. For further information, consult theIBM Software Support Handbook found at
IBM will maintain this information for at least one year after the original licensee acquires the program (warranty period).
Program support
Enhanced support, called Subscription and Support, includes telephone assistance, as well as access to updates, releases, and versions of the program as long as support is in effect. You will be notified of discontinuance of support with 12 months' notice.
Money-back guarantee
If for any reason you are dissatisfied with the program and you are the original licensee, you may obtain a refund of the amount you paid for it, if within 30 days of your invoice date you return the program and its PoE to the party from whom you obtained it. If you downloaded the program, you may contact the party from whom you acquired it for instructions on how to obtain the refund.
For clarification, note that for programs acquired under any of IBM's On/Off Capacity on Demand (On/Off CoD) software offerings, this term does not apply since these offerings apply to programs already acquired and in use by you.
Authorization for use on home/Portable computer
You may not copy and use this program on another computer without paying additional license fees.
Volume orders (IVO)
No
Passport Advantage applies
No
Usage restriction
Yes. Usage is limited to the quantity of Value Units licensed.
For additional information, refer to the License Information document that is available on the IBM Software License Agreement Web site
Software Subscription and Support (Software Maintenance) applies
No. For operating system software, the revised IBM Operational Support Services - SoftwareXcel offering will provide support for those operating systems and associated products that are not available with the Software Subscription and Support (Software Maintenance) offering.
This will ensure total support coverage for your enterprise needs, including IBM and selected non-IBM products. For complete lists of products supported under both the current and revised offering, visit
System i Software Maintenance applies
No
Variable charges apply
Yes
Educational allowance available
Yes. When ordering through the program number process, a 15% education allowance applies to qualified education institution customers.
Education Software Allowance Program applies when ordering through the program number process.
ESAP available
Yes, to qualified customers.
Sub-capacity terms and conditions
For each System z IPLA program with Value Unit pricing, the quantity of that program needed to satisfy applicable IBM terms and conditions is referred to as the required license capacity. Your required license capacity is based upon the following factors:
- The System z IPLA program you select
- The applicable Value Unit Exhibit
- The applicable terms
- Whether your current mainframes are full capacity or sub-capacity
For more information on the Value Unit Exhibit for the System z IPLA program you selected, refer to theOrdering information section.
Program Parent,
number Program name Terms if applicable
5698-B35 IBM Tivoli Key z/OS-based NA
Lifecycle Manager
Full-capacity mainframes
In cases where full capacity is applicable, the following terms apply.
Execution-based, z/OS-based, full-machine-based: The required capacity of a System z IPLA program with these terms equals the MSU-rated capacity of the machines where the System z IPLA program executes.
For more information on mainframe MSU-rated capacities, visit
Reference-based: The required license capacity of a System z IPLA program with these terms equals the license capacity of the applicable monthly license charge (MLC) program. This MLC program is called the parent program.
Sub-capacity mainframes
In cases where sub-capacity is applicable, the following terms apply.
Execution-based: The required capacity of a System z IPLA sub-capacity program with these terms equals the capacity of the LPARs where the System z IPLA program executes.
z/OS-based: The required license capacity of a System z IPLA program with these terms equals the license capacity of z/OS on the machines where the System z IPLA program executes.
Reference-based: The required license capacity of a System z IPLA program with these terms equals the license capacity of the applicable monthly license charge (MLC) program. This MLC program is called the parent program.
Full-machine-based: The required license capacity of a System z IPLA program with full machine based terms equals the MSU-rated capacity of the machines where the System z IPLA program executes.
For more information on mainframe MSU-rated capacities, refer to The IBM System z Machines Exhibit, Z125-3901, or visit the Mainframes section of the System z Exhibits Web site
For more information on sub-capacity System z IPLA terms and conditions, refer to Software Announcement ZA04-0227, dated August 10, 2004.
For additional information for products with reference-based terms, System z IPLA sub-capacity programs with reference-based terms adds value to the parent program across the environment, regardless of where in the environment the System z IPLA program executes.
An environment is defined as either a single or stand-alone machine or a qualified Parallel Sysplex®. You may have one or more different environments across the enterprise. To determine the required license capacity for each System z IPLA program with referenced-based terms, each environment should be assessed separately.
When a System z IPLA sub-capacity program with reference-based terms is used in a qualified Parallel Sysplex environment, the required license capacity of the System z IPLA program must equal with the license capacity of the parent program across the Parallel Sysplex. Qualified Parallel Sysplex refers to one:
- That meets the criteria defined in Hardware Announcement ZA98-0120, dated January 13, 1998
- Where MLC pricing is aggregated across the sysplex
Sub-capacity eligibility
To be eligible for sub-capacity charging on select System z IPLA programs, you must first implement and comply with all terms of either sub-capacity Workload License Charges (WLC) or sub-capacity Entry Workload License Charges (EWLC). To implement sub-capacity WLC or EWLC, a machine must be System z (or equivalent). On that machine:
- All instances of the OS/390 operating system must be migrated to the z/OS operating systems.
- Any licenses for the OS/390 operating system must be discontinued.
- All instances of the z/OS operating systems must be running in z/Architecture® (64-bit) mode.
For that machine, you must create and submit a Sub-Capacity Report to IBM each month. Sub-Capacity Reports must be generated using the Sub-Capacity Reporting Tool (SCRT). For additional information or to obtain a copy of SCRT, visit the System z Software Pricing Web site
You must comply with all of the terms of the WLC or EWLC offering, whichever is applicable:
- The complete terms and conditions of sub-capacity WLC are defined in the IBM Customer Agreement - Attachment for System z Workload License Charges (Z125-6516).
- The complete terms and conditions for sub-capacity EWLC are defined in the IBM Customer Agreement - Attachment for IBM System z 890 and 800 License Charges (Z125-6587).
Additionally, you must sign and comply with the terms and conditions specified in the amendment to the IPLA contract - Amendment for IBM System z9 and System z Programs Sub-Capacity Pricing (Z125-6929). Once the amendment is signed, the terms in the amendment replace any and all previous System z IPLA sub-capacity terms and conditions.
IBM Getting Started Sub-capacity Pricing for z/OS IPLA Software applies.
Sub-capacity utilization determination
Sub-capacity utilization is determined based on the utilization of an eligible operating system and machine (for example, z/OS running in z/Architecture (64 bit) mode on a System z (or equivalent) server).
|
|
| IBM Electronic Services |
IBM has transformed its delivery of hardware and software support services to help you achieve higher system availability. Electronic Services is a Web-enabled solution that offers an exclusive, no-additional-charge enhancement to the service and support available for IBM servers. These services are designed to provide the opportunity for greater system availability with faster problem resolution and preemptive monitoring. Electronic Services comprises two separate, but complementary, elements: Electronic Services news page and Electronic Services Agent.
The Electronic Services news page is a single Internet entry point that replaces the multiple entry points traditionally used to access IBM Internet services and support. The news page enables you to gain easier access to IBM resources for assistance in resolving technical problems.
The Electronic Service Agent is no-additional-charge software that resides on your server. It monitors events and transmits system inventory information to IBM on a periodic, client-defined timetable. The Electronic Service Agent automatically reports hardware problems to IBM. Early knowledge about potential problems enables IBM to deliver proactive service that may result in higher system availability and performance. In addition, information collected through the Service Agent is made available to IBM service support representatives when they help answer your questions or diagnose problems. Installation and use of IBM Electronic Service Agent for problem reporting enables IBM to provide better support and service for your IBM server.
To learn how Electronic Services can work for you, visit
|
|
| Prices |
Contact your local IBM representative for the applicable charges.
|
|
| Announcement countries |
All European, Middle Eastern, and African countries except:
- Iran
- Sudan
- Syria
Trademarks
DS8000, z9, System Storage and Electronic Service Agent are trademarks of IBM Corporation in the United States, other countries, or both.
IBM, Tivoli, z/OS, System z, System z9, DB2, System p, Scalable POWERparallel Systems, OS/390, S/390, Passport Advantage, SystemPac, Parallel Sysplex and z/Architecture are registered trademarks of IBM Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both.
Intel is a registered trademark 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.
Other company, product, and service names may be trademarks or service marks of others.
Terms of use
IBM products and services which are announced and available in your country can be ordered under the applicable standard agreements, terms, conditions, and prices in effect at the time. IBM reserves the right to modify or withdraw this announcement at any time without notice. This announcement is provided for your information only. Reference to other products in this announcement does not necessarily imply those products are announced, or intend to be announced, in your country. Additional terms of use are located at:
For the most current information regarding IBM products, consult your IBM representative or reseller, or visit the IBM worldwide contacts page