License Information documents

Repository for licenses under the IPLA family

Previous


A Concurrent Session is a) a logical connection made between the Program (residing on a single Server) and a Client Device and b) except as indicated below, each logical connection made between an instance of the Administration Console component of a Program and an IDS instance of a Program or any separately acquired IDS V11.50 program. Each such connection is counted as a Concurrent Session whether or not it is actually in use and regardless of the duration of the connection and/or period(s) of activity. If an individual end user establishes multiple connections, each one is counted as a separate Concurrent Session, even if they share a common physical pathway. From the day You began using the Program, the highest number of connections ever established at any time for each copy (i.e., instance) of the Program on each Server will be counted for purposes of determining the total Concurrent Session entitlements required. You must acquire entitlements for the greatest number of logical connections ever established at any time for all Program instances on each Server, including (except as indicated below) each logical connection made between an instance of the Administration Console component of a Program and an IDS instance of a Program or any separately acquired IDS V11.50 program. See the example below.

The Informix Warehouse Feature includes the Informix Warehouse Administration Console components. The following applies to the Informix Warehouse Feature for Workgroup and Enterprise Editions:

When a SQL Warehouse run request is issued from an instance of the Administration Console, it may create a number of parallel logical connections to an instance of IDS. While each original connection between an Administration Console instance and an IDS instance is counted as a Concurrent Session for which a PoE entitlement must be acquired, additional parallel connections created in conjunction with such SQL Warehouse run requests are not counted as Concurrent Sessions, and no additional PoE entitlements are needed for them.

Each logical connection made between a Client Device and a copy of the Program residing on a Server is counted as a Concurrent Session for which an entitlement is required. For example, if copies of the Program reside on 2 different Servers and a single Client Device is connected to the Program on both Servers, then two (2) Concurrent Sessions have been established and a PoE must be acquired for each of them. As a further example, if four copies of the Program reside on 2 different Servers and a single Client Device is connected to each of the four instances of the Program, then four (4) Concurrent Sessions have been established and a PoE must be acquired for each of them. As a further example, if four copies of the IDS component of a Program reside on 2 different Servers and a single Client Device is connected to each of the four instances of the IDS component, and two (2) Administration Console instances (one on each Server) are connected to each of four (4) instances of the IDS component, then twelve (12) Concurrent Sessions (4 total from the Client Device and 8 total from the Administration Console) have been established and a PoE must be acquired for each of them.

Each logical connection from a Client Device made, directly or indirectly, to this Program (residing on a single Server), through the Intranet (connections from within Your Enterprise) or through the Internet (connections from outside Your Enterprise) is counted as a separate Concurrent Session and a separate entitlement (PoE) must be acquired for such Concurrent Session.

A PoE is required for each Concurrent Session established to access the Program or any Program component either directly or indirectly through any means. An example of "indirect" access would be through a multiplexing program, Client Device, or application server. The number of connections is not reduced by any program, Client Device, or machine, such as a front-end server, application server, or multiplexer, which may be used to connect, manage, and/or concentrate the logical connections.

For example, if You install one or more copies (i.e., instances) of the Program on each of three (3) Servers and from the day You begin using the Program, the greatest number of Concurrent Sessions ever established on the total Program instances (including applicable Administration Console instance to IDS instance connections as specified above) on Server 1 was twelve (12), on Server 2 was seventy (70), and on Server 3 was eighty-nine (89), then You must acquire, and pay for, PoE entitlements for one hundred and seventy-one (171) Concurrent Sessions, even if the number of Your logical connections decreases over time (e.g, logical connections are reduced to the following: Server 1: 12; Server 2: 56; Server 3: 80). Of course, You may subsequently again increase Your total number of logical connections to one hundred-seventy-one (171) without needing to acquire additional Concurrent Session entitlements; provided that you do not increase the total number of logical connections, including logical connections made between an instance of the Administration Console component of a Program and an IDS instance of a Program or any separately acquired IDS V11.50 program on any one of the Servers beyond the highest number of applicable logical connections ever previously established on that Server. In this example, You could again increase the logical connections on Server 2 up to 70, and could increase the logical connections on Server 3 up to 89, without needing to acquire additional Concurrent Session entitlements. To be clear, if You did increase the total number of logical connections on Server 2 up to 70, You could change the combination of such logical connections that were originally acquired without needing to acquire additional entitlements (e.g., if You originally had entitlements for 50 connections between Client Devices and the Program and 20 Administration Console instance connections to IDS instances, then you could instead implement 60 connections between Client Devices and the Program and 10 Administration Console instance connections to IDS instances). However, if You increased the number of logical connections on Server 1 to 25, even though the number of logical connections on Servers 2 and 3 remained at 56 and 80, respectively, You would need to acquire an additional 13 Concurrent Session entitlements for Server 1 (bringing Your total entitlements to one hundred and eighty-four (184)). Concurrent Sessions are not equivalent to concurrent users.

Each batch process being executed at the same time is also considered to be a Concurrent Session.

You must acquire a separate Concurrent Session license entitlement for each Concurrent Session as described above.

Each logical connection from a Client Device made, directly or indirectly, to this Program (residing on a single Server), through the Intranet (connections from within Your Enterprise) or through the Internet (connections from outside Your Enterprise) is counted as a separate Concurrent Session and a separate entitlement (PoE) must be acquired for such Concurrent Session.

The following minimum Concurrent Sessions requirement applies to licenses to the Informix Warehouse Feature for Enterprise Edition V11.50:


The Program must be licensed for, and PoE acquired for, the greater of (a) at least ten (10) Concurrent Sessions per Server on which the Program is installed or (b) the total number of Concurrent Sessions accessing the Program.

The following minimum Concurrent Sessions requirement applies to licenses to Informix Warehouse Feature for Workgroup Edition V11.50:

The Program must be licensed for, and PoE acquired for, the greater of (a) at least ten (10) Concurrent Sessions per Server on which You install the Program; or, (b) the total number of Concurrent Sessions accessing the Program.

1.3) Processor Value Unit (PVU) - If You acquire a Program based on this Charge Metric, then the terms of this Section apply.

"Processor Value Unit (PVU)" is a unit of measure by which the Program can be licensed. PVU entitlements are based on processor technology (defined within the PVU table* by Processor Vendor, Brand, Type and Model Number). IBM defines a processor, for purposes of PVU-based licensing, to be each processor core on a chip. Each software product has a unique price per PVU. To determine the total cost of deploying an individual software product in a specific hardware environment, you must take the following steps:
1. For each processor core in the hardware environment on which the software product is to be licensed, determine the PVU requirement based on its processor technology per the PVU table*.
2. Sum the PVU requirements for all processor cores in the hardware environment.
3. Multiply the software product's price per PVU by the total number of PVUs required as determined in step 2 above.

PVU entitlements are specific to the Program and may not be exchanged, interchanged, or aggregated with PVU entitlements of another software product.

Unless the Program and Your environment are each eligible for sub-capacity licensing according to the IBM International Passport Advantage Agreement Attachment for Sub-Capacity Licensing Terms (the "Attachment")**, You must obtain PVU Proofs of Entitlement (PoEs) for the maximum number of activated*** physical processor cores in the hardware environment made available to or managed by the Program. This is also referred to as "full capacity" licensing.

* PVU licensing is subject to additional details and terms, including the latest PVU requirements table, described at: http://www.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_customers.html

** Passport Advantage sub-capacity licensing terms, conditions and eligibility requirements are described at: http://www-01.ibm.com/software/lotus/passportadvantage/subcaplicensing.html

*** Activated processor cores are physical processor cores that are available for use in a server.

They include processor cores:
1. that are activated (available for use) when the server is shipped by the manufacturer, and
2. that are activated subsequently through activation codes purchased from the server manufacturer by the customer,
in each case regardless of whether the capacity of the processor cores can be or is limited by the customer through virtualization technologies, operating system commands or BIOS settings.

Processor Value Unit (PVU) Sub-Capacity Licensing

This Program is eligible for sub-capacity licensing. In order to take advantage of sub-capacity licensing, Your virtualization environment must meet the eligibility requirements described in the IBM International Passport Advantage Agreement Attachment for Sub-Capacity Licensing Terms (the "Attachment"), and You must accept the terms of the Attachment. You must obtain PVU Proofs of Entitlement (PoEs) for the maximum processor core capacity available to the Program when deployed in an eligible virtualization environment. This is also referred to as sub-capacity or virtualization capacity licensing.

Customers must use the IBM License Metric Tool unless they meet the exceptions described in the Attachment.

Additional details regarding Passport Advantage sub-capacity licensing terms, conditions and eligibility requirements, including the Attachment and IBM License Metric Tool ordering information, are described at: http://www.ibm.com/software/lotus/passportadvantage/subcaplicensing.html

1.4) Limited Use Socket (LU Socket)

The LU Socket charge metric is only available to the Informix Warehouse Feature for Workgroup Edition V11.50 Program.

This Program is licensed on a Limited Use Socket ("LU Socket") basis as follows. You must: (1) acquire one LU Socket entitlement for each Socket on the Server on which the Program is installed; and (2) comply with the resource use restrictions further defined below in this License Information. A "Server" is a single physical computer that executes requested procedures, commands, or applications to one or more user or client devices. Where blade technology is employed, each blade is considered a separate Server. A "Socket" is electronic circuitry that accepts a processor chip. A "processor chip" is electronic circuitry containing one or more processor cores that plugs into a Socket. A "processor core" is a functional unit within a computing device that interprets and executes program instructions, and consists of at least an instruction control unit and one or more arithmetic or logic units.

This Program is eligible for sub-capacity licensing, and You may be permitted to license less than all Sockets on the Server. Sub-capacity licensing terms, conditions and eligibility requirements for LU Socket-charged products are described at: ftp://ftp.software.ibm.com/software/smb/pdfs/LicensingGuide.pdf. If Your use of the Program is not eligible for sub-capacity licensing based on these terms and conditions, You must acquire LU Socket entitlements for all Sockets on the Server on which the Program is installed. The LU Socket entitlements are specific to the Program and may not be exchanged, interchanged, or aggregated with LU Socket entitlements of another software program.

Usage restrictions on Limited Use Socket
If You have acquired the Program based on the LU Socket charge metric, You may install and use this Program subject to all of the following restrictions:
- Each Program instance may use up to a maximum of 16GB of allocated SHMTOTAL memory and may only utilize up to a total of 16 processor cores.
- The physical server may have a maximum capacity of four (4) sockets
- When a Program is used in Hot/Active or Idle Standby configuration (as defined above), You must acquire the number of license entitlements for each copy of the Program on each Hot/Active or Idle Standby Server, using the same charge metric as used for the Program on the corresponding Primary Server. With regard to Hot/Active Standby, when the Program is licensed on the Primary Server on the LU Socket charge metric basis, You must (1) acquire entitlements for the number of Sockets included on the Server on which the Program is installed; and (2) comply with the resource use restrictions specified above, With regard to Idle Standby, when the Program is licensed on the Primary Server on the LU Socket charge metric basis, You must (1) acquire one LU Socket entitlement for each idle Standby Server and (2) comply with the resource use restrictions specified above.

Informix Warehouse Feature V11.50 Additional Level of Use Section

The following apply specifically to the use of the Informix Warehouse Feature Program or component of a Program.


2) You must have valid entitlements covering both the IDS Program and Informix Warehouse Feature for all Servers upon which this Feature is installed

3) Usage Restriction - Informix Warehouse Design Studio Components of the Informix Warehouse Feature

The Informix Warehouse Feature includes the Informix Warehouse Design Studio components. You are authorized to install and use the Informix Warehouse Design Studio components only in association with Your licensed use of Informix Warehouse Feature for the purpose of Informix Warehouse related database development. Your license authorizes You to create the physical schema for the Informix database.



D/N: L-KLET-7R4NZQ
P/N: CT5G6ML

Previous