IBM United States
Software Announcement 201-331
November 13, 2001
IBM Parallel Environment V3.2 Enhanced for AIX 5L with New Performance Analysis Tools
(Corrected on January 30, 2002)
In Ordering Information, under Current Licenses section, the first sentence was delete. Software Maintenance (5771-PAE - 5773-PAE) section under Existing Customers of Parallel Environment, replaced with new information.
(Corrected on December 10, 2001)
Text was added "but not for 64-bit kernel" everywhere 64-bit applications or 64-bit executables was found.
(Corrected on November 26, 2001)
Supplemental section, Direct Customer Support section -- first sentence
At a Glance
Parallel Environment V3.2 is designed to contain a rich set of functional enhancements , including:
Additional V3.2 changes:
IBM Parallel Environment for AIX® 5L Version 3, Release 2 (V3.2) is a high-function development and execution environment for parallel applications using either the IBM Cluster 1600, RS/6000® SP system, or one or more clustered IBM pSeries or RS/6000 servers.
Parallel Environment V3.2 Functional Enhancements
Parallel Environment V3.2 Enhancements
New Parallel Environment Benchmarker Tools: This release of Parallel Environment contains a new suite of applications and utilities that you can use to analyze the performance of programs. This suite of tools is called Parallel Environment Benchmarker and contains:
Improved Parallel Checkpointing Capabilities: This release of Parallel Environment is designed to include more flexible parallel checkpoint/restart capabilities. In previous releases, only Parallel Operating Environment (POE)/MPI applications submitted under LoadLeveler in batch mode could be checkpointed, with significant limitations. What's more, a checkpoint sequence could be initiated only by all tasks in the parallel MPI program. In this release, Parallel Environment's checkpointing capabilities have been extended to allow:
Also, many significant limitations of the checkpointing capabilities have been removed, and the checkpointing compiler scripts (mpcc_chkpt, for example) are no longer used.
MPI Enhancements: With this release, Parallel Environment MPI is designed to provide all of the functions in the MPI standard, except for the functionality defined in "Process Creation and Management" chapter of MPI-2.
Additional Command for Starting MPI Jobs
While you can continue to use the poe command to start MPI jobs, this release of Parallel Environment is designed to provide support for the mpiexec command described in the MPI-2 standard. This command is not meant to replace the poe command. Instead, it is provided as a portable way to start MPI programs, and should prove helpful for applications that target multiple implementations of MPI.
Support for 64-bit Applications, but not for 64-bit Kernel
Certain architectures that Parallel Environment supports, such as POWER3 SMP High Node, POWER3 SMP Thin Node, POWER3 Wide Node, and POWER4 nodes, can run applications using a 64-bit address space. Accordingly, the tools that are provided with Parallel Environment, as well as the MPI threads library, have been enhanced to support 64-bit applications, but not for 64-bit kernel on 64-bit processors.
MPI-IO Performance Enhancements
To improve the performance of IBM's implementation of MPI-IO, a variety of optimizations have been made to this release of Parallel Environment. For example, two new POE environment variable/command-line flag pairs and one new file hint have been added. The two new POE environment variable/command-line flag pairs are the:
The new file hint, IBM_sparse_access, enables you to specify whether the file access requests from participating tasks are sparse or dense.
Extended Collective Communications
This release provides the MPI_IN_PLACE and intercommunicator semantic that MPI-2 has added to a number of MPI 1.1 collective communication subroutines. The new subroutines, MPI_ALLTOALLW and MPI_EXSCAN, are also provided. The nonblocking collective subroutines, which have a prefix of MPE_I, are not enhanced.
C++ and Fortran 90 Support
This release provides the C++ bindings described by MPI-2. C++ programmers can now use Parallel Environment MPI more naturally, as they no longer need to use the C bindings. The nonblocking collective subroutines, which have a prefix of MPE_I, are not enhanced for C++. Fortran 90 programs can now use the MPI module in place of mpif.h.
MPI-2 External Interfaces Support
With this release, Parallel Environment now provides full support of MPI-2 external interfaces in the MPI threads library. This support enables you to layer additional functionality on top of MPI with an interface that is similar to MPI's.
Miscellaneous MPI-2 Enhancements
Some of the functions included in the "Miscellany" chapter of MPI-2 were provided in prior releases of Parallel Environment. This release provides the rest of these miscellaneous functions.
LAPI Now Packaged with Parallel Environment: The LAPI, previously packaged only with Parallel Systems Support Program (PSSP), is now also shipped with Parallel Environment, for use on stand-alone RS/6000 workstations, where fileset ssp.css is not installed. For RS/6000 SP installations, LAPI will continue to be installed from PSSP as part of ssp.css.
The LAPI library provided with Parallel Environment supports the LAPI shared memory execution model only. This model is meant for applications that execute on the same node, to take advantage of the efficient shared memory protocol, rather than the SP switch adapter.
The following are enhancements to LAPI shared memory execution model:
Dynamic Probe Class Library (DPCL) Now an Open Source Offering: The DPCL is no longer a part of the IBM Parallel Environment for AIX licensed program, but it is still shipped with Parallel Environment for convenience. Instead, DPCL is now available as an open source offering that supports Parallel Environment. For more information on the DPCL open source project, visit:
Removal of pedb Debugger Support: Parallel Environment V3.2 no longer includes the pedb parallel debugger. As a result, the pedb command is no longer available. The pdbx parallel debugger, however, is still supported; use it instead of pedb to debug your parallel applications.
Removal of Visualization Trace (VT) Trace Collection Support: Parallel Environment V3.2 no longer supports the parallel trace collection facility formerly used by the Parallel Environment VT (which was removed from Parallel Environment in R3.1). Because the usefulness of examining these traces independent of VT is limited, the VT trace facility has been replaced by the more robust tracing capabilities of the new Parallel Environment Benchmarker suite of tools.
Accessibility by People with Disabilities
For Software Offerings
The following features support use by people with disabilities:
This program is not impacted by euro currency.
Parallel Environment is a must for IBM Cluster 1600, including SP, customers who develop, debug, analyze, tune, and execute parallel C/C++ and Fortran applications that use the industry-standard MPI.
Parallel Environment is IBM's strategic high-function development and execution environment for parallel applications using either the pSeries or RS/6000 servers or SP systems. Parallel Environment is designed to exploit SMP nodes as well as threaded applications and the MPI message passing API, and is now available on AIX 5L. Parallel Environment V3.2 is also supported on the new pSeries p690 in Switch-less stand-alone mode.
Parallel Environment V3.2 tool and MPI Threads libraries now support 64-bit applications, but not for 64-bit kernel
The Parallel Environment for AIX® 5L program product is a complete environment designed for developing and executing parallel Fortran, C, or C++ programs. Parallel Environment consists of components and tools for developing, executing, debugging, profiling, and tuning parallel programs.
The Parallel Environment is a distributed memory message passing system. It runs on the IBM pSeries, IBM Cluster 1600, or RS/6000® platform using the AIX 5L V5.1 operating system. Specifically, you can use the Parallel Environment to execute parallel programs on:
The pSeries or RS/6000 processors of your system are called processor nodes. If you are using a Symmetric Multiprocessor (SMP) system, it is important to know that, although an SMP node has more than one processing unit, it is still considered, and referred to as, a processor node.
A parallel program executes as a number of individual, but related, parallel tasks on a number of your system's processor nodes. The group of parallel tasks is called a partition (not to be confused with an LPAR partition). The processor nodes are connected on the same LAN, so the parallel tasks of your partition can communicate to exchange data or synchronize execution. If you are using an SP system:
Parallel Environment supports the two basic parallel programming models Single Program Multiple Data (SPMD) and Multiple Program Multiple Data (MPMD). In the SPMD model, the programs running the parallel tasks of your partition are identical. The tasks, however, work on different sets of data. In the MPMD model, each task may be running a different program. A typical example of this is the master/worker MPMD program. In a master/worker program, one task, the master, coordinates the execution of all the others the workers.
Note: While the remainder of this introduction describes each of the Parallel Environment components and tools in relation to a specific phase of an application's life cycle, this does not imply that they are limited to one phase. They are ordered this way for descriptive purposes only; you will find many of the tools useful across an application's entire life cycle. The application developer begins by creating a parallel program's source code. The application developer might create this program from scratch or could modify an existing serial program. In either case, the developer places calls to Message Passing Interface (MPI) or Low-level Application Programming Interface (LAPI) routines so that it can run as a number of parallel tasks. This is known as parallelizing the application.
The MPI has some similarity with the Message Passing Library (MPL) from an earlier version of Parallel Environment, but complies with an industry standard and is much more versatile. MPI provides message passing capabilities for the current version of Parallel Environment. There are two libraries for MPI:
All tasks of a program must use either the signal handling or the threaded library, but not a combination of each. MPL programs are still supported for 32-bit, non-threaded applications only. The message passing calls enable the parallel tasks of your partition to communicate data and coordinate their execution. The message passing routines, in turn, call communication subsystem library routines which handle communication among the tasks of a job. There are two separate implementations of the communication subsystem library the Internet Protocol (IP) Communication Subsystem and the User Space (US) Communication Subsystem. While the message passing application interface remains the same, the communication subsystem libraries use different protocols for communication among tasks of a job. The IP communication subsystem uses Internet Protocol, while the US communication subsystem is designed for the SP system's high performance switch feature. The communication subsystem library implementations are dynamically loaded when you invoke the program. For more information on the message passing subroutine calls, refer to IBM Parallel Environment for AIX: MPI Subroutine Reference, IBM Parallel Environment for AIX: MPL Programming and Subroutine Reference, and IBM Parallel Environment for AIX: Hitchhiker's Guide.
In addition to MPI message passing communication, the Parallel Environment supports a separate communication protocol known as the Low-level Application Programming Interface. LAPI differs from MPI in that it is based on an "active message style" mechanism that provides a one-sided communications model. That is, one process initiates an operation and the completion of that operation does not require any other process to take a complementary action.
LAPI is designed and optimized to use the SP Switch or SP Switch2 communication fabric available with the Cluster 1600. However, it may also be used on a stand-alone (not clustered) pSeries server when all tasks (processes) are on the same server. In this case, it uses shared memory to communicate between tasks.
Although LAPI can be used for data communication in conjunction with Parallel Environment, it is actually part of the communication subsystem for IBM Parallel System Support Programs (PSSP). For more information on LAPI, refer to IBM Parallel System Support Programs for AIX: Administration Guide, and IBM Parallel System Support Programs for AIX: Command and Technical Reference on:
After writing the parallel program, the application developer then begins a cycle of modification and testing. The application developer now compiles and runs his program from his home node using the Parallel Operating Environment (POE). The home node is any workstation on the LAN. POE is an execution environment designed to hide, or at least smooth, the differences between serial and parallel execution.
To assist with node allocation for job management, LoadLeveler provides resource management function both on and off the SP system. You can run parallel programs on a cluster of processor nodes running LoadLeveler, or on a mixed system of LoadLeveler processor nodes that supplement an SP system. LoadLeveler not only provides SP node allocation for jobs using the US communication subsystem, but also provides management for non-SP nodes, or for SP nodes being used for jobs other than User Space. LoadLeveler can also be used for POE batch jobs. Refer to the IBM LoadLeveler documentation for more information on this job management system.
In general, with POE, you invoke a parallel program from your home node and run its parallel tasks on a number of remote nodes. When you invoke a program on your home node, POE starts your Partition Manager which allocates the nodes of your partition and initializes the local environment. Depending on your hardware and configuration, the Partition Manager uses a host list file, LoadLeveler, or both a host list file and LoadLeveler to allocate nodes. A host list file contains an explicit list of node requests, while LoadLeveler can allocate nodes from one or more system pools implicitly based on their availability.
When using LoadLeveler, POE provides an option to enable you to specify whether your program will use MPI, LAPI, or both. Using this option, POE checks that each API initializes properly and informs LoadLeveler which APIs are used so each node is set up completely.
For SPMD applications, the Partition Manager executes the same program for all tasks. For MPMD applications, the Partition Manager prompts you for the name of the program to load for each task. The Partition Manager also connects standard input/output (I/O) to each remote task so the parallel tasks can communicate with the home node. Although you are running tasks on remote nodes, POE allows you to continue using the standard UNIX and AIX execution techniques with which you are already familiar. For example, you can redirect input and output, pipe the output of programs, or use shell tools. The POE includes:
The following tools are discussed in IBM Parallel Environment for AIX: Operation and Use, Volume 2 on:
and allow you to debug and tune parallel programs.
Details of Parallel Environment V3.2 enhancements and changes may be found in the Description section of this announcement.
Product information is available through Offering Information (OITOOL) at:
The following publications are on the media in HTML and PDF formats, and can also be printed from the Resource Center CD-ROM.
Publication Title Number IBM Parallel Environment for AIX: GA22-7418 Installation Guide IBM Parallel Environment for AIX: GA22-7419 Messages IBM Parallel Environment for AIX: SA22-7422 MPI Programming Guide IBM Parallel Environment for AIX: SA22-7423 MPI Subroutine Reference IBM Parallel Environment for AIX: SA22-7424 Hitchhikers Guide IBM Parallel Environment for AIX: SA22-7425 Operation and Use Vol. 1, Using the Parallel Operating Environment IBM Parallel Environment for AIX: SA22-7426 Operation and Use Vol. 2, Tools Reference
These publications may also be viewed at:
(Specify country, then search on PARALLEL ENVIRONMENT.)
Displayable Softcopy Publications
On the same medium as the Parallel Environment product code, IBM ships Parallel Environment manual pages, HTML files, and PDF files. In order to use these publications, you must first install the appropriate fileset: ppe.html, ppe.pdf, or ppe.man.
To view the Parallel Environment HTML publications, you need access to an HTML document browser such as Netscape. The HTML files and an index that links to them are installed in the /usr/lpp/ppe.html directory. Once installed, you can also view the HTML files from the RS/6000 SP Resource Center.
To view the Parallel Environment PDF publications, you need access to the Adobe Acrobat Reader 3.0.1. The Acrobat Reader is shipped with the AIX 5L V5.1 Bonus Pack and is also freely available for downloading from the Adobe Web site at:
Specified Operating Environment
Compatibility: Parallel Environment V3.2 is a functional enhancement of Parallel Environment V3.1, with support for AIX 5L V5.1 only. Parallel Environment V3.1 will remain orderable for the AIX V4.3.3 operating system platform. The end of service date for Parallel Environment V3.1 is not affected by this announcement.
Programs compiled with prior versions of Parallel Environment using shared library support are binary compatible. That is, executables built using Parallel Environment V2.1, V2.2, V2.3, V2.4, and V3.1 will run correctly with Parallel Environment V3.2.
Applications compiled with XL High Performance Fortran for AIX, V1.3.1 (5765-612) will be supported by the Parallel Environment for AIX, V3.2 MPI Signals Library.
Parallel ESSL for AIX, V2.3 (5765-C41) supports the Parallel Environment for AIX, V3.2 MPI Signals Library and the MPI Threaded library.
When Parallel Environment is used with the SP system, Parallel Environment jobs can only run in a PSSP system partition that has all of its nodes at the same PSSP level.
In a particular PSSP system partition, IBM Parallel Environment for AIX V3.2 requires PSSP V3.4.
LAPI programs cannot be run on RS/6000 clusters or on the High Performance Switch. LAPI only supports the SP Switch or the SP Switch2, or single stand-alone servers using shared memory. The following are the requirements and limitations for using LAPI shared memory on a stand-alone server:
The non-threaded MPI library was functionally stabilized with the general availability of Parallel Environment V3.1, and no new functionality in the non-threaded library beyond that provided in the initial general availability of Parallel Environment V3.1 is provided.
The following features are supported only in the threaded MPI library:
Because MPL is in only the non-threaded library, continued use of MPL is incompatible with exploiting MPI enhancements.
The following table summarizes the limits on the total number of tasks in a parallel job and the maximum number of tasks on a node (operating system image). If two limits are listed, the most restrictive limit applies.
Total Tasks Protocol Task per Node Library Switch/Adapter Limit Limit IP any 1024 32 IP any 2048 16 User Space SP Switch/any 1024 4 User Space SP Switch2/Switch2 4096 16 User Space SP Switch2/PCI 4096 32
Customer Responsibilities: When ordering Parallel Environment for an RS/6000 SP system, you may order copies for a sub-set of the total nodes of your SP system based on your requirements. In estimating your license requirements, you will want to take into consideration the number of jobs that may be concurrently running, and the number of nodes that those jobs will be collectively using. The number of copies to be ordered should be the predetermined number of total nodes to be enabled with Parallel Environment, and, thus, the maximum number of nodes on which the Parallel Environment could run.
For all processors and servers within or attached to an RS/6000 SP or any cluster of servers, the same release level of the Parallel Environment software is required.
On the RS/6000 SP system with SP Switch, a function of PSSP called system partitioning is available. When using PSSP system partitioning, sets of nodes within one partition are not able to communicate with nodes in other partitions across the SP Switch. Normally, nodes within a partition can be at different software levels. However, nodes running Parallel Environment must be at a consistent level of software within a system partition. In general, a single Parallel Environment application will not be able to communicate across system partitions (with the exception of an Internet Protocol job using a hostlist file and all partitions are at the same software level.)
Direct Customer Support: Direct customer support in the form of Software Maintenance is now included in the price of each product in this announcement, for one year from date of acquisition. Additional one-year and three-year renewal options are available under the new IBM Agreement for Acquisition of Support (Z125-6011), and The Addendum for Support (Software Maintenance) for Select iSeries and pSeries Programs (Z125-6495).
For information regarding Software Maintenance, call 800-IBM-4YOU (426-4968) or visit:
Eligible customers can obtain installation and usage assistance from the AIX Support Family line at 800-225-5249.
To obtain customer eligibility and registration procedures, contact the appropriate support center.
Security, Auditability, and Control
The announced program uses the security features of the AIX 5L V5.1 operating system. No additional security enhancements are included in this announcement.
The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.
Parallel Environment is a product that has one charge unit: Authorizations. These are available in order quantities of 1 5, 6 10, 11 50, and greater than 50.
Note: Charge units for SP-based products are based on nodes; charge units for workstations and servers are based on the number of physical installations of the product (for example, installation on a system or LPAR partition). The number of authorizations desired should be based on each installation of the product.
Software Maintenance information
IBM Software Maintenance (IBM Agreement for Acquisition of Support (Z125-6011), and The Addendum for Support (Software Maintenance) for Select iSeries and pSeries Programs (Z125-6495)), is a one-year or three-year contract offering that enables you to maintain software product version and release currency, with voice support during normal business hours included at no additional charge for the first year, for selected AIX and UNIX-based software products at a predetermined cost. One year of Software Maintenance is included in the price of the original license. For products participating in IBM Software Maintenance, you can receive all software product version and release upgrades and voice support, announced during the contract period. If you allow either the one-year or three-year software maintenance offering to expire without renewal, there will be a "Maintenance-After-License" option to enable reinstatement in the IBM Software Maintenance offering, on a product-by-product basis.
The following is general information regarding the Software Maintenance Offering being announced:
Definition of Software Upgrade
An upgrade is either a new version (3.x.x to 4.x.x) or a new release (x.3.x to x.4.x) of an IBM program announced as eligible for which you enrolled under the IBM Software Maintenance. Software Maintenance entitles you to future upgrades from only the latest announced version or release of an available eligible product.
Upgrades do not include programs sold separately from the enrolled program, but enhance the performance of that program, or are considered add-ons or utilities. Programs that perform the same functions as the enrolled program but are installed on a non-AIX platform are not considered upgrades.
Note: Software preventative maintenance releases x.x.1 to x.x.2 (modification level changes, updates, or refreshes) are released under the one-year or three-year maintenance program numbers, but only when a supply feature has been announced. Supply features are only announced under the one-year and three-year options when there is an announced version/release change against the original program product. No-charge preventative maintenance releases should be obtained by Software Maintenance customers in the same manner as non-Software Maintenance customers.
Example: Product A is offered under IBM Software Maintenance and three months later PTFs are incorporated into the program package. This is considered an update that would not be obtained under the one-year or three-year maintenance program numbers under the IBM Software Maintenance offering. Using the same example above, three months after the PTFs were incorporated into the program package, IBM announced a new version of product A. At that time, a supply feature is announced for product A under the one-year and three-year maintenance program numbers. This allows customers who are entitled either by purchase or when the first year of maintenance is included with the license, of either the one-year or three-year maintenance offering for product A, to order the upgrade under the one-year or three-year offering.
IBM may announce a product that can be substituted for an enrolled product. This product is neither a new version, a new release, nor a preventative maintenance release of that enrolled product. In most cases, this product has a different architecture, more function, and a higher license charge than the enrolled product. IBM may provide those customers enrolled in the IBM Software Maintenance offering access to this product at a discounted rate. The terms of this transaction will be included in the new product announcement.
Note: IBM will not offer stand-alone upgrades as a standard product offering. Stand-alone upgrades to this product/release, and its future versions and releases, will be considered only on a special request basis by IBM. Contract Duration
The IBM Software Maintenance contracts are on a product-by-product basis and are offered for one or three years. One year of Software Maintenance is included with the purchase of a new license for the product. The three-year prepay option covers two additional years of coverage since the first year is included in the product license. The three-year prepay option can be purchased at the same time a license for an eligible product is purchased. Refunds do not apply if cancellation occurs during the one- or three-year contract period. Customers are not required to renew under either the one- or three-year offering when the contract expires, but will need to use the Maintenance-After-License option should they let the contract expire and want to acquire a new version or release of an eligible product. If the one- or three-year contracts aren't renewed, the one- or three- year contracts will be removed from IBM administrative systems. Contract transfer within an enterprise are allowed.
Customers enroll in the plan at a reduced "Initial" price at the same time a new license for an eligible program product is purchased. Customers can also enroll in the plan after purchase of a new license for an eligible program product is purchased, but must purchase the "Maintenance-After-License" option.
Software Maintenance Prices
The IBM Software Maintenance program prices are based on the published price of the software program at the time of the contract preparation.
Minimum Contract Value: None
Notification of Upgrade Availability and Offering
Changes are currently underway to the Web server where customers will register for e-mail notifications when Software Maintenance products are upgraded. Availability of this service is expected first quarter 2002. The Software Maintenance component of the Web server will be found at:
A customer ordering a new license for Parallel Environment licensed program (5765-D93) must include a one-year (5771-PAE) or a three-year (5773-PAE) maintenance order to be entitled to future version or release updates of the licensed program. Not only will customers be entitled to future version or release updates, this new offering includes a year of voice support at no additional costs. Customers entering a one-year or three-year Software Maintenance offering for Parallel Environment should specify machine type/model 5771-PAE or 5773-PAE. After selecting the one-year or three-year machine type/model, customers should add the applicable billing features with quantity equal to the number of licenses in the contract.
Program Name: Parallel Environment V3.2
New users of Parallel Environment for AIX V3 should specify machine type 5765, model D93, asset feature number 9001, the appropriate Parallel Environment V3.1 for AIX V4 or Parallel Environment V3.2 for AIX 5L Medium feature number, and the appropriate one-time charge (OTC) feature number in quantity equal to the total number of desired licenses to be installed times the quantity of authorizations.
OTC Medium Order-Type Machine Feature Feature Description Type/Model Number Number Medium Parallel Environment V3.1 for AIX V4 1 to 5 Authorizations 5765-D93 0001 5000 CD-ROM 6 to 10 Authorizations 0002 11 to 50 Authorizations 0003 51 or greater Authorizations 0004 Parallel Environment V3.2 for AIX V5 1 to 5 Authorizations 5765-D93 0001 5809 CD-ROM 6 to 10 Authorizations 0002 11 to 50 Authorizations 0003 51 or greater Authorizations 0004
Upgrades: Upgrades are no longer offered. Refer to the Software Maintenance section below.
Software Subscription for AIX 5692-SSO
Customers who purchased protection for Parallel Environment V3.1 for AIX, under Software Subscription for AIX (5692-SSO) are entitled to receive Parallel Environment for AIX 5L V3.2 at no charge (NC). Eligible customers should add CD media supply feature number 0591 under their existing 5692-SSO record. Parallel Environment V3.2 for AIX is offered on CD-ROM media only.
Software Maintenance is NOT included with licenses or medium obtained via Software Subscription upgrade. Support Line contracts will be honored until their expiration. Customers who obtain Parallel Environment V3.2 under SSO upgrade from Parallel Environment V3.1 MAY optionally purchase One-Year or Three-Year Software Maintenance. Customers wishing to do so should place an order for 5771-PAE (One-Year) or 5773-PAE (Three-Year) and specify the desired Authorizations feature number from the RENEWAL column in the tables in the Software Maintenance section below.
5692-SSO Eligible Medium Billing Supply Order-Type Feature Feature Description ASC(1) CD-ROM From 5765-D93 V3.1 0591 to 5765-D93 V3.2 1 to 5 Authorizations 6466 6470 6471 6 to 10 Authorizations 6467 6636 6637 11 to 50 Authorizations 6468 6638 6639 51 or More Authorizations 6469 6640 6641
Current licensees of Parallel Environment V3.1 who do
have an active AIX Software Subscription or AIX/UNIX Upgrade Protection
contract can order an upgrade to Parallel Environment V3.2 by contacting
their IBM representative or IBM reseller and requesting an order be
placed for either the one year (5771-PAE) or three year (5773-PAE)
Maintenance and specifying the appropriate After-License feature and
supply feature from the table below.
Software Maintenance (5771-PAE or 5773-PAE)
Software Subscription for AIX is no longer an offering. The replacement offering is called Software Maintenance.
General Information on Software Maintenance
The Software Maintenance Offering was previously announced (Refer to Software Announcement 201-201 , dated July 10, 2001). The following are some key points from the original announcement.
The following term differs from the above Software Announcement: Stand-alone upgrades to this product/release, and its future versions and releases, will be considered only on a special request basis from IBM.
Ordering Information for Software Maintenance
For additional information on the IBM Software Maintenance for Select pSeries Programs, visit:
New Licensees of Parallel Environment:
The software license for new customers of Parallel Environment (5765-D93) will include Software Maintenance, for one year. The three-year option is the configurator default and it configures the price for the second and third year of the contract only. Customers should select the one-year or three-year PID, the appropriate feature number and quantity to extend coverage for their software licenses.
Note the following for New Licensee:
OTC One-Year Software Maintenance Program 5771-PAE
Maintenance- After- Current Registration Renewal License Licensee NC Billing Billing Supply Feature Feature Feature Feature Program Name Number Number Number Number Parallel Environment (5765-D93) 5809 1 to 5 Authorizations 0014 0018 0022 6 to 10 Authorizations 0015 0019 0023 11 to 50 Authorizations 0016 0020 0024 51 or more Authorizations 0017 0021 0025
OTC Three-Year Software Maintenance Program 5773-PAE
Maintenance- After- Current Renewal License Licensee Registration Billing Billing Supply Feature Feature Feature Feature Program Name Number(2) Number Number Number Parallel Environment (5765-D93) 5809 1 to 5 Authorizations 0013 0017 0021 6 to 10 Authorizations 0014 0018 0022 11 to 50 Authorizations 0015 0019 0023 51 or more Authorizations 0016 0020 0024
Withdrawal of Parallel Environment V3.1 Base License and Upgrade Feature Numbers
The following base license and upgrade feature numbers are withdrawn effective April 8, 2002.
Parallel Environment V3.1 is now ordered as a separate Medium Supply feature number (5000) under 5765-D93.
Program Feature Description Number Number Parallel Environment V3.1 5765-D93 3001 3002 3003 3004 3005 3006 3007 3008
Withdrawal of Software Subscription for AIX Feature Numbers
The effective withdrawal date of the following feature numbers is April 8, 2002.
Program Feature Description Number Number Software Subscription for 5692-SSO 6466 6470 6471 for Parallel Environment 6467 6636 6637 V3.1 6468 6638 6639 6469 6640 6641
Customization Options: Select the appropriate feature numbers to customize your order with delivery options desired. These features can be specified on the initial or MES orders.
Feature Description Number Initial Shipments Serial Number Only (suppresses shipment 3444 of media and documentation) Expedite Shipments Local IBM Office Expedite 3445 (for IBM use only) Customer Expedite Process Charge 3446 ($30 charge for each product)
Expedite shipments will be processed to receive 72-hour delivery from the time IBM Software Delivery and Fulfillment (SDF) receives the order. SDF will then ship the order via overnight air transportation.
Terms and Conditions
The following agreements apply for maintenance and do not require customer signatures:
The prices provided in this announcement are suggested retail prices for the U.S. only and are provided for your information only. Dealer prices may vary, and prices may also vary by country. Prices are subject to change without notice. For additional information and current prices, contact your local IBM representative.
Program Name: Parallel Environment, V3.2
New users of Parallel Environment for AIX V3 should specify machine type 5765, model D93, asset feature number 9001, the appropriate Parallel Environment V3.1 for AIX V4 or Parallel Environment V3.2 for AIX 5L Medium feature number, and the appropriate OTC feature number in quantity equal to the total number of desired licenses to be installed times the quantity of Authorizations.
OTC Order-Type Machine Feature Description Type/Model Number OTC 1 to 5 Authorizations 5765-D93 0001 $9,141 6 to 10 Authorizations 0002 7,102 11 to 50 Authorizations 0003 5,024 51 or greater Authorizations 0004 3,035
Main- tenance- Regis- After- tration Renewal License NC Billing Billing Feature Feature Feature LPP Program Name Number OTC Number OTC Number OTC Software Maintenance -- One Year (5771-PAE) 1 to 5 Authorizations 0014 NC 0018 $2,031 0022 $4,063 6 to 10 Authorizations 0015 NC 0019 1,578 0023 3,175 11 to 50 Authorizations 0016 NC 0020 1,117 0024 2,233 51 or more Authorizations 0017 NC 0021 675 0025 1,349
NC = No Charge
Main- tenance- After- Regis- Renewal License tration Billing Billing Feature Feature Feature LPP Program Name Number OTC Number OTC Number OTC Software Maintenance -- Three Year (5773-PAE) 1 to 5 0013 $4,063 0017 $6,049 0021 $10,156 Authorizations 6 to 10 0014 3,157 0018 4,735 0022 7,891 Authorizations 11 to 50 0015 2,233 0019 3,350 0023 5,583 Authorizations 51 or more 0016 1,349 0020 2,024 0024 3,373 Authorizations
Contact your sales channel for Support Line pricing information.
Customer Financing: IBM Global Financing offers attractive financing to credit-qualified commercial and government customers and Business Partners in more than 40 countries around the world. IBM Global Financing is provided by the IBM Credit Corporation in the United States. Offerings, rates, terms, and availability may vary by country. Contact your local IBM Global Financing organization. Country organizations are listed on the Web at: