Sub-capacity pricing for select IBM zseries IBM Program License Agreement programs helps improve flexibility and price/performance

Transcription

1 Marketing Announcement August 10, 2004 Sub-capacity pricing for select IBM zseries IBM License Agreement programs helps improve flexibility and price/performance Overview IBM extends sub-capacity charging benefits to an additional set of zseries software programs governed by the International License Agreement (IPLA). IPLA programs have an one-time-charge (OTC) and an annual (optional) maintenance charge, called Subscription & Support. This announcement affects select zseries software programs in the following categories: DB2 tools IMS tools CICS tools WebSphere Tivoli Application development tools For a list of the specific zseries IPLA programs eligible for sub-capacity charging, refer to the s eligible for sub-capacity section. There are three types of sub-capacity licensing terms for eligible zseries IPLA programs: Execution-based licensing terms Reference-based licensing terms z/os -based licensing terms Under sub-capacity charging, you may: Improve alignment between software use and software charges Add hardware capacity without necessarily increasing software charges Enable greater flexibility with software licensing Achieve better price/performance for zseries IPLA programs Key Prerequisites Sub-capacity terms and conditions are available on eligible zseries IPLA programs and only on zseries machines that have implemented sub-capacity charging for IBM monthly license charge programs under either the Workload License Charges (WLC) offering or the Entry Workload License Charges (EWLC) offering. Planned availability date September 1, 2004 This announcement is provided for your information only. For additional information, contact your IBM representative. IBM Europe, Middle East, Africa IBM is a registered trademark of International Business Machines Corporation. ZA

2 The term sub-capacity generally describes a situation where an IBM customer may pay for software at less than full-machine capacity. IBM has two offerings which allow sub-capacity charging for monthly license charge programs: WLC EWLC Machines with either sub-capacity WLC or sub-capacity EWLC are eligible for sub-capacity charging on eligible zseries IPLA programs, as described in this announcement. For a description of the specific requirements to implement sub-capacity charging on eligible zseries IPLA programs, refer to the Eligibility requirements Types of zseries IPLA sub-capacity terms Each sub-capacity eligible zseries IPLA program will be licensed according to either execution-based terms, reference-based terms, or z/os-based terms, as determined by IBM. The quantity of each zseries IPLA program needed to satisfy applicable IBM terms and conditions is referred to as the required license capacity. The quantity of each zseries IPLA program that you have acquired is referred to as entitled license capacity Execution-based terms Execution-based terms apply to zseries IPLA programs whose value is based on the capacity of the execution (run-time) environment. Under these terms, the capacity of a zseries IPLA sub-capacity program must equal the capacity of the LPAR(s) where the zseries IPLA program executes. For example, the required license capacity for WebSphere Application Server for z/os must be equal to the capacity of the LPAR(s) where and when it executes. Reference-based terms Reference-based terms apply to zseries IPLA programs that add value to particular monthly license charge programs. Under these terms, the required license capacity of a zseries IPLA program must equal the license capacity of the applicable monthly license charge (MLC) program. This MLC program is called the parent program. For example, the DB2 Administration Tool for z/os adds value to the MLC program DB2 UDB for z/os. DB2 UDB for z/os is the parent program for the DB2 Administration Tool for z/os. Therefore, the required license capacity for the DB2 Administration Tool for z/os must be equal to the license capacity of DB2 UDB for z/os. zseries IPLA sub-capacity programs with reference-based terms adds value to the parent program across the environment, regardless of where in environment the zseries IPLA program executes. An environment is defined as either a single/stand-alone machine or a qualified Parallel Sysplex. Customers may have one or more different environments across their enterprise. To determine the required license capacity for each zseries IPLA program with referenced-based terms, each environment should be assessed separately. When a zseries IPLA sub-capacity program with reference-based terms is used in a qualified sysplex environment the required license capacity of the zseries IPLA program must equal with the license capacity of the parent program across the sysplex. Qualified sysplex refers to one: 1. Where MLC pricing is aggregated across the sysplex z/os-based terms z/os-based terms apply to zseries IPLA programs that provide value to the particular machine where the program executes. Under these terms, the required license capacity of a zseries IPLA program must equal the license capacity of z/os (and z/os.e) on the machine(s) where the zseries IPLA program executes. The applicable type of sub-capacity terms per zseries IPLA program is determined solely by IBM. Applicable terms per eligible program are listed in the section of this announcement letter. Subsequent zseries IPLA sub-capacity program announcements will indicate the type of sub-capacity terms, if applicable. Only one type of sub-capacity terms may apply per program. For a complete listing of the eligible zseries IPLA programs and their type of sub-capacity terms, refer to ipla.html Required and entitled license capacity The quantity of each zseries IPLA program needed to satisfy applicable IBM terms and conditions is referred to as the required license capacity. The quantity of each zseries IPLA program that you have acquired is referred to as your entitled license capacity. For each zseries IPLA program, IBM will compare your required license capacity with your entitled license capacity every month. In the case that your required license capacity exceeds your entitled licensed capacity, IBM will consider this an order for that zseries IPLA software program. Therefore, IBM will initiate an order on your behalf for additional license capacity for that program and issue you the related invoice. After you have acquired a zseries IPLA program, you cannot reduce your entitled license capacity for that zseries IPLA program. Subscription & Support for zseries IPLA programs is optional. If you elect to purchase Subscription & Support for a zseries IPLA program, the Subscription & Support capacity must be equal to the zseries IPLA program entitled license capacity across your enterprise. zseries MLC sub-capacity methodology Under IBM sub-capacity MLC offerings, WLC and EWLC, required license capacity for eligible MLC programs is determined based upon the highest observed rolling four-hour average utilization of the LPAR(s) where a program executes during a reporting period (second day of the month through the first day of the next month). This required license capacity per sub-capacity MLC program, is reported in terms of millions of service rnits (MSUs) on each monthly Sub-Capacity Report. For each sub-capacity eligible MLC program, the required license capacity is reevaluated based upon the monthly Sub-Capacity Report submitted to IBM. zseries IPLA sub-capacity methodology A zseries IPLA sub-capacity program with execution-based terms follows the same methodology as sub-capacity eligible MLC programs. The required license capacity for each zseries IPLA program with execution-based licensing will be based upon the highest rolling four-hour average utilization of the LPAR(s) where ZA

3 that zseries IPLA program executes. Each zseries sub-capacity IPLA program with execution-based terms and its required license capacity will appear in the monthly Sub-Capacity Report. Under these terms, the zseries IPLA required license capacity is reevaluated based upon the monthly Sub-Capacity Report(s) submitted to IBM. The required license capacity of a zseries IPLA sub-capacity program with reference-based terms is equal to the license capacity of the parent program (in the case of a qualified sysplex environment, the sysplex-wide license capacity of the parent program is used). zseries IPLA programs with reference-based terms will not appear on each monthly Sub-Capacity Report. Because your required license capacity is equal to the MSUs of the parent program, IBM will determine your required license capacity for that zseries IPLA program by reviewing the billable MSUs shown in the Sub-Capacity Report for the parent program (in the case of a qualified sysplex environment, the MSUs of the parent program on the Sub-Capacity Reports from all the machines in the sysplex will be considered). Under these terms, the zseries IPLA required license capacity is reevaluated based upon the monthly Sub-Capacity Report(s) submitted to IBM. The required license capacity of a zseries IPLA sub-capacity program with z/os-based terms is equal to the license capacity of z/os (and z/os.e) on the machine(s) where the zseries IPLA program is executing. zseries IPLA programs with z/os-based terms will not appear on each monthly Sub-Capacity Report. Because your required license capacity is equal to z/os MSUs, IBM will determine your required license capacity for that IPLA program by reviewing the billable z/os MSUs shown on the Sub-Capacity Reports for the machine(s) where the zseries IPLA program executes. Under these terms, the zseries IPLA required license capacity is reevaluated based upon the monthly Sub-Capacity Report(s) submitted to IBM. Value Unit Pricing The zseries IPLA programs affected by this announcement are priced according to Value Units. Value Unit pricing enables a lower cost of incremental growth and enterprise aggregation. Each zseries IPLA product with Value Unit pricing has a single price per Value Unit and a conversion plan, called Value Unit Exhibit, for converting from MSUs to Value Units. For each zseries IPLA program with Value Unit Pricing, you should: Determine the required license capacity in MSUs Aggregate the required license capacity across the enterprise Convert the total MSUs to Value Units, using the applicable Value Unit Exhibit, and Multiply the price per Value Unit by the total of Value Units to determine the total cost. To simplify conversion from MSUs to VUs 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 Eligibility requirements To be eligible for sub-capacity charging on select zseries IPLA programs, you must first implement and comply with all terms of either sub-capacity WLC or sub-capacity EWLC. To implement sub-capacity WLC or EWLC, a machine must be zseries (or equivalent). On that machine: All instances of the OS/390 operating system must be migrated to the z/os (or z/os.e) operating systems Any licenses for the OS/390 operating system must be discontinued All instances of the z/os operating (or z/os.e) 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 zseries 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 zseries Workload License Charges (Z ). The complete terms and conditions for sub-capacity EWLC are defined in the IBM Customer Agreement Attachment for z800 and z890 Software License Charges (Z ). Additionally, you must sign and comply with the terms and conditions specified in the amendment to the IPLA contract Amendment for zseries Platform s Sub-Capacity Pricing (Z ). Once the amendment is signed, the terms in the amendment replace any and all previous zseries IPLA sub-capacity terms and conditions. Clarifications on existing zseries IPLA terms and conditions The following terms and conditions apply to zseries IPLA programs in either full-capacity or sub-capacity environments: zseries IPLA programs with reference-based terms add value to the parent program across the environment, regardless of where in environment the zseries IPLA program executes. An environment is defined as either a single/stand-alone machine or a qualified parallel sysplex. You may have one or more different environments across your enterprise. To determine required license capacity for each zseries IPLA program with referenced-based terms, each environment should be assessed separately. Note: Most DB2 tools, CICS tools, and IMS tools are zseries IPLA programs with reference-based terms. When a zseries IPLA program with reference-based terms is used in a single/stand-alone machine environment, the required license capacity of the zseries IPLA program must (at least) equal the license capacity of the parent program on that machine. When a zseries IPLA program with reference-based terms is used in a qualified sysplex environment, the required license capacity of the zseries IPLA program -3- ZA

4 must (at least) equal the license capacity of the parent program across the sysplex. Qualified sysplex refers to one: 1. Where MLC pricing is aggregated across the sysplex zseries IPLA programs with reference-based terms have a single program family as the parent (for example, multiple versions of the MLC. program, DB2). When determining the required license capacity for the zseries IPLA program with reference-based terms, the billable MSUs of the parent will be used. In the case that multiple versions of the parent are billable (for example, the Single Version Charging period has ended but two versions are installed and billable) then the parent MSU capacity will be capped at the z/os MSU capacity. This calculation regarding parent MSUs will be performed separately on each mainframe to determine parent MSU capacity and, therefore, the required license capacity of the zseries IPLA program. For each zseries IPLA program, the sum of your acquired zseries IPLA licenses across your enterprise equals your enterprise-wide entitled license capacity. Subscription & Support for zseries IPLA programs is optional. If you elect to purchase Subscription & Support, the Subscription & Support capacity must equal your zseries IPLA enterprise-wide entitled license capacity. After you have acquired a zseries IPLA program, you cannot reduce your zseries IPLA entitled license capacity for that program. IBM does not distinguish between zseries IPLA entitled license capacity for sup-capacity and full-capacity environments. Entitled license capacity may be used to satisfy required license capacity in either sub-capacity or full-capacity environments. Excess entitled license capacity may be kept and used in the future to satisfy any increases in required license capacity, due to changes such as license moves or environment growth. If you purchase Subscription & Support for a particular zseries IPLA program, you are entitled to no-charge version upgrades for that program. If you have Subscription & Support, you may run multiple versions of the zseries IPLA program during six-month grace period. The grace period begins when the new zseries IPLA program is installed in the enterprise. Afterwards, it is expected that you will be migrated to the latest version. If you do not complete your migration within the grace period, IBM reserves the right to recalculate your required license capacity for the zseries IPLA program by combining the MSUs of the old version and the new version. Once you decide to adopt zseries IPLA sub-capacity, you must sign the IPLA Amendment for zseries Platform s Sub-Capacity Pricing (Z ). This contract may cover your entire enterprise. Under this contract, you agree to track all of your IBM zseries IPLA licenses and notify IBM of the location of execution of your zseries IPLA products. The scope of your tracking responsibilities includes all mainframes in your environment, including mainframes with either sub-capacity or full-capacity monthly license charges. If you are unable or unwilling to fulfill your tracking responsibilities, IBM may terminate the zseries IPLA amendment. In such an event, full-capacity terms would apply. If the IPLA amendment for zseries Platform s Sub-Capacity Pricing is not signed, full-capacity terms will apply unless specific sub-capacity terms are present in the license information document for a particular zseries IPLA program. For information on estimating required license capacity and a listing of the programs eligible for sub-capacity pricing, refer to the Additional information section. ZA

5 IBM Europe, Middle East, Africa Announcement Supplemental Information August 10, 2004 Additional information Estimating required license capacity If you wish to acquire a sub-capacity zseries IPLA product, you must make an estimate of their future required license capacity for that product. The method for estimating required license capacity depends on the applicable sub-capacity zseries IPLA licensing terms: For sub-capacity zseries IPLA programs with execution-based terms, look at the capacity of the LPAR(s) where the zseries IPLA program will execute, as reported on the previous month s sub-capacity reports. Each LPAR s capacity can be found in the Detail LPAR Data section of the sub-capacity reports For sub-capacity zseries IPLA programs with reference-based terms, look at the license capacity of the parent product as reported in the previous month s sub-capacity reports. Consider the license capacity of the parent product across all the machines in the parallel sysplex, if the zseries IPLA product is being added into a qualified parallel sysplex For sub-capacity zseries IPLA programs with z/os-based terms, look at the license capacity of z/os (and z/os.e) as reported in the previous month s sub-capacity report. Consider the license capacity of z/os (and z/os.e) across all the machines where the zseries IPLA product will be used The following examples depict different zseries sub-capacity customers estimating their required license capacity for a variety of zseries IPLA products. Sample Customer One: Fault Analyzer for z/os If Customer One wishes to acquire Fault Analyzer for z/os, determine the applicable terms for Fault Analyzer by visiting the IBM sub-capacity zseries IPLA Web site ipla.html After visiting the Web site, Customer One determines that Fault Analyzer is a sub-capacity zseries IPLA product with execution-based terms. Since Fault Analyzer is a sub-capacity zseries IPLA product with execution-based terms, Customer One must designate the LPAR(s) in which Fault Analyzer will execute. Customer One determines that they wish to run Fault Analyzer only in LPAR SYSA, which exists on a zseries machine X. Once Customer One has designated LPAR(s) where Fault Analyzer will run, they can look at the detail LPAR Data section in last month s sub-capacity reports to determine the capacity of the designated LPARs. Since Customer One has designated only one LPAR, SYSA, they need only consider the sub-capacity report for machine X, where LPAR SYSA exists. The detail LPAR Data section of the machine X s sub-capacity report will indicate the highest rolling 4-hour average of each LPAR on a given machine. The highest rolling 4-hour average utilization of SYSA equals the software-pricing related capacity of SYSA. Customer One must assess whether last month s sub-capacity reports will represent the capacity of the desired LPAR(s) in the future. For example, Fault Analyzer will run only in LPAR SYSA, and SYSA s capacity last month was 100 MSUs. However, consider that last month s 100 MSUs may be smaller than the expected future capacity of SYSA. In the case that SYSA may be growing in the future, Customer One may want to acquire a greater capacity of Fault Analyzer to ensure they have sufficient entitled license capacity in the future and, thus, avoid IBM-initiated billing. Here are some other options for Customer One: Constrain LPAR SYSA to limit the required license capacity of Fault Analyzer. Some examples of available capping techniques are enforcing the logical weight (sometimes known as hardcapping) or using defined capacity License Fault Analyzer based upon the maximum potential capacity of LPAR SYSA, to ensure that IBM-initiated billing does not occur. The simplest way to determine the maximum potential capacity of LPAR SYSA is by counting the of logical engines assigned to LPAR SYSA. If the LPAR SYSA has 4 logical engines and the machine has 12 physical engines with an MSU rating of 372 MSUs, then LPAR SYSA s maximum potential capacity is approximately (4/12)*372 MSUs = 124 MSUs. Sample Customer Two: DB2 Administration Tool for z/os If Customer Two wishes to acquire DB2 Administration Tool for z/os, determine the applicable terms for DB2 Administration Tool by visiting ipla.html After visiting the Web site, Customer Two determines that DB2 Administration Tool is a sub-capacity zseries IPLA product with reference-based terms. Since DB2 Administration Tool is a sub-capacity zseries IPLA product with reference-based terms, Customer Two must determine in which environments they wish to use the DB2 Administration Tool to add value to the parent product, DB2 UDB for z/os. Customer Two determines that they wish to use the DB2 Administration Tool to add value to DB2 in their New York-qualified Parallel Sysplex and to add value to DB2 in their stand-alone machine in Dallas. They will not yet be using the DB2 Administration Tool to add value to DB2 in their European qualified Parallel Sysplex. Once they have determined the environments(s) where DB2 Administration Tool will add value to DB2, Customer Two can look at the DB2 UDB for z/os MSUs in the Product Summary section of last month s sub-capacity reports to determine the required license capacity of DB2 Administration Tool. When making this calculation, Customer Two must look at the sub-capacity reports for This announcement is provided for your information only. For additional information, contact your IBM representative. IBM Europe, Middle East, Africa IBM is a registered trademark of International Business Machines Corporation. ZA

6 all the machines running DB2 in the New York qualified parallel sysplex and the sub-capacity report for the stand-alone machine in Dallas. Customer Two must assess whether last month s sub-capacity reports will represent the DB2 MSUs in the future. Consider that last month s DB2 MSUs may be smaller than the expected future capacity of the New York sysplex and the stand-alone Dallas machine. In the case that DB2 MSUs may be growing in the future, Customer Two may want to acquire a greater capacity of DB2 Administration Tool to ensure they have sufficient entitled license capacity in the future and, thus, avoid IBM-initiated billing. Sample Customer Three: Session Manager for z/os If Customer Three wishes to acquire Session Manager for z/os, determine the applicable terms for Session Manager by visiting ipla.html After visiting the Web site, Customer Three determines that Session Manager is a sub-capacity zseries IPLA product with z/os-based terms. Since Session Manager is a sub-capacity zseries IPLA product with z/os-based terms, Customer Three must determine which machines will use the Session Manager. Customer Three determines that they will use Session Manager on three machines: X, Y, and Z. Once they have determined the machines(s) where Session Manager will be used, Customer Three looks at the z/os MSUs in the Product Summary section of last month s sub-capacity reports to determine the required license capacity of Session Manager. When making this calculation, Customer Three must look at the sub-capacity reports for machines X, Y and Z. Customer Three must assess whether last month s sub-capacity reports will represent the z/os MSUs in the future. Consider that last month s z/os MSUs may be larger or smaller than the expected future z/os MSUs. In the case that z/os MSUs on Machines X, Y and Z may be growing in the future, Customer Three may want to acquire a greater capacity of Session Manager to ensure they have sufficient entitled license capacity in the future and, thus, avoid IBM-initiated billing. s eligible for sub-capacity The following list of the select zseries IPLA programs are eligible for sub-capacity charging: zseries IPLA Sub-capacity programs with execution-based terms 5655-I18 Migration Utility for OS/390 and z/os V I35 WebSphere Application Server for z/os V I39 Workload Simulator for z/os and OS/390 V I40 WebSphere Data Interchange for z/os V I49 WebSphere Studio Asset Analyzer V I58 WebSphere MQ Integrator Broker for z/os V J18 Debug Tool Utilities and Advanced Functions for z/os and OS/390 V J47 Fault Analyzer for z/os and OS/390 V J48 File Manager for z/os and OS/390 V J62 Application Workload Modeler for z/os V J67 WebSphere Studio Application Monitor for z/os and OS/390 V K12 WebSphere Portal for z/os and OS/390 V K57 WebSphere Business Integration Event Broker for z/os V K60 WebSphere Business Integration Message Broker for z/os V L03 SCLM Suite Administrator Workbench for z/os V L21 WebSphere Studio Asset Analyzer V L22 Application Monitor for z/os V L23 Debug Tool Utilities and Advanced Function for z/os V L25 Fault Analyzer for z/os V L26 File Manager for z/os V L42 WebSphere Studio Application Monitor for z/os V L50 CICS Data Collector for WebSphere Studio Application Monitor V L85 WebSphere Business Integration Server Foundation for z/os V F19 Fault Analyzer for OS/390 V F20 File Manager for OS/390 V G57 Cloud 9 for SCLM for OS/390 V G58 Breeze for SCLM OS/390 V H59 Enhanced Access Control for SCLM V H62 Automated Tape Allocation Manager for z/os and OS/390 V H63 Application Monitor for z/os and OS/390 V H70 Merge Tool for z/os and OS/390 V I11 WebSphere Business Integration Message Broker with R & F Extension for z/os V I89 Migration Utility for z/os V A02 Tivoli Access Manager for Business Integration Host Edition V A10 Tivoli Monitoring for Network Performance V A14 Tivoli System Automation for z/os V A17 Tivoli Workload Scheduler Host Edition V FNP Tivoli Monitoring for Network Performance V2 1 These products were previously defined as sub-capacity eligible. Refer to Marketing Announcement letter ZA dated September 30, BPM WebSphere MQ Workflow z/os V F31 WebSphere Application Server for z/os and OS/390 V G74 Fault Analyzer for z/os and OS/390 V G75 File Analyzer for z/os and OS/390 V G93 Cloud 9 for SCLM for z/os V G97 WebSphere MQ Integrator for z/os V I03 WebSphere Host Publisher for zseries V I14 WebSphere Studio Workload Simulator for z/os and OS/390 V1 1 ZA

7 zseries IPLA Sub-capacity programs with reference-based terms Parent program is CICS Transaction Server ( , , 5697-E93) 5655-F38 CICS Performance Analyzer for OS/390 V G76 CICS Interdependency Analyzer for z/os and OS/390 V H91 CICS VSAM Recovery V I05 CICS Online Transmission Time Optimizer for z/os V J99 CICS Business Event Publisher for MQSeries V L66 CICS VSAM Copy for z/os V I76 CICS VSAM Transparency for z/os V1 Parent program is DB2 UDB (5695-DB2, 5655-DB2, 5645-DB2, 5675-DB2, 5625-DB2) 5655-E39 DB2 Path Checker for z/os V E43 DB2 Bind Manager for z/os V E46 DB2 Data Export Facility for z/os V E54 DB2 Buffer Pool Analyzer for z/os V E56 DB2 Log Analysis Tool for z/os V E60 DB2 DataPropagator V E61 DB2 Performance Monitor V E64 DB2 Administration Tool for z/os V E65 DB2 Row Archive Manager V E66 DB2 Log Analysis Tool for OS/390 V E67 DB2 Query Monitor for z/os V E69 DB2 High Performance Unload V E70 DB2 Administration Tool for OS/390 V E71 DB2 Web Query Tool V E72 DB2 Object Restore Tool for z/os V E98 DB2 Utilities Suite for z/os V E98 DB2 Utilities Suite for z/os V D38 DB2 Bind Manager for OS/390 V F54 DB2 Archive Log Compression Tool for z/os V F55 DB2 Change Accumulation Tool for z/os V I19 DB2 High Performance Unload for z/os V I20 DB2 Object Comparison Tool for z/os V I21 DB2 Performance Expert for z/os V I22 DB2 SQL Performance Analyzer for z/os V I23 DB2 Administration Tool for z/os V I60 DB2 DataPropagator for z/os V I95 DB2 Data Archive Expert for z/os V J49 DB2 Performance Expert for z/os V J50 DB2 Performance Monitor for z/os V K61 DB2 Utilities Suite for z/os V F57 DB2 SQL Performance Analyzer for OS/390 V G52 DB2 Forms for OS/390 V G63 DB2 Automation Tool for z/os V G64 DB2 Object Comparison Tool for z/os V G65 DB2 Table Editor for z/os V H82 DB2 Buffer Pool Analyzer for z/os V I02 DB2 Test Database Generator for z/os V I03 DB2 Query Monitor for z/os V I20 DB2 Object Comparison Tool for z/os V I23 DB2 Path Checker for z/os V I73 DB2 Archive Log Accelerator for z/os V I80 DB2 Automation Tool for z/os V K40 DB2 Object Comparison Tool for z/os V K90 DB2 Administration Tool for z/os V5 Parent program is IMS ( , , 5655-B01, 5655-C56, 5655-J38) 5655-E02 IMS HD Compression Extended for z/os V E03 IMS Database Repair Facility for OS/390 V E06 IMS High Performance Unload V E07 IMS High Performance Load V E08 IMS High Performance Prefix Resolution V E09 IMS High Performance Pointer Checker for OS/390 V E10 IMS Image Copy Extensions for OS/390 V E11 IMS Sequential Randomizer Generator V E12 IMS Extended Terminal Option Support for z/os V E14 IMS Restart Facility V E15 IMS Performance Analyzer for OS/390 V E24 IMS Index Builder for z/os V E30 IMS Fast Path Basic Tools for z/os V E31 IMS Fast Path Online Tools V E32 IMS DEDB Fast Recovery for z/os V E41 IMS Network Compression Facility for z/os V E50 IMS Database Recovery Facility for z/os V E51 IMS Connect for z/os V E52 IMS DataPropagator for z/os V E99 IMS Queue Control Facility for OS/390 V F40 IMS Command Control Facility V F43 IMS High Performance Sysgen Tools V F45 IMS Message Format Services Reversal Utilities V F59 IMS High Performance Change Accumulation Utility for z/os V F74 IMS Parallel Reorganization for z/os V F76 IMS Database Control Suite for z/os V F78 IMS Fast Path Online Tools for z/os V G50 IMS Performance Monitor for z/os V I01 IMS HALDB Conversion Aid for z/os V I15 IMS High Performance Prefix Resolution for z/os V I42 IMS Library Integrity Utilities for z/os V I44 IMS Database Recovery Facility for z/os V J56 IMS Image Copy Extensions for z/os V J57 IMS Batch Terminal Simulator for z/os V K47 IMS HALDB Conversion & Maintenance Aid for z/os V K48 IMS Connect Extensions for z/os V K50 IMS Problem Investigator for z/os V K52 IMS Connect for z/os V K53 IMS High Performance Pointer Checker for z/os V K96 IMS High Performance Image Copy for z/os V L08 IMS Database Control Suite for z/os V L61 IMS Extended Terminal Option Support for z/os V H75 IMS Batch Backout Manager for z/os V H77 IMS Buffer Pool Analyzer for z/os V H91 IMS Multi-Dialog Manager for z/os V1 zseries IPLA Sub-capacity programs with z/os-based terms Ties to z/os (5694-A01) 5655-K01 Session Manager for z/os V A03 Tivoli Business Systems Manager V A08 Tivoli Information Management for z/os V A15 Tivoli Web Access for Information Management V1-3- ZA

8 Trademarks IMS, z/architecture, and DataPropagator are trademarks of International Business Machines Corporation in the United States or other countries or both. The e-business logo, zseries, DB2, CICS, WebSphere, Tivoli, z/os, Parallel Sysplex, OS/390, MQ Integrator, and MQSeries are registered trademarks of International Business Machines Corporation in the United States or other countries or both. Other company, product, and service names may be trademarks or service marks of others. ZA