BMC Atrium Discovery copyright information

Apache License, Version 2.0

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and
distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the
copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other
entities that control, are controlled by, or are under common control
with that entity. For the purposes of this definition, "control" means
(i) the power, direct or indirect, to cause the direction or management
of such entity, whether by contract or otherwise, or (ii) ownership of
fifty percent (50%) or more of the outstanding shares, or (iii)
beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising
permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation source,
and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but not limited
to compiled object code, generated documentation, and conversions to
other media types.

"Work" shall mean the work of authorship, whether in Source or Object
form, made available under the License, as indicated by a copyright
notice that is included in or attached to the work (an example is
provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form,
that is based on (or derived from) the Work and for which the editorial
revisions, annotations, elaborations, or other modifications represent,
as a whole, an original work of authorship. For the purposes of this
License, Derivative Works shall not include works that remain separable
from, or merely link (or bind by name) to the interfaces of, the Work and
Derivative Works thereof.

"Contribution" shall mean any work of authorship, including the original
version of the Work and any modifications or additions to that Work or
Derivative Works thereof, that is intentionally submitted to Licensor for
inclusion in the Work by the copyright owner or by an individual or Legal
Entity authorized to submit on behalf of the copyright owner. For the
purposes of this definition, "submitted" means any form of electronic,
verbal, or written communication sent to the Licensor or its
representatives, including but not limited to communication on electronic
mailing lists, source code control systems, and issue tracking systems
that are managed by, or on behalf of, the Licensor for the purpose of
discussing and improving the Work, but excluding communication that is
conspicuously marked or otherwise designated in writing by the copyright
owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on
behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright
license to reproduce, prepare Derivative Works of, publicly display,
publicly perform, sublicense, and distribute the Work and such Derivative
Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this
License, each Contributor hereby grants to You a perpetual, worldwide,
non-exclusive, no-charge, royalty-free, irrevocable (except as stated in
this section) patent license to make, have made, use, offer to sell,
sell, import, and otherwise transfer the Work, where such license applies
only to those patent claims licensable by such Contributor that are
necessarily infringed by their Contribution(s) alone or by combination of
their Contribution(s) with the Work to which such Contribution(s) was
submitted. If You institute patent litigation against any entity
(including a cross-claim or counterclaim in a lawsuit) alleging that the
Work or a Contribution incorporated within the Work constitutes direct or
contributory patent infringement, then any patent licenses granted to You
under this License for that Work shall terminate as of the date such
litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or
Derivative Works thereof in any medium, with or without modifications,
and in Source or Object form, provided that You meet the following
conditions:

   1. You must give any other recipients of the Work or Derivative Works
a copy of this License; and

   2. You must cause any modified files to carry prominent notices
stating that You changed the files; and

   3. You must retain, in the Source form of any Derivative Works that
You distribute, all copyright, patent, trademark, and attribution notices
from the Source form of the Work, excluding those notices that do not
pertain to any part of the Derivative Works; and

   4. If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must include
a readable copy of the attribution notices contained within such NOTICE
file, excluding those notices that do not pertain to any part of the
Derivative Works, in at least one of the following places: within a
NOTICE text file distributed as part of the Derivative Works; within the
Source form or documentation, if provided along with the Derivative
Works; or, within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents of the
NOTICE file are for informational purposes only and do not modify the
License. You may add Your own attribution notices within Derivative Works
that You distribute, alongside or as an addendum to the NOTICE text from
the Work, provided that such additional attribution notices cannot be
construed as modifying the License.

You may add Your own copyright statement to Your modifications and may
provide additional or different license terms and conditions for use,
reproduction, or distribution of Your modifications, or for any such
Derivative Works as a whole, provided Your use, reproduction, and
distribution of the Work otherwise complies with the conditions stated in
this License.

5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work by You
to the Licensor shall be under the terms and conditions of this License,
without any additional terms or conditions. Notwithstanding the above,
nothing herein shall supersede or modify the terms of any separate
license agreement you may have executed with Licensor regarding such
Contributions.

6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to
in writing, Licensor provides the Work (and each Contributor provides its
Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF
ANY KIND, either express or implied, including, without limitation, any
warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or
FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for
determining the appropriateness of using or redistributing the Work and
assume any risks associated with Your exercise of permissions under this
License.

8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise, unless
required by applicable law (such as deliberate and grossly negligent
acts) or agreed to in writing, shall any Contributor be liable to You for
damages, including any direct, indirect, special, incidental, or
consequential damages of any character arising as a result of this
License or out of the use or inability to use the Work (including but not
limited to damages for loss of goodwill, work stoppage, computer failure
or malfunction, or any and all other commercial damages or losses), even
if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the
Work or Derivative Works thereof, You may choose to offer, and charge a
fee for, acceptance of support, warranty, indemnity, or other liability
obligations and/or rights consistent with this License. However, in
accepting such obligations, You may act only on Your own behalf and on
Your sole responsibility, not on behalf of any other Contributor, and
only if You agree to indemnify, defend, and hold each Contributor
harmless for any liability incurred by, or claims asserted against, such
Contributor by reason of your accepting any such warranty or additional
liability.

END OF TERMS AND CONDITIONS 

END USER LICENSE AGREEMENT

BY OPENING THE PACKAGE, INSTALLING, PRESSING "AGREE" OR "YES" OR USING
THE PRODUCT, THE ENTITY OR INDIVIDUAL ENTERING INTO THIS AGREEMENT
AGREES TO BE BOUND BY THE FOLLOWING TERMS. IF YOU DO NOT AGREE WITH ANY
OF THESE TERMS, DO NOT INSTALL OR USE THE PRODUCT, PROMPTLY RETURN THE
PRODUCT TO BMC OR YOUR BMC RESELLER, AND IF YOU ACQUIRED THE LICENSE
WITHIN 15 DAYS OF THE DATE OF YOUR ORDER CONTACT BMC OR YOUR BMC
RESELLER FOR A REFUND OF LICENSE FEES PAID. IF YOU REJECT THIS
AGREEMENT, YOU WILL NOT ACQUIRE ANY LICENSE TO USE THE PRODUCT.

This Agreement ("Agreement") is between the entity or individual
entering into this Agreement ("Customer") and the BMC Entity for the
applicable Territory as described in Section 19 ("BMC"). In addition to
the restrictions imposed under this Agreement, any other usage
restrictions contained in the Product installation instructions or
release notes shall apply to your use of the Product.

Territory:  The country where Customer acquired the license.

1.     GENERAL DEFINITIONS.
"Affiliate" is an entity that controls, is controlled by or shares
common control with BMC or Customer, where such control arises from
either (a) a direct or indirect ownership interest of more than 50% or
(b) the power to direct or cause the direction of the management and
policies, whether through the ownership of voting stock by contract, or
otherwise, equal to that provided by a direct or indirect ownership of
more than 50%.
"Documentation" means the technical publications relating to the
software, such as release notes, reference, user, installation, systems
administrator and technical guidelines, included with the Product.
"Licensed Capacity" is the amount of each Product licensed as
established in the Order.
"Order" is an agreed written or electronic document, subject to the
terms of this Agreement that identifies the Products to be licensed and
their Licensed Capacity and/or the Support to be purchased and the fees
to be paid.
"Product" is the object code of the software and all accompanying
Documentation delivered to Customer, including all items delivered by
BMC to Customer under Support.
"Support" is the support services program as further specified in this
Agreement.

2.     SCOPE. Licenses are granted, and Support is obtained, solely by
execution of Orders. Each Order is deemed to be a discrete contract,
separate from each other Order, unless expressly stated otherwise
therein, and in the event of a direct conflict between any Order and
the terms of this Agreement, the terms of the Order will control only
if the Order is executed by an authorized representative of each party.
Orders may be entered under this Agreement by and between (a) BMC or an
Affiliate of BMC; and (b) the Customer or an Affiliate of Customer.
With respect to an Order, the terms "BMC" and "Customer" as used in
this Agreement will be deemed to refer to the entities that execute
that Order, the Order will be considered a two party agreement between
such entities, and BMC will separately invoice the Customer named in
the Order for the associated License fees and Support fees. Neither
execution of this Agreement, nor anything contained herein, shall
obligate either party to enter into any Orders. In the event an Order
is proposed by BMC and is deemed to constitute an offer, then
acceptance of such offer is limited to its terms. In the event Customer
proposes an Order by submitting a purchase order, then regardless of
whether BMC acknowledges, accepts or fully or partially performs under
such purchase order, BMC OBJECTS to any additional or different terms
in the purchase order, other than those that establish Product, price
and Licensed Capacity in accordance with this Agreement.

3.     LICENSE. Subject to the terms, conditions, payment requirements
and restrictions set forth in this Agreement, BMC grants Customer a
non-exclusive, non-transferable, non-sub-licensable perpetual (unless a
non-perpetual license is provided on an Order) license, as specified in
the relevant Order, to exercise the following rights  to the Product up
to the Licensed Capacity:  (a) copy the Product for the purpose of
installing it on Customer's owned or leased hardware at a facility
owned or controlled by Customer in the Territory; (b) operate solely
for  Customer's and its Affiliates own internal Customer's business
operations; and (c) make one copy of the Product for archival purposes
only (collectively a "License").  Affiliates may use and access the
Products and Support under the terms of this Agreement, and Customer is
responsible for its Affiliates compliance with the terms of this
Agreement.

4.     RESTRICTIONS. Customer will not:  (a) copy, operate or use any
Product in excess of the applicable Licensed Capacity; (b) modify,
delete or remove any ownership, title, trademark, patent or copyright
notices ("Identification") from any Product; (c) copy any Product or
any portion of any Product without reproducing all Identification on
each copy or partial copy;  (d)  disassemble, reverse engineer,
decompile or otherwise attempt to derive any Product source code from
object code, except to the extent expressly permitted by applicable law
despite this limitation without possibility of contractual waiver; (e)
distribute, rent, lease, sublicense or provide the Product to any third
party or use it in a service bureau, outsourcing environment, or for
the processing of third party data; (f) provide a third party with the
results of any functional evaluation, or performance tests, without
BMC's prior written approval; (g) attempt to disable or circumvent any
of the licensing mechanisms within the Product; or (h) violate any
other usage restrictions contained in the Documentation.

5.     PRODUCT PERFORMANCE WARRANTY. BMC warrants that (a) the Product
will perform in substantial accordance with its Documentation for a
period of one year from the date of the first Order, (b)  BMC has used
commercially reasonable efforts consistent with industry standards to
scan for and remove software viruses, and (c) other than passwords that
may be required for the operation of the Product, BMC has not inserted
any code that is not addressed in the Documentation and that is
designed to delete, interfere with or disable the normal operation the
Products in accordance with the License. This warranty will not apply
to any problems caused by hardware, Computers, or software other than
the Product, or misuse of the Product use of the Product other than as
provided by the applicable License,  modification of the Product, or
claims made either outside the warranty period or not in compliance
with the notice and access requirements set forth below.  No warranty
is provided for additional Licensed Capacity, Product provided pursuant
to Support or Product provided pursuant to Section 11.

6.     LIMITED REMEDIES. BMC's entire liability, and Customer's
exclusive remedy, for breach of the above warranty is limited to:
BMC's use of commercially reasonable efforts to have the Product
perform in substantial accordance with its Documentation,  or
replacement of the non-conforming Product within a reasonable period of
time, or if BMC cannot have the Product perform in substantial
accordance with its Documentation  replace the  Product within such
time period, then BMC will refund the amount paid by Customer for the
License for that Product. Customer's rights and BMC's obligations in
this section are conditioned upon Customer's providing BMC during the
warranty period (a) full cooperation and access to the Product in
resolving any claim; and (b) written notice addressed to the BMC Legal
Department that includes notice of the claim, a complete description of
the alleged defects sufficient to permit their reproduction in BMC's
development or support environment, and a specific reference to the
Documentation to which such alleged defects are contrary.

7.     DISCLAIMER OF WARRANTIES. EXCEPT FOR THE EXPRESS WARRANTIES IN
THIS AGREEMENT, THE PRODUCT IS PROVIDED WITH NO OTHER WARRANTIES
WHATSOEVER, AND BMC, ITS AFFILIATES AND LICENSORS DISCLAIM ALL OTHER
WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND
NON-INFRINGEMENT. BMC DOES NOT WARRANT THAT THE OPERATION OF THE
PRODUCT WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT ALL DEFECTS CAN BE
CORRECTED.

8.     PAYMENTS AND DELIVERY. Customer will pay each License fee
and/or Support fee upon receipt of invoice.  Customer will pay, or
reimburse, BMC or when required by law the appropriate governmental
agency  for taxes of any kind, including sales, use, VAT, excise,
customs duties, withholding, property, and other similar taxes (other
than taxes based on BMC's net income) imposed in connection with the
License and/or the Support fees which are exclusive of these taxes. For
Products that are delivered electronically, upon request from BMC,
Customer agrees to provide BMC with Documentation supporting that the
designated Product was received electronically. If Customer accepts any
Product in a non-electronic format, there may be an additional charge
and it is the sole responsibility of Customer to bear any sales/use tax
obligation, penalties, and interest. The unpaid balance of each late
payment bears interest at a rate equal to the lesser of 1% per month or
the maximum amount permitted by law. All Products are licensed FCA
("Free Carrier" as per Incoterms 2000) shipping point. The Products are
accepted on the date BMC delivers the Product to the Customer either
physically or by providing access codes for electronic download,
whichever occurs first, however, such acceptance will not affect the
Product Performance Warranty provided in this Agreement.

9.     PROPRIETARY RIGHTS AND CONFIDENTIALITY. (a) BMC, its Affiliates
or licensors retain all right, title and interest to the Product,
Support and all related intellectual property and proprietary rights.
The Product and all third party software provided with the Product are
protected by applicable copyright, trade secret, industrial and other
intellectual property laws. Customer may not remove any product
identification, copyright, trademark or other notice from the Product.
BMC reserves any rights not expressly granted to Customer in this
Agreement. (b)  "Confidential Information" means all proprietary or
confidential information that is disclosed to the recipient
("Recipient") by the discloser ("Discloser"), and includes, among other
things (i) any and all information relating Discloser  financial
information, customers, employees, products or  services, including,
without limitation, software code, flow charts, techniques,
specifications, development and marketing plans, strategies, forecasts,
and proposal related documents and responses; (ii) as to BMC, and its
licensors, the Product and any third party software provided with the
Product; and (iii) the terms of this Agreement, including without
limitation, Product pricing information. Confidential Information does
not include information that Recipient can show: (a) was rightfully in
Recipient's possession without any obligation of confidentiality before
receipt from the Discloser; (b) is or becomes a matter of public
knowledge through no fault of Recipient; (c) is rightfully received by
Recipient from a third party without violation of a duty of
confidentiality; or (d) is independently developed by or for Recipient.
Recipient may not disclose Confidential Information of Discloser to any
third party or use the Confidential Information in violation of this
Agreement. The Recipient (i) will exercise the same degree of care and
protection with respect to the Confidential Information of the
Discloser that it exercises with respect to its own Confidential
Information and (ii) will not, either directly or indirectly, disclose,
copy, distribute, republish, or allow any third party to have access to
any Confidential Information of the Discloser. Notwithstanding the
foregoing, Recipient may disclose Discloser's Confidential Information
to Recipient's employees and agents who have the need to know provided
that such employees and agents have legal obligations of
confidentiality substantially the same (and in no case less protective)
as the provisions of this Agreement. (c)  Notification Obligation. If
the Recipient becomes aware of any unauthorized use or disclosure of
Discloser's Confidential Information, then Recipient will promptly and
fully notify the Discloser of all facts known to it concerning such
unauthorized use or disclosure. In addition, if the Recipient or any of
its employees or agents are required (by oral questions,
interrogatories, requests for information, or documents in legal
proceedings, subpoena, civil investigative demand, or other similar
process) to disclose any of Discloser's Confidential Information, the
Recipient will not disclose the Discloser's Confidential Information
without providing the Discloser with commercially reasonable advance
prior written notice to allow Discloser to seek a protective order or
other appropriate remedy or to waive compliance with this provision. In
any event, the Recipient will exercise its commercially reasonable
efforts to preserve the confidentiality of the Discloser's Confidential
Information, including, without limitation, cooperating with Discloser
to obtain an appropriate protective order or other reliable assurance
that confidential treatment will be accorded to the Confidential
Information.

10.     DISCLAIMER OF DAMAGES; LIMITS ON LIABILITY. EXCEPT FOR
VIOLATIONS OF LICENSE (SECTION 3), LICENSE RESTRICTIONS (SECTION 4),
PROPRIETARY RIGHTS AND CONFIDENTIALITY (SECTION 9) AND FOR INFRINGEMENT
CLAIMS (SECTION 12), NEITHER PARTY, ITS AFFILIATES OR BMC'S LICENSORS
ARE LIABLE FOR (A) ANY SPECIAL, INDIRECT, INCIDENTAL, PUNITIVE OR
CONSEQUENTIAL DAMAGES RELATING TO OR ARISING OUT OF THIS AGREEMENT,
SUPPORT, THE PRODUCT OR ANY THIRD PARTY CODE OR SOFTWARE PROVIDED WITH
THE PRODUCT (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, LOST COMPUTER
USAGE TIME, AND DAMAGE TO, OR LOSS OF USE OF DATA), EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES, AND IRRESPECTIVE OF NEGLIGENCE OF A
PARTY OR WHETHER SUCH DAMAGES RESULT FROM A CLAIM ARISING UNDER TORT OR
CONTRACT LAW OR (B) DAMAGES OF ANY KIND IN AN AMOUNT GREATER THAN THE
AMOUNT OF ACTUAL, DIRECT DAMAGES UP TO THE GREATER OF THE AMOUNT PAID
AND PAYABLE BY CUSTOMER FOR THE LICENSE TO THE APPLICABLE PRODUCT
GIVING RISE TO SUCH DAMAGES.

11.     TRIAL LICENSE. BMC may determine, in its sole discretion, to
make products available to Customer without an Order and without charge
Such products are deemed to be "Products" pursuant to this Agreement
except that (a) they are provided to Customer solely so that Customer
may evaluate internally whether to  acquire a license to the products
for a fee, (b) the license term for such products is thirty (30) days;
(c) the Products are provided "AS IS" and without any warranty or
support, and (d) the products cannot be put into productive use or
included as part of Customer's business processes in any manner, unless
or until they are expressly licensed and paid for under an Order. BMC
may terminate all of Customer's rights and licenses to these products
for BMC's convenience upon notice to Customer.

12.     INFRINGEMENT CLAIMS. If a third party asserts a claim against
Customer asserting that Customer's use of a Product in accordance with
this Agreement violates that third-party's patent, trade secret or
copyright rights ("Infringement Claim"), then BMC will, at its own
expense: (a) defend or settle the Infringement Claim; and (b) indemnify
Customer for any damages finally awarded against Customer based on
infringement by the Product. BMC's obligations under this Section will
not apply if: (a) BMC's legal department does not receive prompt,
detailed written notice of the Infringement Claim from Customer, (b)
BMC is not able to retain sole control of the defense of the
Infringement Claim and all negotiations for its settlement or
compromise, (c) BMC does not receive all reasonable assistance, or (d)
the Infringement Claim is based on (i) the use of Product in
combination with products not approved by BMC in the Product's
Documentation, (ii) the failure of Customer to use any updates to such
Product within a reasonable time after such updates are made available
to Customer, or (iii) the failure of Customer to use the Product as
permitted by the Order and in accordance with the Documentation. BMC
will not bind Customer to a monetary obligation in a settlement or
compromise, or make an admission on behalf of Customer, without
obtaining Customer's prior consent. If BMC determines in BMC's
reasonable discretion that use of the Product should be stopped because
of an Infringement Claim or potential Infringement Claim, if a court of
competent jurisdiction enjoins Customer from using a Product as a
result of an Infringement Claim and BMC is unable to have such
injunction stayed or overturned, or if BMC settles an Infringement
Claim on terms that would require Customer to stop using the Product,
then BMC will, at its expense and election: (a) modify or replace the
Product, (b) procure the right to continue using the Product, or (c) if
in BMC's reasonable judgment, neither (a) or (b) is commercially
reasonable, terminate Customer's License to the Product and (i) for any
perpetual licenses, issue a refund based upon the applicable license
fees paid, prorated over 48 months from the date of the Order under
which the Products were initially licensed; and (ii) for any
non-perpetual licenses, release Customer from its obligation to make
future payments for the Product or issue a pro rata refund for any fees
paid in advance. This Section contains Customer's exclusive remedies
and BMC's sole liability for Infringement Claims.

13.     TERMINATION. Upon thirty days advance written notice, either
party may terminate this Agreement for its convenience on a prospective
basis; however, such termination will have no effect on Orders executed
by the parties prior to its effective date and such Orders will remain
in full force and effect under the terms of this Agreement. BMC may:
(i) terminate an Order and the Licenses to the Products on that Order
if Customer fails to pay any applicable fees due under that Order
within 30 days after receipt of written notice from BMC of non-payment;
 (ii) terminate any or all Orders, Licenses to the Products and/or this
Agreement, without notice or cure period, if Customer violates the
intellectual property rights of BMC, its Affiliates or licensors, or
uses the Products outside of the scope of the applicable Licenses; or
(iii) terminate all Licenses and this Agreement in whole or in part if
Customer commits any other material breach of this Agreement and fails
to correct the breach within 30 days after BMC notifies Customer in
writing of the breach. Upon any termination of a License, Customer will
immediately uninstall and stop using the relevant Product, and upon
BMC's request, Customer will immediately return such Product to BMC,
together with all related Documentation and copies, or certify its
destruction in writing. Neither party is liable for its failure to
perform any obligation under this Agreement, other than a payment
obligation, during any period in which performance is delayed by
circumstances beyond that party's reasonable control.

14.     AUDIT. If requested by BMC not more than once a year, Customer
agrees to deliver to BMC periodic product usage reports generated from
specific products (when available) or written reports, whether
generated manually or electronically, specifying Customer's use of the
Product.  Additionally, if requested by BMC not more than once a year,
Customer agrees to allow BMC to perform an audit at Customer's
facilities during normal business hours to ensure compliance with the
terms of this Agreement. Customer agrees to cooperate during any such
audit and to provide reasonable access to its information and systems.
If an audit reveals that Customer has exceeded the Licensed Capacity
for a Product, Customer agrees to pay the applicable fees for
additional capacity. If the understated capacity exceeds 5% of the
Licensed Capacity of the applicable Product, then Customer agrees to
also pay BMC's reasonable costs of conducting the audit.

15.     EXPORT CONTROLS. By using the Technology (as this term is
defined below), Customer acknowledges that it is responsible for
complying with the applicable laws and regulations of the United States
and all other relevant countries relating to exports and re-exports.
Customer agrees that it will not download, access, license or otherwise
export or re-export, directly or indirectly, any software code
(delivered as a BMC Product, through support/maintenance, or through
other services), any technical publications relating to the software
code, such as release notes, reference, user, installation, systems
administrator and technical guidelines, or services (collectively,
"Technology") in violation of any such laws and regulations, including
regulations prohibiting export to certain restricted countries
("Restricted Countries"), or without any written governmental
authorization required by such applicable laws. The list of Restricted
Countries can and does change from time to time. It currently includes
Cuba, Iran, North Korea, Sudan and Syria. In particular, but without
limitation, the Technology may not be downloaded, licensed, transferred
or otherwise exported or re-exported, directly or indirectly, including
via remote access (a) into a Restricted Country or to a national or
resident of a Restricted Country; (b) to anyone on the U.S. Treasury
Department's list of Specially Designated Nationals or Other Blocked
Persons, the U.S. Commerce Department's Denied Parties List, Entity
List, or Unverified List; or (c) to or for any proliferation-related
(nuclear weapons, missile technology, or chemical/biological weapons)
end use. By downloading, licensing and/or using the Technology,
Customer represents and warrants that (w) it is not located in, under
the control of, acting on behalf of, or a national or resident of any
Restricted Country; (x) Customer is not on any list in (b) above; (y)
Customer is not involved in any end use listed in (c) above; and (z) no
U.S. federal agency has suspended, revoked, or denied its export
privileges. Customer agrees that all rights to use the Technology are
granted on the condition that such rights are forfeited if it fails to
comply with these terms.

EC No. 428/2009 sets up a Community regime for control of exports of
dual-use items and technology, and it is declared that this Technology
is intended for civil purposes only. Therefore, Customer agrees not to
license, download or transfer, directly or indirectly any Technology
controlled by it to any military entity or to any other entity for
military purposes, including any State Security Forces pursuant to this
Agreement, nor to knowingly transfer any Technology to end-users for
use in connection with chemical, biological or nuclear weapons or
missiles capable of delivering such weapons. Customer also agrees, (a)
not to export or re-export any Technology to an entity that is based in
China and describe themselves as "Institute(s)" or "Academy(ies)"; or
(b) not to knowingly export or re-export any Technology to any country
that is subject to European Union, United Nations or Organizations for
Security and Co-operation in Europe sanctions without first obtaining a
validated license.

16.     GOVERNING LAW. This Agreement is governed by the substantive
laws in force, without regard to conflict of laws principles:  (a) in
the State of Texas, if you acquired the License in the United States,
Puerto Rico, or any country in Central or South America; (b) in the
Province of Ontario, if you acquired the License in Canada (subsections
(a) and (b) collectively referred to as the "Americas Region"); (c) in
Singapore, if you acquired the License in Japan, South Korea, Peoples
Republic of China, Special Administrative Regions of Hong Kong or
Macau, Taiwan, Philippines, Indonesia, Malaysia, Myanmar, Singapore,
Brunei, Vietnam, Cambodia, Laos, Thailand, India, Pakistan, Australia,
New Zealand, Papua New Guinea or any of the pacific island states
(collectively, "Asia Pacific Region"); or (d) in the Netherlands, if
you acquired the License in any other country not described above. The
United Nations Convention on Contracts for the International Sale of
Goods is specifically disclaimed in its entirety.

17.     ARBITRATION. ANY DISPUTE BETWEEN CUSTOMER AND BMC ARISING OUT
OF THIS AGREEMENT OR THE BREACH OR ALLEGED BREACH, SHALL BE DETERMINED
BY BINDING ARBITRATION CONDUCTED IN ENGLISH. IF THE DISPUTE IS
INITIATED IN THE AMERICAS REGION, THE ARBITRATION SHALL BE HELD IN NEW
YORK, U.S.A., UNDER THE CURRENT COMMERCIAL OR INTERNATIONAL, AS
APPLICABLE, RULES OF THE AMERICAN ARBITRATION ASSOCIATION. IF THE
DISPUTE IS INITIATED IN A COUNTRY IN THE ASIA PACIFIC REGION, THE
ARBITRATION SHALL BE HELD IN SINGAPORE, SINGAPORE UNDER THE CURRENT
UNCITRAL ARBITRATION RULES. IF THE DISPUTE IS INITIATED IN A COUNTRY
OUTSIDE OF THE AMERICAS REGION OR ASIA PACIFIC REGION, THE ARBITRATION
SHALL BE HELD IN AMSTERDAM, NETHERLANDS UNDER THE CURRENT UNCITRAL
ARBITRATION RULES. THE COSTS OF THE ARBITRATION SHALL BE BORNE EQUALLY
PENDING THE ARBITRATOR'S AWARD. THE AWARD RENDERED SHALL BE FINAL AND
BINDING UPON THE PARTIES AND SHALL NOT BE SUBJECT TO APPEAL TO ANY
COURT, AND MAY BE ENFORCED IN ANY COURT OF COMPETENT JURISDICTION.
NOTHING IN THIS AGREEMENT SHALL BE DEEMED AS PREVENTING EITHER PARTY
FROM SEEKING INJUNCTIVE RELIEF FROM ANY COURT HAVING JURISDICTION OVER
THE PARTIES AND THE SUBJECT MATTER OF THE DISPUTE AS NECESSARY TO
PROTECT EITHER PARTY'S CONFIDENTIAL INFORMATION, OWNERSHIP, OR ANY
OTHER PROPRIETARY RIGHTS. ALL ARBITRATION PROCEEDINGS SHALL BE
CONDUCTED IN CONFIDENCE, AND THE PARTY PREVAILING IN ARBITRATION SHALL
BE ENTITLED TO RECOVER ITS REASONABLE ATTORNEYS' FEES AND NECESSARY
COSTS INCURRED RELATED THERETO FROM THE OTHER PARTY.

18.     U.S. FEDERAL ACQUISITIONS. This Article applies to all 
acquisitions of the commercial Product subject to this Agreement by or
on behalf of the federal government, or by any prime contractor or
subcontractor (at any tier) under any contract, grant, cooperative
agreement or other activity with the federal government. By accepting
delivery of the Product, the government hereby agrees that the Product
qualifies as "commercial" within the meaning of the acquisition
regulation(s) applicable to this procurement. The terms and conditions
of this Agreement shall pertain to the government's use and disclosure
of the Product, and shall supersede any conflicting contractual terms
and conditions. If the license granted by this Agreement fails to meet
the government's needs or is inconsistent in any respect with Federal
law, the government agrees to return the Product, unused, to BMC. The
following additional statement applies only to acquisitions governed by
DFARS Subpart 227.4 (October 1988):  "Restricted Rights - Use,
duplication and disclosure by the Government is subject to restrictions
as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data
and Computer Software clause at DFARS 252.227-7013 (Oct. 1988)."

19.     BMC ENTITIES. The following licensing entities apply to this
Agreement:

Territory          Licensing Entity           Address of Licensing Entity

United States      BMC Software, Inc.         2101 CityWest Boulevard
and Latin America                             Houston,  Texas 77042
South (not a
specified Central
or South America
country below)

Canada             BMC Software Canada Inc.   50 Minthorn Boulevard,
                                              Suite 200
                                              Markham, Ontario L3T 7X8
                                              Canada

EMEA (Europe,      BMC Software               Boeing Avenue 245,
Middle East        Distribution B.V.          1119 PE Schiphol Rijk,
and Africa)                                   The Netherlands

Brazil             BMC Software do            Rua Leopoldo Couto de
                   Brasil Ltda.               Magalhães Jr, 758 - 14º andar,
                                              São Paulo - SP - Brazil

Mexico             BMC Software Distribution  Torre Esmeralda II Blvd.
                   de México, S.A. de C.V.    Manuel Avila, Camacho #36,
                                              Piso 23 Lomas de Chapultepec,
                                              CP11000, México D.F.

Argentina          BMC Software de            Ing. Butty 220 - Piso 14,
                   Argentina S.A.             Buenos Aires,
                                              Republica Argentina,
                                              C1001AFB

S.E.A (Southeast   BMC Software Asia Pacific  600 North Bridge Road,
Asia), Australia,  Pte Ltd                    #20-01/10 Parkview Square,
New Zealand,                                  Singapore 188778
Hong Kong, Taiwan

China              BMC Software (China)       Suite 501-504, Level 5,
                   Limited                    Tower W1, The Towers,
                                              Oriental Plaza,
                                              #1 East Chang An Ave.,
                                              Dong Cheng,
                                              Beijing 100738, China

Japan              BMC Software K.K.          Harmony Tower 24th Floor,
                                              1-32-2 Honcho, Nakano-ku,
                                              Tokyo, 164-8721

Korea              BMC Software Korea Ltd     33rd Fl.,
                                              ASEM Tower
                                              World Trade Center,
                                              159-1, Samsung-dong,
                                              Kangnam-ku,
                                              Seoul 135-798


20.     ASSIGNMENT AND TRANSFERS. Customer may not assign or transfer a
Product separate from the applicable Agreement and License, and may not
assign or transfer an Agreement or a License, except in the event of a
merger with or into, or a transfer of all or substantially all of
Customer's assets to, a third party who assumes all of Customer's
liabilities and obligations under the Agreement and License, and
expressly agrees in writing to be bound by and comply with all of the
terms of the Agreement and License. Except as specifically authorized
by applicable law, any attempt to assign or transfer an Agreement or
License in violation of this provision will be null and void and be
treated as a violation of BMC's intellectual property rights or use
outside the scope of the License.

21.     FORCE MAJEURE. Any delay or failure of any party to perform any
obligation under this Agreement caused by governmental restrictions,
labor disputes, storms or natural disasters, emergency, or other causes
beyond the reasonable control of the party, will not be deemed a breach
of this Agreement. This provision does not apply to the payment of
monies or any breach of Section 9.

22.     DATA PROTECTION. (a) Customer acknowledges that BMC neither
requires nor needs Customer to (i) send BMC any personal data collected
by Customer ("Customer Collected Data") or (ii) give BMC access to any
Customer Collected Data. Consequently, Customer remains responsible for
either filtering, making anonymous, encrypting such Customer Collected
Data or for having proper procedures in place to prevent Customer
Collected Data from being sent to or accessed by BMC. (b) In the course
of normal business, BMC may collect and process personal information
related to the Customer (mainly contact and related information) in
order to perform its obligations under this Agreement and/or under an
Order, such information being referred to hereinafter as "Customer
Contact Information". BMC undertakes to comply with all the relevant
data protection legislation and/or regulations where the Customer
Contact Information is to be processed. BMC shall in particular: (i)
allow Customer to access, modify, correct or erase Customer Contact
Information when necessary; (ii) take reasonable technical and
organizational security measures to maintain the confidentiality and
integrity of Customer Contact Information and to prevent its
unauthorized access, use, or disclosure; (iii) refrain from
transferring any Customer Contact Information to any third party
without obtaining the express consent of the person to whom Customer
Contact Information relates to, and (iv) refrain from using Customer
Contact Information for any other purpose than performing its
obligations under this Agreement and/or any Order.

23.     MISCELLANEOUS TERMS. A waiver by a party of any breach of any
term of this Agreement will not be construed as a waiver of any
continuing or succeeding breach. Should any term of this Agreement be
invalid or unenforceable, the remaining terms will remain in effect.
The parties acknowledge they have read this Agreement and agree that it
is the complete and exclusive statement of the agreement and supersedes
any prior or contemporaneous negotiations or agreements, between the
parties relating to the subject matter of this Agreement. There are no
representations, promises, warranties, covenants, or undertakings
between the parties other than those expressly set forth in this
Agreement. This Agreement may not be modified or rescinded except in
writing signed by both parties. The prevailing party in any litigation
is entitled to recover its attorney's fees and costs from the other
party. Customer agrees that BMC and its affiliates may refer to
Customer as a customer of BMC, both internally and in externally
published media. The BMC Products may contain both open source code
("Open Source") and proprietary third party code (together "TPS") which
is delivered to Customer as part of the Product and may not be taken
out of the Product or used separately from the Product ("Embedded
TPS"). Embedded TPS is included in the defined term "Product" and is
covered by all of the terms of the Agreement, including but not limited
to, the warranty and indemnification responsibilities of BMC. Some
terms related to Embedded TPS may be included in the Documentation due
to requirements of the TPS licensor, however these terms will not (1)
impose any additional restrictions on Customer's use of the Product, or
(2) negate or amend the BMC responsibilities with respect to the
Embedded TPS in the Product (or the Product itself). If the Open Source
is also distributed separately by BMC pursuant to requirements by the
owner of the Open Source, then Customer may separately use the Open
Source and such use will be subject to the separate license agreement
that accompanies the Open Source and not the BMC Agreement.

24.     SUPPORT. Customer may acquire BMC support services ("Support")
on an Order. Once Support is acquired for a Product, Customer is
automatically enrolled in Support on an annual basis for all Licensed
Capacity of that Product, unless either party terminates Support on all
Licensed Capacity of a Product upon at least 30 days written notice
prior to the next Support anniversary date. The annual fee for Support
will be agreed upon at the time of each Order. For a description of
Support go to www.bmc.com/support/review-policies. BMC may change its
Support terms, to be effective upon Customer's support anniversary
date. BMC reserves the right to discontinue Support for a Product where
BMC generally discontinues such services to all licensees of that
Product. If Customer terminates Support and then re-enrolls in Support,
BMC may charge Customer a reinstatement fee.

25.     ADDITIONAL TERMS. The following additional terms are
incorporated into this Agreement.

a. DEFINITIONS. Terms set forth below have the indicated meaning
regardless of whether they are capitalized.
"Client" means a third party whose data is processed by Customer and is
only permitted if Customer is an authorized BMC service provider.
"Cloud Environment" means a shared pool of configurable computing
resources (e.g., networks, servers, storage, applications and services)
managed so they behave as if they were one computer.
"Cloud Services" means the dynamic provisioning of IT resources as a
service, where typically the Cloud infrastructure is shared across
multiple tenants, and tenants are billed on a utility/subscription
basis for what they use. Examples of Cloud Services include
Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and
Software as a Service (SaaS).
"Cloud Service Provider" is an entity that provides Cloud Services to
Clients under agreements pursuant to transactions for which the Cloud
Service Provider is compensated.
"Computer" or "Server" has the meaning generally given within the
computer industry, which is a single machine, whether a central
processing unit, such as a mainframe machine, or a distributed systems
machine, such as a Unix or Intel based server. A mainframe machine
would be an individual mainframe computer having single or multiple
processors or engines. For purposes of distributed systems machines, a
Computer or Server may be physical or virtual.
"Documentation" means the technical publications relating to the
software, such as release notes, reference, user, installation, systems
administrator and technical guidelines, included with the Product.
"Enterprise" is the environment consisting of all hardware owned or
leased by a Customer, or by a Client respectively, in the Territory.

b. LICENSE RESTRICTIONS. The following restrictions apply to certain
Products.
BMC AppSight Products:
* BMC AppSight Initial Platform ("AppSight System") may only be used to
  support a Customer's own applications according to the AppSight System
  configuration licensed. For this purpose, Customer's "own" applications
  are those of which Customer is the ultimate beneficiary or applications
  developed by Customer as an independent software vendor. Each AppSight
  System may only be used with the platform designated on the Product
  Table (Windows/.Net or J2EE) unless a BMC AppSight Additional Platform
  is licensed for that AppSight System which enables the AppSight System
  to be used with an additional platform. Each AppSight System may only
  be used for the Workflow designated on the Product Order Form unless a
  BMC AppSight Additional Platform is licensed for that AppSight System
  for an additional Workflow.
  o AppSight System-Team Edition may only be used at a designated Site to
    support a designated Application for a designated Workflow.
  o AppSight System - Group Edition may be used at a designated Site to
    support multiple applications of a designated Group for a designated
    Workflow.
  o AppSight System - Division Edition may be used at multiple Sites to
    support multiple applications of a designated Division for a
    designated Workflow.
* BMC AppSight Named User is a license to use the full BMC AppSight
  System. Customer must provide the individual domain ID or email ID for
  each named user. Once designated, the BMC AppSight Named User may only
  be changed if the individual leaves the Customer or the Team, Group or
  Division as applicable. BMC AppSight Named Users may not be transferred
  from one AppSight System to another.
* BMC AppSight QA User is a license to use the AppSight Test Recorder
  module of the AppSight System.
* BMC AppSight Level 1 Viewer is a license to use limited-functions of
  AppSight System that provides a user with the ability to view and
  replay the visual recording of a Black Box log. The AppSight Level 1
  Viewer may be used by the named users provided to BMC.
* BMC AppSight for Citrix Support User is a license to use the AppSight
  System for Citrix application support. Only licensed BMC AppSight for
  Citrix users may use the AppSight System for Citrix support.
* BMC AppSight Connector for Defect/Incident Tracking may only be used
  to interface the AppSight System to Customer's defect/incident tracking
  application.
* BMC Desktop Capture. Customer must provide the individual domain ID
  or email ID for each named user. The BMC Desktop Capture Player may be
  used by licensed named users to play back and view BMC Desktop Capture
  incident recordings. Once designated, a named user may only be changed
  if the individual leaves the Customer.

BMC AppSight and BMC Application Problem Resolution Products:
* License Key. The Product may require a software license key that
  limits usage to that provided under the terms of the Agreement and this
  Product Order Form. Licensee must install and run license manager
  software provided with the Product at no additional cost. All AppSight
  Consoles must be connected to the license manager.
* AppSight Black Box is the agent portion of the AppSight System.. All
  AppSight Systems include unlimited AppSight Black Boxes which may be
  installed on any computers of Customer or Customer's customers.
  Customer may provide Customer's customers the limited right to install
  and to use on behalf of Customer the AppSight Black Boxes (but not any
  other components of the AppSight System) but only for the sole purpose
  of providing information to Customer to support Customer's own software
  applications, and in no event to support Customer's customer's own
  internal software applications.
* Embedded Black Box. Customer may incorporate the AppSight Black Box
  into a Customer application, in which case, in addition to the licenses
  granted above, Customer is hereby granted a worldwide, nonexclusive,
  perpetual license to (a) incorporate the unmodified unaltered object
  code version of the AppSight Black Box into Customer's designated
  application ("Customer Application"); (b) reproduce and distribute the
  AppSight Black Box as incorporated into the Customer Application; and
  (c) to use in unaltered form the BMC trademarks, service marks or
  marketing logos (the "BMC Trademarks") solely to promote the Customer
  Application, provided Customer obtains BMC's prior written approval for
  each new usage. Customer shall ensure that any Customer Application
  incorporating the AppSight Black Box shall be governed by a license
  agreement which is at least as protective of BMC's proprietary rights
  in the AppSight Black Box as of Customer's proprietary rights in the
  Customer Application, but no less protective than this Agreement,
  including rights and restrictions related to end user's right to make
  backup and archival copies. In the event Customer incorporates the
  Black Box into Customer's Application, Customer shall include in the
  startup screen, help and/or the about screens in the Customer
  Application, BMC's logo and the following, "POWERED BY BMC'S APPSIGHT
  BLACK BOX TECHNOLOGY."  Furthermore, Customer shall visually display
  the BMC name and the BMC product names and trademarks in the
  documentation for the Customer Application incorporating the AppSight
  Black Box, on Customer's website and in advertising and promotional
  materials.

BMC Atrium Orchestrator Automation Pack - Device Endpoint License
Add-on:  Restricts license rights to up to five (5) peers in the
orchestration environment; and allows use of the following runbooks
(Continuous Compliance for Network Automation and NetApp Solutions) and
supporting base Adapters only for the Licensed Capacity.

BMC Atrium Orchestrator Automation Pack - Server Endpoint License
Add-on:  Restricts license rights to up to five (5) peers in the
orchestration environment; and allows use of the following runbooks
(Continuous Compliance for Server Automation, Discovery Synch, and
NetApp Solutions) and supporting base Adapters only for the Licensed
Capacity.

BMC Atrium Orchestrator - Adapters License Add-on:  Restricts license
rights to deploy one unique adapter for every unit licensed; also
includes unlimited deployment rights to use Light Weight Activity Peers
in combination with licensed adapters; test and development license are
provided at no additional cost.
- Adapter - a system/interfaces/gateways/connectors used to talk to
  external applications.
- Light Weight Activity Peer - Slave peers/servers that can optionally
  be added to a grid to accommodate network latencies and/or security
  topologies when deployed in combination with adapters; these peers do
  not directly add incremental processing power.

BMC Atrium Orchestrator - Peer License Add-on:  Restricts license
rights to deploy one peer for every unit licensed; a peer can either be
a Configuration Distribution Peer or an Application Peer; test and
development license are provided at no additional cost.
- Application Peer - Server that executes workflows.
- Configuration Distribution Peer - Master application that controls
  all workflows, including load balancing across the grid of Peers.
  BMC BladeLogic Automation Suite - Base License: Includes unlimited use
  of the following BMC Atrium Orchestrator core product components
  including Repository, Access Manger, Grid Manager, Metrics and
  Reporting, Operations Actions Management Modules, and Operations
  Actions Utility Modules. Test and development licenses are provided at
  no additional cost.
  Restricts license rights to use the following BMC Atrium Orchestrator
  product components for configuration of an initial Orchestration
  environment as detailed here: One (1) Configuration Distribution Peer,
  3 Development Studio user licenses, 5 Operator Control Panel user
  licenses, and Application Adapters for BMC products.
- Adapter - a system/interfaces/gateways/connectors used to talk to
  external applications
- Configuration Distribution Peer - Master application that controls
  all workflows, including load balancing across the grid of Peers.
- Development Studio - Graphical workflow authoring tool used to create
  and modify workflows.
- Operator Control Panel - Web-based UI designed for operators to
  monitor workflows in action, launch workflows manually, or view reports
  on workflow actions.

BMC BladeLogic Application Release Automation:  Excludes use of BMC
BladeLogic agent for server compliance, remediation, configuration,
patching, and provisioning tasks.

BMC Application Automation - License Add-on:  Excludes use of BMC
BladeLogic agent for server compliance, remediation, configuration,
patching, and provisioning tasks

BMC Decision Support - Server Automation (5 Viewer, 1 Query License):
Excludes use of Report Authoring module which must be licensed
separately.

BMC Decision Support - Network Automation (5 Viewer/Query Licenses):
Excludes use of Report Authoring module which must be licensed
separately.

BMC Decision Support - Database Automation (5 Viewer/Query Licenses):
Excludes use of Report Authoring module which must be licensed
separately.

BMC BladeLogic Server Automation - Configuration Module:  Excludes use
of BMC BladeLogic agent for server compliance, remediation, and
provisioning tasks.

BMC BladeLogic Server Automation - Provisioning Module: Excludes use of
BMC BladeLogic agent for server configuration, patching, compliance,
and remediation tasks.

BMC Capacity Management for Mainframes: Any BMC Capacity Management for
Mainframes Product and/or any BMC Performance Analyzer for Mainframes,
BMC Performance Predictor for Mainframes, BMC Performance Perceiver for
Mainframes, BMC Performance Analyzer for Mainframe Applications and
other related products that may be released as part of the BMC Capacity
Management for Mainframes must be licensed for all Computer(s) within
the mainframe environment for which the Product or one of its
components will process data or execute functionality on behalf of,
regardless of whether the Product or one of its components is
specifically installed on that Computer.  The Products may be installed
on or moved to any Computer(s) included in the licensed environment.

BMC Capacity Management Products: Any BMC Capacity Management Product,
BMC Capacity Optimization Product, BMC Performance Assurance Product
and/or any other related products that may be released as part of the
BMC Capacity Management solutions for distributed systems environments
are licensed to the Computer(s) for which the Products are initially
assigned and may not be reassigned to another Computer(s) unless the
original Computer(s) has been removed from service. "Removed from
service" or "out of service" is defined as no longer providing support
for a business application or workload. A license is required for all
Computers for which the Product or one of its components executes
functionality, either locally or remotely.

BMC Cloud Service Management - Development Environment for Service
Providers License Add-on ("CSM Dev"):
* The Product may only be used in the Cloud Service Provider's
  Development Sites for the sole purpose of developing or demonstrating
  commercial Cloud Services. The Product may not be used for production
  processing, such as a cloud pilot or cloud production environment for
  Clients or any other third party. Licenses cannot be transferred (i)
  from a Development Site to other environments, or (ii) from a Cloud
  Service Provider to any other third party.
* CSM Dev provides a license to use the BMC Service Cost Management
  solution, excluding access to, and usage of, IT service cost industry
  benchmark data content published by Rubin Systems, Inc.

BMC Cloud Lifecycle Management - Core License Add-on ("CLM Core"):
* The Product may only be used in a Cloud Environment.
* The Product includes the right to use BMC Network Automation for the
  network devices in the Cloud Environment as long as the number of
  supported Network Devices does not exceed the Licensed Capacity.
* The Product includes the right to use BMC Network Automation only in
  order to enable the initial provisioning, on-going network operations,
  and use of the Virtual Data Center feature for Network Devices in the
  Cloud Environment. The Product does not include the right to use BMC
  Network Automation for the management of Network Devices that are not
  in a BMC Network Automation Pod.

BMC Cloud Lifecycle Management - Standard Pack License Add-on ("CLM
Standard"):
* The Product may only be used in a Cloud Environment.
* If Customer is also a Cloud Service Provider then Product cannot be
  used by the Cloud Service Provider for other environments, including
  but not limited to the Cloud Service Provider's internal IT
  environment, or System Integration activities for Clients which are not
  part of Cloud Services. The Product may not be installed on Client
  premises or accessed or used directly by Clients.
* The Product includes expanded license rights for BMC Atrium
  Orchestrator including unlimited peer licenses, use of all generally
  available Base Adapters, and Development Studio and Operator Control
  Panel user licenses to support the Licensed Capacity. The Product does
  not include the right to use any other Application Adapters other than
  what is installed out-of-the-box.
* Customer may only use the BMC Remedy Service Request Management
  functionality of the BMC Remedy ITSM product.  The Product includes the
  right to use BMC Remedy Service Request Management for any number of
  users, to support any service requests that are directly related to the
  delivery or consumption of Cloud Services, for the Licensed Capacity.
* The Product includes the right to use BMC Network Automation for the
  network devices in the Cloud Environment as long as the number of
  supported Network Devices does not exceed the Licensed Capacity. The
  Product includes the right to use BMC Network Automation only in order
  to enable the initial provisioning, on-going network operations, and
  use of the Virtual Data Center feature for Network Devices in the Cloud
  Environment. The Product does not include the right to use BMC Network
  Automation for the management of Network Devices that are not in a BMC
  Network Automation Pod.
* The Product includes the right to use BMC ProactiveNet Performance
  Management for the Licensed Capacity, only in order to deliver the CPU
  monitoring capabilities that are installed out-of-the-box. The Product
  does not include the right to use any other functional capabilities of
  BMC ProactiveNet Performance Management, including but not limited to,
  use of the BMC ProactiveNet Performance Management console for
  operational purposes, monitoring of IT infrastructure beyond what is
  specified, and any other analytics, diagnostics, event or impact
  management capabilities.
* The product includes the right to use BMC Capacity Optimization for
  the Licensed Capacity only in order to enable the out-of-the-box
  Capacity Aware Placement Advice capability as part of the CLM Resource
  Manager. The Product does not include the rights to use any other
  functional capabilities of BMC Capacity Optimization, including but not
  limited to, the use of BMC Capacity Optimization for capacity planning,
  virtualization and consolidation; capacity analysis, forecasting,
  reporting and dashboards; and capacity metering for showback or
  chargeback.

BMC Cloud Lifecycle Management - Foundation Pack for Service Providers
License Add-on ("CLM Foundation"):
* The Product may only be used in a Cloud Environment.
* If Customer is also a Cloud Service Provider then The Product cannot
  be used by the Cloud Service Provider for other environments, including
  but not limited to the Cloud Service Provider's internal IT
  environment, or System Integration activities for Clients which are not
  part of Cloud Services. The Product may not be installed on Client
  premises or accessed or used directly by Clients.
* The Product includes expanded license rights for BMC Atrium
  Orchestrator including unlimited peer licenses, use of all generally
  available Base Adapters, and Development Studio and Operator Control
  Panel user licenses to support the Licensed Capacity. The Product does
  not include the right to use any other Application Adapters other than
  what is installed out-of-the-box.
* The Product includes the right to use the BMC BladeLogic Server
  Automation (BBSA) for Server Provisioning and Software Deployment
  functionality only. The Product does not include the right to use any
  other functionality of BBSA, including, but not limited to, patching,
  compliance, application release automation, configuration management,
  discovery, inventory, and nsh-scripting.
* Customer may only use the BMC Remedy Service Request Management
  functionality of the BMC Remedy ITSM product.  The Product includes the
  right to use BMC Remedy Service Request Management for any number of
  users, to support any service requests that are directly related to the
  delivery or consumption of Cloud Services, for the Licensed Capacity.
* The Product includes the right to use BMC Network Automation for the
  network devices in the Cloud Environment as long as the number of
  supported Network Devices does not exceed the Licensed Capacity. The
  Product includes the right to use BMC Network Automation only in order
  to enable the initial provisioning, on-going network operations, and
  use of the Virtual Data Center feature for Network Devices in the Cloud
  Environment. The Product does not include the right to use BMC Network
  Automation for the management of Network Devices that are not in a BMC
  Network Automation Pod.
* The Product includes the right to use BMC ProactiveNet Performance
  Management for the Licensed Capacity, only in order to deliver the CPU
  monitoring capabilities that are installed out-of-the-box. The Product
  does not include the right to use any other functional capabilities of
  BMC ProactiveNet Performance Management, including but not limited to,
  use of the BMC ProactiveNet Performance Management console for
  operational purposes, monitoring of IT infrastructure beyond what is
  specified, and any other analytics, diagnostics, event or impact
  management capabilities.
* The product includes the right to use BMC Capacity Optimization for
  the Licensed Capacity only in order to enable the out-of-the-box
  Capacity Aware Placement Advice capability as part of the CLM Resource
  Manager. The Product does not include the rights to use any other
  functional capabilities of BMC Capacity Optimization, including but not
  limited to, the use of BMC Capacity Optimization for capacity planning,
  virtualization and consolidation; capacity analysis, forecasting,
  reporting and dashboards; and capacity metering for showback or
  chargeback.

Desktop/Mobile Management Product Restrictions for BMC Configuration
Management Products: Each "Desktop/Mobile Management" License is
limited for use with one Client Endpoint. "Client Endpoint" means a
laptop, desktop or other non-Server Computer.
* Desktop/Mobile Patch Management Restriction: A "Desktop/Mobile Patch
  Management" License may only be used to manage, deploy, update and
  inventory anti-virus software and security patches on one Client
  Endpoint.
* Desktop/Mobile Patch Management Pack Restriction: The Desktop/Mobile
  Application Management Product and the Desktop/Mobile Configuration
  Discovery Product that are shipped with the Desktop/Mobile Patch
  Management Pack License may only be used to manage, deploy, update and
  inventory anti-virus software and security patches on one licensed
  Client Endpoint, unless Customer has separately licensed the
  Desktop/Mobile Application Management Product and the Desktop/Mobile
  Configuration Discovery Product. Customer may not use the functionality
  of such Products for any other purpose.
* BMC Configuration Management Desktop OS Management Restriction: A
  "BMC CM Desktop OS Management" License may only be used to manage
  operating system migration activities on one Client Endpoint. Each BMC
  CM Desktop OS Management License: (a) may only be used on a licensed
  Client Endpoint that is licensed for use with both a Desktop/Mobile
  Application Management License and a Desktop/Mobile Configuration
  Discovery License; and (b) may not be redeployed or harvested to a
  different Client Endpoint.
* Extranet Application Management Restriction: An "Extranet Application
  Management" License may only be used on one Client Endpoint. The
  parties must mutually agree on the name of each Single Application and
  its primary function at the time of Order. Single Application is
  defined as a Tuner channel containing one application with one primary
  function, and Tuner is defined as is the client component of the
  Product configured by Customer for deployment on licensed Endpoints.

BMC Configuration Management Control Center Module Restriction for BMC
Configuration Management Products: Each "BMC CM Control Center" License
may only be used by Administrators for the project for which it was
licensed. An Administrator is defined as an employee with access to or
the right to use the administrative components of the Product.

BMC Configuration Management Developers Kit Definition and Restriction
for BMC Configuration Management Products: A "BMC CM Developers Kit"
license allows Customer to embed the "SDK Run Time Code" in unmodified
object code form, into a single software application developed by
Customer to create an "SDK Client." "SDK Run Time Code" means the
unmodified object code files in the BMC CM Product that are designated
as re-distributable. "SDK Client" means a software technology with e a
principal purpose and functionality substantially different than that
of the SDK Run Time Code and that uses only a BMC Desktop/Mobile
Management Product, a BMC Device Management Product and/or a BMC Server
Management Product, as applicable, to invoke the update functionality
of the SDK Run Time Code. An SDK Client may only be used on, or
distributed to, licensed Endpoints that are licensed separately by
Customer, which licensed Endpoints may be within or outside of
Customer's organization. "Client Endpoint" means a laptop, desktop or
other non-Server Computer. "Device Endpoint" means a personal digital
assistant or similar computing device. "Endpoint" means a Client
Endpoint, a Device Endpoint, a Server Endpoint, or Other Endpoint, as
the case may be. "Other Endpoint" means a router, a switch, a hub, or
other network device, peripheral or hardware instrument, as the case
may be. "Server Endpoint" is any virtual or physical Computer that
provides a service for other Computers or users connected to it via the
Internet, extranet, intranet, or other networked technologies.
Device Management Product Restriction for BMC Configuration Management
Products: Each "Device Management" License is limited for use with one
Device Endpoint. "Device Endpoint" " means a personal digital assistant
or similar computing device.

Server Management Product Restrictions for BMC Configuration Management
Products: Each "Server Management" License is limited for use per CPU -
Subcapacity.
* Server Patch Management Restriction: A "Server Patch Management"
  License may only be used to manage, deploy, update and inventory
  anti-virus software and security patches per CPU - Subcapacity.
* Server Patch Management Pack Restriction: The Desktop/Mobile
  Application Management Product and the Desktop/Mobile Configuration
  Discovery Product that are shipped with the Server Patch Management
  Pack License may only be used to manage, deploy, update and inventory
  anti-virus software and security patches on licensed Server Endpoints,
  unless Customer has separately licensed the Desktop/Mobile Application
  Management Product and the Desktop/Mobile Configuration Discovery
  Product. Customer may not use the functionality of such Products for
  any other purpose. With respect to the above Server Management
  Licenses, Customer must comply with any restrictions designated at the
  time of Order on the maximum number of CPUs that may be included in
  each Server Endpoint. "Server Endpoint" is any virtual or physical
  Computer that provides a service for other Computers or users connected
  to it via the Internet, extranet, intranet, or other networked
  technologies.

CONTROL-M/Assist: Control-M/Assist may only be used to interface with
the third party scheduler and may not be used to schedule or manage
batch processes outside of the cross-scheduler dependencies.

Control-M Self Service Mobile Integration Kit:  The Control-M Self
Service Mobile Integration Kit is governed by the terms and conditions
of the license agreement provided with the product.

BMC Identity Products:
* Internal User: If a Product name includes the term "Internal User,"
  that Product can only be used by Customer's employees (full time and
  part time) and contractors whose information is being managed using the
  BMC IdM tools. Information on these users will typically be found in
  the HR database.
* External User: If a Product name includes the term "External User,"
  that Product can only be used by Customer's business partners and
  customers/ prospects whose information is being managed using the BMC
  IdM tools or Customer's employees (full or part time)/contractors who
  are licensed to use one or more of the following BMC Identity
  Management Tools: (1) BMC Identity User Administration (2) BMC
  Identity Password Management (3) BMC Identity Compliance Manager,
  provided the users have no more than 2 logons (access points) being
  managed by the IdM tools.
* Archive User: If a Product name includes the term "Archive User,"
  that Product can only be used by users whose identity information is
  stored within the IdM system but is not being actively managed; the
  information could be stored for the purpose of audit/ forensics etc.
* Developer User: If a Product name includes the term "Developer User,"
  that Product can only be used by users who create or modify
  applications using the BMC Directory Management Studio.

BMC Middleware Management - Performance and Availability and BMC
Middleware Management - Transaction Monitoring Products: If Customer is
using BMC Middleware Management version 6.0 or lower, notwithstanding
the Licensed Capacity the number of individual employees or contractors
of Customer to whom access to the Management Console is granted ("End
Users") is limited to the lesser of (a) the Licensed Capacity of the
Product if priced on a per named user Unit of Measurement, or (b) 250
End Users.

BMC Middleware and Transaction Management Products: If Customer is
using BMC Middleware Management version 6.0 or lower, when licensed on
the per CPU - Subcapacity or per MIPS Unit of Measurement, regardless
of the Licensed Capacity, Customer is limited to ten (10) individual
employees or contractors to whom access to the Management Console is
granted ("End Users"). When licensed on the per named user Unit of
Measurement, Customer is limited to the lesser of (a) the Licensed
Capacity of the Product, or (b) 250 End Users.

BMC Mobile Device Management Products: For BMC Mobile Device Management
(MDM) Products, any clickwrap agreement with AirWatch, LLC contained in
the Products is void and of no effect. Customer's use of these Products
is governed by the Agreement.

BMC Monitoring Only Products: Customer is not entitled to use analytics
as further detailed in the Documentation.

BMC Real End User Experience Monitoring and Analytics - Licensed Add-on
Product: For synthetic transaction monitoring solutions, each instance
of the execution server installed should be counted. For real end user
transaction monitoring solutions, each instance of the watchpoint
created should be counted.

BMC Remedy Products: Customer may not bypass, in any way, the use of a
concurrent or named user license to manage an update (including,
without limitation, submitting a ticket to a parallel form and then
using workflow to perform the update without a license).

Development License Restriction for BMC Remedy Products: If a Product
name includes the term "Dev Lsn", Customer will restrict installation,
access and use of such Product to a server dedicated to development and
testing only, and will not allow any production or commercial activity
on that server.

Hot Backup License Definition and Restriction for BMC Remedy Products:
A hot backup license is a replicate of the Remedy production licenses
on one backup server. Customer may access that backup server only when
the customary server on which the AR System is installed fails or in
preparation of that backup server for such situation.

Load Balanced System Restriction for BMC Remedy Products: If Customer
has multiple servers in a single logical environment pointing to a
single AR System database instance, only one Instance of Remedy "per
Instance" licenses is required for installation on these servers
(except for the AR System, which must be licensed for each server).

BMC Server Automation - Compliance License Add-on: Excludes use of the
BMC BladeLogic agent for server configuration, patching, and
provisioning tasks.

BMC Server Automation - Configuration License Add-on: Excludes use of
the BMC BladeLogic agent for server compliance, remediation, and
provisioning tasks.

BMC Server Automation - Patch License Add-on: Excludes use of the BMC
BladeLogic agent for server configuration, compliance, and provisioning
tasks.

BMC Server Automation - Provisioning License Add-on: Excludes use of
the BMC BladeLogic agent for server configuration, patching,
compliance, and remediation tasks.

BMC Service Desk Express Products: No terms in any Business Objects or
Crystal license agreement embedded in the Product apply to the Product.
Customer may make and operate 2 additional copies of the Product solely
for internal pre-production configuration and testing purposes.

BMC Service Desk Express Suite Restriction for BMC Service Desk Express
Products: When purchasing Concurrent User licenses for the "Service
Desk Express" Product, regardless of the number of such licenses
purchased and regardless of the number of purchases made (including
future purchases), Customer is restricted via license keys to a total
of (i) five Concurrent Users conducting a process in the report
environment of the Crystal Reports "Web Server" product which is
embedded in the "Service Desk Express" Product and (ii) two named users
accessing the "Crystal Reports Professional " product which is bundled
with the "Service Desk Express" Product.

License Allocation Restriction for BMC ITSM Products: Notwithstanding
anything to the contrary in this Order or the Agreement, and when the
Product is licensed (i) on the "per named user" Unit of Measurement,
Customer may exchange 5 named user licenses of the Product for 2
licenses of the same Product with the Unit of Measurement of "per
concurrent user" or (ii) on the "per concurrent user" Unit of
Measurement, Customer may exchange 2 concurrent user licenses for 5
licenses of the same Product with the Unit of Measurement of "per named
user". Customer will not incur additional charges for such exchange of
licenses so long as Customer does not exceed the Licensed Capacity of
the Product granted to Customer, however, Customer must: (i) notify BMC
in writing of its intent to exchange the Product Licenses and (ii)
enter into a separate Order to reflect Customer's new Licensed Capacity
and the new Unit of Measurement.

License Restriction for Borland Silk Performer Synthetic Transaction
Monitoring for BMC Software:  The Borland Silk Performer Synthetic
Transaction Monitoring for BMC Software product may only be used with
BMC performance management products and BMC application performance
management products.

Products Installed on Customer's Amazon Web Services ("AWS") Cloud
Environment:
* In instances where Customer hosts the Product on Customer's AWS cloud
  environment, Customer is responsible for working with AWS to ensure the
  security of its overall AWS cloud environment and the Product.
* An Amazon Machine Image ("AMI") is a special type of pre-configured
  operating system and virtual application software which is used to
  create a virtual machine within the Amazon Elastic Compute Cloud
  ("EC2"). An AMI serves as the basic unit of deployment for services
  delivered using EC2.  In instances where BMC provides Customer with an
  AMI of a Product to be used on Customer's AWS cloud environment,
  Customer is responsible for the security of the Product's operation and
  any potential vulnerabilities in a Product AMI's preconfigured OS
  stack, Application stack, and/or OS configuration.

c. UNITS OF MEASUREMENT.  The following units of measurement apply to
certain Products.

 per adapter: A license is required for each installation of an adapter
that interfaces with the Product.
 per agent: A license is required for each unit of software with the
official name of Remote Sys Call Daemon or RSCD Agent that can be
deployed on a physical or virtual operating system.
 per application: A license is required for all unique collection of
application component templates and configuration objects used to form
a single logical platform defined by the Customer.
 per asset: A license is required for every physical or logical Server
Endpoint, Client Endpoint, Device Endpoint, Data Center Rack, Data
Center IP Sensor, or Other Endpoint monitored, managed or discovered by
the Product. "Client Endpoint" means a laptop, desktop or other
non-Server Computer. "Device Endpoint" means a personal digital
assistant or similar computing device. "Other Endpoint" means a router,
a switch, a hub, or other network device, peripheral or hardware
instrument, as the case may be. A "Server Endpoint" is any virtual or
physical Computer that provides a service for other Computers or users
connected to it via the Internet, extranet, intranet, or other
networked technologies.
 per CiscoTM UCS Server: A license is required for each Cisco Unified
Computing System (UCS) Server on which the Product is installed and/or
manages regardless of whether the Product or one of its components is
installed on that Server.
 per Client Endpoint: A license is required for each Client Endpoint.
"Client Endpoint" means a laptop, desktop or other non-Server Computer.
 per component: A license is required for all objects that represent a
physical or logical part of the service model.
 per concurrent access license: A license is required for the maximum
number of simultaneous sessions accessing the Product. Sessions are
counted in packs of 5.
 per concurrent session: A license is required for the maximum number
of simultaneous sessions accessing the Product.
 per concurrent user: A license is required for the maximum number of
individual employees or contractors of Customer to whom simultaneous
access has been granted to the Product on a computer or multiple
computers.
 per CPU - Full Capacity: A license is required for the total number of
active, physical CPUs in each Computer upon which the Product is
installed or which the Product manages, either remotely or locally.
"CPU" means a physical processor or central unit in a designated
Computer containing the logic circuitry that performs the instructions
of a Computer's programs and refers to the "socket" which can contain
one or more processor cores.
 per CPU - Subcapacity: A license is required for all active, physical
CPUs which the Product manages, either remotely or locally. "CPU" means
a physical processor or central unit in a designated Computer
containing the logic circuitry that performs the instructions of a
Computer's programs and refers to the "socket" which can contain one or
more processor cores.
 per database: A license is required for the total allocated database
space per host ID or physical Computer which the Product is managing.
The total allocated database capacity cannot be segregated or
aggregated into lower or higher ranges.
 per deployed robot: A license is required for all PATROL End-to-End
Response Timer robots deployed.
 per Device Endpoint: A license is required for each Device Endpoint.
"Device Endpoint" means a personal digital assistant or similar
computing device.
 per engine: A license is required for each mainframe general purpose
engine on the server upon which the Product is installed and/or manages
regardless of whether the Product or one of its components is installed
on that Server.
 per enterprise: A license is required per Customer and per Client
each, regardless of the number of times Customer installs the Product
in its Enterprise or its Client's Enterprise.
 per gigabyte: A license is required for the total allocated database
space of all Computers on which the Product has been installed or
operated.
 per gigabyte range: A license is required for the total allocated
database space per host ID or physical Computer which the Product is
managing. The Product may not be moved to another Computer unless the
current Computer is taken out of service. The total allocated database
capacity cannot be segregated or aggregated into lower or higher ranges
among different Computers. For example: if Customer licenses 26-50
gigabytes, the Customer is only licensed for a maximum of 50 gigabytes
in total across all the databases of the licensed Product on one
particular Computer.
 per installed server: A license is required for each Server (with a
Classification at the appropriate Tier level, if applicable) upon which
the Product or any of its components is installed.
 per instance: A license is required for all named occurrences of the
Product created or installed in the Enterprise.
 per Linux engine: A license is required for all engines of a mainframe
Computer on which Customer is running Linux, when applicable classified
by Linux Group using BMC's standard Computer classification.
 per managed asset - Device Endpoint: A license is required for every
Device Endpoint that is monitored, managed, or discovered by the
Product(s). A "Device Endpoint" can be any virtual or physical
Non-Server Client Computer (e.g. laptop, desktop computer, PDA, smart
phone); any network device (e.g. router, switch, hub) standalone or
chassis-based device/card/processor using a unique-IP address (also
includes virtual network devices managed through the IP address of its
physical host); and independent storage (e.g. a disk array, a fiber
switch, a tape library, a switch director). When applicable, the
license must be computed at the appropriate tier level.
 per managed asset - server endpoint: A license is required for every
Server Endpoint monitored, managed (directly or indirectly), or
discovered by the Product(s). "Server Endpoint" is any virtual or
physical Computer that provides a service for other Computers or users
connected to it via the Internet, extranet, intranet, or other
networked technologies.
 per managed component: A license is required for all objects that
represent a physical or logical part of the service model managed by
the Product.
 per managed network device: A license is required for each Network
Device managed using a unique IP-address. "Network Device" means a
standalone or chassis-based network device/card/processor.
 per managed server: A license is required for each Server managed by
the Product or one of its components whether locally or remotely. When
applicable, this license must be computed at the appropriate tier level
based on the cumulative count of managed servers. Network Devices are
not counted as Servers. This license does not include the Product's
installation on or management of Integrated Facility for Linux (IFL)
engines. "Network Device" means a standalone or chassis-based network
device/card/processor.
 per MIPS: A license is required for the total aggregate number of MIPS
for each Computer, including all Computers coupled in a parallel
Sysplex environment, upon which the Product is installed, managed or
monitored.  MIPS Rating is the aggregate computing power (expressed in
millions of instructions per second) of a Computer, using the MIPS
rating set forth in the then current Gartner Group Rating Guide.
Computer-specific passwords will be issued for the Product.
 per monitored element: A license is required for all remotely
monitored elements, such as a Server, database, operating system, URL,
firewall, storage, or network device.
 per monitored server: A license is required for each Server (with a
Classification at the appropriate Tier level, if applicable) which the
Product or one of its components is monitoring regardless of whether
the Product is monitoring it locally or remotely.
 per named user: A license (with a Classification at the appropriate
Level, if applicable) is required for all individual employees or
contractors or clients of Customer to whom access has been granted to
the Product on a computer or multiple computers typically via the
issuance of a unique ID regardless of whether the individual is
actively using the Product at any given time.
 per node: A license is required for every Node which the Product
manages and/or monitors. "Node" means a laptop, desktop, or any virtual
or physical Computer that provides a service for other Computers or
users connected to it via the Internet, extranet, intranet, or other
networked technologies.
 per port: A license is required for each port. A port is defined as a
physical connection point used by a storage device to connect other
devices or systems. For the purpose of BMC licensing, all active ports
(Fibre Channel, iSCSI, etc.) for all managed devices (storage arrays,
filers, tape libraries, etc.) are counted. Ports on hosts, gateways and
switches are not to be counted.
 per project: A license is required for each specific project, facility
or business unit, as the case may be specified at the time of order.
 per Server Endpoint: A license is required for each Server Endpoint. A
"Server Endpoint" is any virtual or physical Computer that provides a
service for other Computers or users connected to it via the Internet,
extranet, intranet, or other networked technologies.
 per Service Management MIPS: A license is required for the total
aggregate number of MIPS for each Computer, including all Computers
coupled in a parallel Sysplex environment, upon which the Product is
installed, managed or monitored. MIPS Rating is the aggregate computing
power (expressed in millions of instructions per second) of a Computer,
using the MIPS rating set forth in the then current Gartner Group
Rating Guide.
 per site: A license is required for the physical site at which the
Product is installed regardless of the number of times the Product is
installed.
 per task: For all Control-M Products, except those that are restricted
to the Mainframe environment, a license is required for the maximum
number of Tasks (as defined below) present in the Control-M "Active
Jobs" databases in any 24-hour period, regardless of whether the Tasks
execute or not. For the Control-M Mainframe add-on products, a license
is required for the maximum number of Tasks (as defined below) present
in solely the Mainframe environment's Control-M "Active Jobs" database.
Tasks in the Control-M "Active Jobs" databases include all Tasks that
are monitored by Control-M in all Distributed Systems and/or Mainframe
environments (including but not limited to development, staging, QA,
pre-production, production, and test environments), except that, (i)
SMART folders/table and sub-folders/tables which contain scheduling
definitions and are listed as tasks in the "Active Jobs" databases are
not counted as Tasks, (ii) Tasks that have time zone settings may
remain in the "Active Jobs" databases for up to three consecutive days,
but are only counted as one Task, (iii) a Task that runs more than once
during the day (with the same Order ID) is counted as one Task - this
includes Tasks that are rerun and cyclic Tasks, and (iv) Tasks that are
provided for by licenses under alternative Units of Measurement (i.e.
tier or MIPS) are not considered Tasks under this "per task" unit of
measurement. The number of steps or scripts executed within the named
Task shall have no bearing upon the number of Tasks licensed. "Task"
is interchangeable with "job" and means an executable command
containing the name of the JCL, CL, DCL, ECL, script or dummy processes
that is scheduled to execute, as well as the scheduling criteria, flow
control, and resource usage.
 per terabyte: A license is required for the total aggregate storage
capacity in the Enterprise.
 per third-party software: A license is required for each installation
of the third-party software product that interfaces with the Product.


YOU AGREE THAT YOU HAVE READ THIS AGREEMENT AND INTEND TO BE BOUND, AS
IF YOU HAD SIGNED THIS AGREEMENT IN WRITING. IF YOU ARE ACTING ON
BEHALF OF AN ENTITY, YOU WARRANT THAT YOU HAVE THE AUTHORITY TO ACCEPT
THE TERMS OF THIS AGREEMENT FOR SUCH ENTITY.

Copyright 2001-2010 (C) MetaStuff, Ltd. All Rights Reserved.

Redistribution and use of this software and associated documentation
("Software"), with or without modification, are permitted provided
that the following conditions are met:

1. Redistributions of source code must retain copyright
   statements and notices.  Redistributions must also contain a
   copy of this document.
 
2. Redistributions in binary form must reproduce the
   above copyright notice, this list of conditions and the
   following disclaimer in the documentation and/or other
   materials provided with the distribution.
 
3. The name "DOM4J" must not be used to endorse or promote
   products derived from this Software without prior written
   permission of MetaStuff, Ltd.  For written permission,
   please contact dom4j-info@metastuff.com.
 
4. Products derived from this Software may not be called "DOM4J"
   nor may "DOM4J" appear in their names without prior written
   permission of MetaStuff, Ltd. DOM4J is a registered
   trademark of MetaStuff, Ltd.
 
5. Due credit should be given to the DOM4J Project - 
   http://dom4j.sourceforge.net
 
THIS SOFTWARE IS PROVIDED BY METASTUFF, LTD. AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL
METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE.

Copyright © 2005-2009, The Dojo Foundation
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

  * Redistributions of source code must retain the above copyright notice,
    this list of conditions and the following disclaimer.
  * Redistributions in binary form must reproduce the above copyright 
    notice, this list of conditions and the following disclaimer in the
    documentation and/or other materials provided with the distribution.
  * Neither the name of the Dojo Foundation nor the names of its 
    contributors may be used to endorse or promote products derived from
    this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.

Copyright © 2000-2004 Jason Hunter & Brett McLaughlin.
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

1. Redistributions of source code must retain the above copyright
   notice, this list of conditions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions, and the disclaimer that follows
   these conditions in the documentation and/or other materials
   provided with the distribution.

3. The name "JDOM" must not be used to endorse or promote products
   derived from this software without prior written permission.  For
   written permission, please contact (request_AT_jdom_DOT_org).

4. Products derived from this software may not be called "JDOM", nor
   may "JDOM" appear in their name, without prior written permission
   from the JDOM Project Management (request_AT_jdom_DOT_org).

In addition, we request (but do not require) that you include in the
end-user documentation provided with the redistribution and/or in the
software itself an acknowledgement equivalent to the following:
    "This product includes software developed by the
     JDOM Project http://www.jdom.org/.
Alternatively, the acknowledgment may be graphical using the logos
available at http://www.jdom.org/images/logos.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED.  IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

This software consists of voluntary contributions made by many
individuals on behalf of the JDOM Project and was originally
created by Jason Hunter (jhunter_AT_jdom_DOT_org) and
Brett McLaughlin (brett_AT_jdom_DOT_org).  For more information
on the JDOM Project, please see see http://www.jdom.org/.

Copyright © 1999-2004 Ng Pheng Siong. All rights reserved.

Portions copyright © 2004-2006 Open Source Applications Foundation.
All rights reserved.

Portions copyright © 2005-2006 Vrije Universiteit Amsterdam.
All rights reserved.

Copyright © 2008-2010 Heikki Toivonen. All rights reserved.

Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in
supporting documentation.

THE AUTHOR PROVIDES THIS SOFTWARE ``AS IS'' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

PLY (Python Lex-Yacc)                   Version 3.4

Copyright © 2001-2011,
David M. Beazley (Dabeaz LLC)
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

* Redistributions of source code must retain the above copyright notice,
  this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
  notice, this list of conditions and the following disclaimer in the
  documentation and/or other materials provided with the distribution.
* Neither the name of the David Beazley or Dabeaz LLC may be used to
  endorse or promote products derived from this software without
  specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

We apply patches to the Python 2.7.1 source to accomplish the following:

    - Stop building of the bsddb module as we use the additional module
      seperately
    - Fix for http://bugs.python.org/issue1692335
    - Replace calls from select to poll in the select module to
      overcome limitations on maximum file descriptor number


This is the official license for the Python 2.7 release:

A. HISTORY OF THE SOFTWARE
==========================

Python was created in the early 1990s by Guido van Rossum at Stichting
Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands
as a successor of a language called ABC.  Guido remains Python's
principal author, although it includes many contributions from others.

In 1995, Guido continued his work on Python at the Corporation for
National Research Initiatives (CNRI, see http://www.cnri.reston.va.us)
in Reston, Virginia where he released several versions of the
software.

In May 2000, Guido and the Python core development team moved to
BeOpen.com to form the BeOpen PythonLabs team.  In October of the same
year, the PythonLabs team moved to Digital Creations (now Zope
Corporation, see http://www.zope.com).  In 2001, the Python Software
Foundation (PSF, see http://www.python.org/psf/) was formed, a
non-profit organization created specifically to own Python-related
Intellectual Property.  Zope Corporation is a sponsoring member of
the PSF.

All Python releases are Open Source (see http://www.opensource.org for
the Open Source Definition).  Historically, most, but not all, Python
releases have also been GPL-compatible; the table below summarizes
the various releases.

    Release         Derived     Year        Owner       GPL-
                    from                                compatible? (1)

    0.9.0 thru 1.2              1991-1995   CWI         yes
    1.3 thru 1.5.2  1.2         1995-1999   CNRI        yes
    1.6             1.5.2       2000        CNRI        no
    2.0             1.6         2000        BeOpen.com  no
    1.6.1           1.6         2001        CNRI        yes (2)
    2.1             2.0+1.6.1   2001        PSF         no
    2.0.1           2.0+1.6.1   2001        PSF         yes
    2.1.1           2.1+2.0.1   2001        PSF         yes
    2.2             2.1.1       2001        PSF         yes
    2.1.2           2.1.1       2002        PSF         yes
    2.1.3           2.1.2       2002        PSF         yes
    2.2.1           2.2         2002        PSF         yes
    2.2.2           2.2.1       2002        PSF         yes
    2.2.3           2.2.2       2003        PSF         yes
    2.3             2.2.2       2002-2003   PSF         yes
    2.3.1           2.3         2002-2003   PSF         yes
    2.3.2           2.3.1       2002-2003   PSF         yes
    2.3.3           2.3.2       2002-2003   PSF         yes
    2.3.4           2.3.3       2004        PSF         yes
    2.3.5           2.3.4       2005        PSF         yes
    2.4             2.3         2004        PSF         yes
    2.4.1           2.4         2005        PSF         yes
    2.4.2           2.4.1       2005        PSF         yes
    2.4.3           2.4.2       2006        PSF         yes
    2.4.4           2.4.3       2006        PSF         yes
    2.5             2.4         2006        PSF         yes
    2.5.1           2.5         2007        PSF         yes
    2.5.2           2.5.1       2008        PSF         yes
    2.5.3           2.5.2       2008        PSF         yes
    2.6             2.5         2008        PSF         yes
    2.6.1           2.6         2008        PSF         yes
    2.6.2           2.6.1       2009        PSF         yes
    2.6.3           2.6.2       2009        PSF         yes
    2.6.4           2.6.3       2009        PSF         yes
    2.6.5           2.6.4       2010        PSF         yes
    2.7             2.6         2010        PSF         yes

Footnotes:

(1) GPL-compatible doesn't mean that we're distributing Python under
    the GPL.  All Python licenses, unlike the GPL, let you distribute
    a modified version without making your changes open source.  The
    GPL-compatible licenses make it possible to combine Python with
    other software that is released under the GPL; the others don't.

(2) According to Richard Stallman, 1.6.1 is not GPL-compatible,
    because its license has a choice of law clause.  According to
    CNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1
    is "not incompatible" with the GPL.

Thanks to the many outside volunteers who have worked under Guido's
direction to make these releases possible.


B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON
===============================================================

PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
--------------------------------------------

1. This LICENSE AGREEMENT is between the Python Software Foundation
("PSF"), and the Individual or Organization ("Licensee") accessing and
otherwise using this software ("Python") in source or binary form and
its associated documentation.

2. Subject to the terms and conditions of this License Agreement, PSF
hereby grants Licensee a nonexclusive, royalty-free, world-wide license
to reproduce, analyze, test, perform and/or display publicly, prepare
derivative works, distribute, and otherwise use Python alone or in any
derivative version, provided, however, that PSF's License Agreement and
PSF's notice of copyright, i.e., "Copyright (c) 2001, 2002, 2003, 2004,
2005, 2006, 2007, 2008, 2009, 2010 Python Software Foundation; All Rights
Reserved" are retained in Python alone or in any derivative version
prepared by Licensee.

3. In the event Licensee prepares a derivative work that is based on
or incorporates Python or any part thereof, and wants to make
the derivative work available to others as provided herein, then
Licensee hereby agrees to include in any such work a brief summary of
the changes made to Python.

4. PSF is making Python available to Licensee on an "AS IS"
basis.  PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED.  BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.

5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

6. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.

7. Nothing in this License Agreement shall be deemed to create any
relationship of agency, partnership, or joint venture between PSF and
Licensee.  This License Agreement does not grant permission to use PSF
trademarks or trade name in a trademark sense to endorse or promote
products or services of Licensee, or any third party.

8. By copying, installing or otherwise using Python, Licensee
agrees to be bound by the terms and conditions of this License
Agreement.


BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
-------------------------------------------

BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1

1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
Individual or Organization ("Licensee") accessing and otherwise using
this software in source or binary form and its associated
documentation ("the Software").

2. Subject to the terms and conditions of this BeOpen Python License
Agreement, BeOpen hereby grants Licensee a non-exclusive,
royalty-free, world-wide license to reproduce, analyze, test, perform
and/or display publicly, prepare derivative works, distribute, and
otherwise use the Software alone or in any derivative version,
provided, however, that the BeOpen Python License is retained in the
Software, alone or in any derivative version prepared by Licensee.

3. BeOpen is making the Software available to Licensee on an "AS IS"
basis.  BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED.  BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.

4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

5. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.

6. This License Agreement shall be governed by and interpreted in all
respects by the law of the State of California, excluding conflict of
law provisions.  Nothing in this License Agreement shall be deemed to
create any relationship of agency, partnership, or joint venture
between BeOpen and Licensee.  This License Agreement does not grant
permission to use BeOpen trademarks or trade names in a trademark
sense to endorse or promote products or services of Licensee, or any
third party.  As an exception, the "BeOpen Python" logos available at
http://www.pythonlabs.com/logos.html may be used according to the
permissions granted on that web page.

7. By copying, installing or otherwise using the software, Licensee
agrees to be bound by the terms and conditions of this License
Agreement.


CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
---------------------------------------

1. This LICENSE AGREEMENT is between the Corporation for National
Research Initiatives, having an office at 1895 Preston White Drive,
Reston, VA 20191 ("CNRI"), and the Individual or Organization
("Licensee") accessing and otherwise using Python 1.6.1 software in
source or binary form and its associated documentation.

2. Subject to the terms and conditions of this License Agreement, CNRI
hereby grants Licensee a nonexclusive, royalty-free, world-wide
license to reproduce, analyze, test, perform and/or display publicly,
prepare derivative works, distribute, and otherwise use Python 1.6.1
alone or in any derivative version, provided, however, that CNRI's
License Agreement and CNRI's notice of copyright, i.e., "Copyright (c)
1995-2001 Corporation for National Research Initiatives; All Rights
Reserved" are retained in Python 1.6.1 alone or in any derivative
version prepared by Licensee.  Alternately, in lieu of CNRI's License
Agreement, Licensee may substitute the following text (omitting the
quotes): "Python 1.6.1 is made available subject to the terms and
conditions in CNRI's License Agreement.  This Agreement together with
Python 1.6.1 may be located on the Internet using the following
unique, persistent identifier (known as a handle): 1895.22/1013.  This
Agreement may also be obtained from a proxy server on the Internet
using the following URL: http://hdl.handle.net/1895.22/1013".

3. In the event Licensee prepares a derivative work that is based on
or incorporates Python 1.6.1 or any part thereof, and wants to make
the derivative work available to others as provided herein, then
Licensee hereby agrees to include in any such work a brief summary of
the changes made to Python 1.6.1.

4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
basis.  CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED.  BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.

5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

6. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.

7. This License Agreement shall be governed by the federal
intellectual property law of the United States, including without
limitation the federal copyright law, and, to the extent such
U.S. federal law does not apply, by the law of the Commonwealth of
Virginia, excluding Virginia's conflict of law provisions.
Notwithstanding the foregoing, with regard to derivative works based
on Python 1.6.1 that incorporate non-separable material that was
previously distributed under the GNU General Public License (GPL), the
law of the Commonwealth of Virginia shall govern this License
Agreement only as to issues arising under or with respect to
Paragraphs 4, 5, and 7 of this License Agreement.  Nothing in this
License Agreement shall be deemed to create any relationship of
agency, partnership, or joint venture between CNRI and Licensee.  This
License Agreement does not grant permission to use CNRI trademarks or
trade name in a trademark sense to endorse or promote products or
services of Licensee, or any third party.

8. By clicking on the "ACCEPT" button where indicated, or by copying,
installing or otherwise using Python 1.6.1, Licensee agrees to be
bound by the terms and conditions of this License Agreement.

        ACCEPT


CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
--------------------------------------------------

Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
The Netherlands.  All rights reserved.

Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in
supporting documentation, and that the name of Stichting Mathematisch
Centrum or CWI not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior
permission.

STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Unless stated in the specfic source file, this work is
Copyright © 1994-2008, Mark Hammond
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the distribution.

Neither name of Mark Hammond nor the name of contributors may be used
to endorse or promote products derived from this software without
specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS
IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The python-ldap package is distributed under Python-style license.

Standard disclaimer:
   This software is made available by the author(s) to the public for free
   and "as is".  All users of this free software are solely and entirely
   responsible for their own choice and use of this software for their
   own purposes.  By using this software, each user agrees that the
   author(s) shall not be liable for damages of any kind in relation to
   its use or performance. The author(s) do not warrant that this software
   is fit for any purpose.

$Id: LICENCE,v 1.1 2002/09/18 18:51:22 stroeder Exp $

Copyright © 2003 Red Hat, Inc. All rights reserved. "Red Hat" and the Red
Hat "Shadowman" logo are registered trademarks of Red Hat, Inc. "Linux" is
a registered trademark of Linus Torvalds. All other trademarks are the
property of their respective owners.

LICENSE AGREEMENT AND LIMITED PRODUCT WARRANTY
RED HAT® ENTERPRISE LINUX® AND RED HAT® APPLICATIONS

This agreement governs the use of the Software and any updates to the
Software, regardless of the delivery mechanism. The Software is a
collective work under U.S. Copyright Law. Subject to the following terms,
Red Hat, Inc. ("Red Hat") grants to the user ("Customer") a license to
this collective work pursuant to the GNU General Public License.

1. The Software. Red Hat Enterprise Linux and Red Hat Applications (the
"Software") are either a modular operating system or application
consisting of hundreds of software components. The end user license
agreement for each component is located in the component's source code.
With the exception of certain image files identified in Section 2 below,
the license terms for the components permit Customer to copy, modify, and
redistribute the component, in both source code and binary code forms.
This agreement does not limit Customer's rights under, or grant Customer
rights that supersede, the license terms of any particular component.

2. Intellectual Property Rights. The Software and each of its components,
including the source code, documentation, appearance, structure and
organization are owned by Red Hat and others and are protected under
copyright and other laws. Title to the Software and any component, or to
any copy, modification, or merged portion shall remain with the
aforementioned, subject to the applicable license. The "Red Hat"
trademark and the "Shadowman" logo are registered trademarks of Red Hat
in the U.S. and other countries. This agreement does not permit Customer
to distribute the Software using Red Hat's trademarks. Customer should
read the information found at
http://www.redhat.com/about/corporate/trademark/ before distributing a
copy of the Software, regardless of whether it has been modified. If
Customer makes a commercial redistribution of the Software, unless a
separate agreement with Red Hat is executed or other permission granted,
then Customer must modify any files identified as "REDHAT-LOGOS" and
"anaconda-images" to remove all images containing the "Red Hat" trademark
or the "Shadowman" logo. Merely deleting these files may corrupt the
Software.

3. Limited Warranty. Except as specifically stated in this agreement or a
license for a particular component, to the maximum extent permitted under
applicable law, the Software and the components are provided and licensed
"as is" without warranty of any kind, expressed or implied, including the
implied warranties of merchantability, non-infringement or fitness for a
particular purpose. Red Hat warrants that the media on which the Software
is furnished will be free from defects in materials and manufacture under
normal use for a period of 30 days from the date of delivery to Customer.
Red Hat does not warrant that the functions contained in the Software
will meet Customer's requirements or that the operation of the Software
will be entirely error free or appear precisely as described in the
accompanying documentation. This warranty extends only to the party that
purchases the Software from Red Hat or a Red Hat authorized distributor.

4. Limitation of Remedies and Liability. To the maximum extent permitted
by applicable law, the remedies described below are accepted by Customer
as its only remedies. Red Hat's entire liability, and Customer's
exclusive remedies, shall be: If the Software media is defective,
Customer may return it within 30 days of delivery along with a copy of
Customer's payment receipt and Red Hat, at its option, will replace it or
refund the money paid by Customer for the Software. To the maximum extent
permitted by applicable law, Red Hat or any Red Hat authorized dealer
will not be liable to Customer for any incidental or consequential
damages, including lost profits or lost savings arising out of the use or
inability to use the Software, even if Red Hat or such dealer has been
advised of the possibility of such damages. In no event shall Red Hat's
liability under this agreement exceed the amount that Customer paid to
Red Hat under this agreement during the twelve months preceding the
action.

5. Export Control. As required by U.S. law, Customer represents and
warrants that it: (a) understands that the Software is subject to export
controls under the U.S. Commerce Department's Export Administration
Regulations ("EAR"); (b) is not located in a prohibited destination
country under the EAR or U.S. sanctions regulations (currently Cuba,
Iran, Iraq, Libya, North Korea, Sudan and Syria); (c) will not export,
re-export, or transfer the Software to any prohibited destination,
entity, or individual without the necessary export license(s) or
authorizations(s) from the U.S. Government; (d) will not use or transfer
the Software for use in any sensitive nuclear, chemical or biological
weapons, or missile technology end-uses unless authorized by the U.S.
Government by regulation or specific license; (e) understands and agrees
that if it is in the United States and exports or transfers the Software
to eligible end users, it will, as required by EAR Section 740.17(e),
submit semi-annual reports to the Commerce Department's Bureau of
Industry & Security (BIS), which include the name and address (including
country) of each transferee; and (f) understands that countries other
than the United States may restrict the import, use, or export of
encryption products and that it shall be solely responsible for
compliance with  any such import, use or export restrictions.

6.Third Party Programs. Red Hat may distribute third party software
programs with the Software that are not part of the Software. These third
party programs are subject to their own license terms. The license terms
either accompany the programs or can be viewed at
http://www.redhat.com/licenses/. If Customer does not agree to abide by
the applicable license terms for such programs, then Customer may not
install them. If Customer wishes to install the programs on more than one
system or transfer the programs to another party, then Customer must
contact the licensor of the programs.

7. General. If any provision of this agreement is held to be
unenforceable, that shall not affect the enforceability of the remaining
provisions. This agreement shall be governed by the laws of the State of
North Carolina and of the United States, without regard to any conflict
of laws provisions, except that the United Nations Convention on the
International Sale of Goods shall not apply.

Copyright © 2000-2010, ReportLab Inc.
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:

*  Redistributions of source code must retain the above copyright notice,
   this list of conditions and the following disclaimer.
*  Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the 
   documentation and/or other materials provided with the distribution.
*  Neither the name of the company nor the names of its contributors may 
   be used to endorse or promote products derived from this software
   without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" 
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE OFFICERS OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

Copyright © 2001-2010 Jochen Katz, Frank Fock

This software is based on SNMP++ 2.6 from Hewlett Packard:

Copyright © 1996
Hewlett-Packard Company

ATTENTION: USE OF THIS SOFTWARE IS SUBJECT TO THE FOLLOWING TERMS.
Permission to use, copy, modify, distribute and/or sell this software 
and/or its documentation is hereby granted without fee. User agrees 
display the above copyright notice and this license notice in all 
copies of the software and any documentation of the software. User 
agrees to assume all liability for the use of the software; 
Hewlett-Packard and Jochen Katz make no representations about the 
suitability of this software for any purpose. It is provided 
"AS-IS" without warranty of any kind, either express or implied. User 
hereby grants a royalty-free license to any and all derivatives based
upon this software code base.

Copyright (c) 2008 VMware, Inc. All Rights Reserved.
Copyright (c) 2009 Altor Networks. All Rights Reserved.
Copyright (c) 2009 NetApp. All Rights Reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

* Neither the name of VMware, Inc. nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL VMWARE, INC.
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The Gist

Webware for Python is open source, but there is no requirement that 
products developed with or derivative to Webware become open source.

Webware for Python is copyrighted, but you can freely use and copy it as 
long as you don't change or remove this copyright notice. The license is 
a clone of the original OSI-approved Python license.

There is no warranty of any kind. Use at your own risk.

Read this entire document for complete, legal details.

Copyright

Copyright © 1999-2010 by Chuck Esterbrook;
All rights reserved.

License

Permission to use, copy, modify, and distribute this software and its 
documentation for any purpose and without fee is hereby granted, provided 
that the above copyright notice appear in all copies and that both that 
copyright notice and this permission notice appear in supporting 
documentation, and that the names of the authors not be used in 
advertising or publicity pertaining to distribution of the software 
without specific, written prior permission.
Disclaimer

THE AUTHORS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, 
INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO 
EVENT SHALL THE AUTHORS BE LIABLE FOR ANY SPECIAL, INDIRECT OR 
CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF 
USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR 
OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 
PERFORMANCE OF THIS SOFTWARE.

Trademarks

All trademarks referred to in the source code, documentation, sample 
files or otherwise, are reserved by their respective owners. 

Copyright © 1999-2011, Digital Creations, Fredericksburg, VA, USA
and Andrew Kuchling; All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

Redistributions of source code must retain the above copyright
notice, this list of conditions, and the disclaimer that follows.

Redistributions in binary form must reproduce the above copyright
notice, this list of conditions, and the following disclaimer in
the documentation and/or other materials provided with the
distribution.

Neither the name of Digital Creations nor the names of its
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY DIGITAL CREATIONS AND CONTRIBUTORS *AS
IS* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL DIGITAL
CREATIONS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.

ipaddr Copyright © 2007 Google Inc

Licensed to PSF under a Contributor Agreement.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied. See the License for the specific language governing
permissions and limitations under the License.

http://code.google.com/p/ipaddr-py/

                   GNU LESSER GENERAL PUBLIC LICENSE
                       Version 3, 29 June 2007

Copyright (C) 2007 Free Software Foundation, Inc. 
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.


  This version of the GNU Lesser General Public License incorporates
the terms and conditions of version 3 of the GNU General Public
License, supplemented by the additional permissions listed below.

  0. Additional Definitions.

  As used herein, "this License" refers to version 3 of the GNU Lesser
General Public License, and the "GNU GPL" refers to version 3 of the GNU
General Public License.

  "The Library" refers to a covered work governed by this License,
other than an Application or a Combined Work as defined below.

  An "Application" is any work that makes use of an interface provided
by the Library, but which is not otherwise based on the Library.
Defining a subclass of a class defined by the Library is deemed a mode
of using an interface provided by the Library.

  A "Combined Work" is a work produced by combining or linking an
Application with the Library.  The particular version of the Library
with which the Combined Work was made is also called the "Linked
Version".

  The "Minimal Corresponding Source" for a Combined Work means the
Corresponding Source for the Combined Work, excluding any source code
for portions of the Combined Work that, considered in isolation, are
based on the Application, and not on the Linked Version.

  The "Corresponding Application Code" for a Combined Work means the
object code and/or source code for the Application, including any data
and utility programs needed for reproducing the Combined Work from the
Application, but excluding the System Libraries of the Combined Work.

  1. Exception to Section 3 of the GNU GPL.

  You may convey a covered work under sections 3 and 4 of this License
without being bound by section 3 of the GNU GPL.

  2. Conveying Modified Versions.

  If you modify a copy of the Library, and, in your modifications, a
facility refers to a function or data to be supplied by an Application
that uses the facility (other than as an argument passed when the
facility is invoked), then you may convey a copy of the modified
version:

   a) under this License, provided that you make a good faith effort to
   ensure that, in the event an Application does not supply the
   function or data, the facility still operates, and performs
   whatever part of its purpose remains meaningful, or

   b) under the GNU GPL, with none of the additional permissions of
   this License applicable to that copy.

  3. Object Code Incorporating Material from Library Header Files.

  The object code form of an Application may incorporate material from
a header file that is part of the Library.  You may convey such object
code under terms of your choice, provided that, if the incorporated
material is not limited to numerical parameters, data structure
layouts and accessors, or small macros, inline functions and templates
(ten or fewer lines in length), you do both of the following:

   a) Give prominent notice with each copy of the object code that the
   Library is used in it and that the Library and its use are
   covered by this License.

   b) Accompany the object code with a copy of the GNU GPL and this
   license document.

  4. Combined Works.

  You may convey a Combined Work under terms of your choice that,
taken together, effectively do not restrict modification of the
portions of the Library contained in the Combined Work and reverse
engineering for debugging such modifications, if you also do each of
the following:

   a) Give prominent notice with each copy of the Combined Work that
   the Library is used in it and that the Library and its use are
   covered by this License.

   b) Accompany the Combined Work with a copy of the GNU GPL and this
   license document.

   c) For a Combined Work that displays copyright notices during
   execution, include the copyright notice for the Library among
   these notices, as well as a reference directing the user to the
   copies of the GNU GPL and this license document.

   d) Do one of the following:

       0) Convey the Minimal Corresponding Source under the terms of this
       License, and the Corresponding Application Code in a form
       suitable for, and under terms that permit, the user to
       recombine or relink the Application with a modified version of
       the Linked Version to produce a modified Combined Work, in the
       manner specified by section 6 of the GNU GPL for conveying
       Corresponding Source.

       1) Use a suitable shared library mechanism for linking with the
       Library.  A suitable mechanism is one that (a) uses at run time
       a copy of the Library already present on the user's computer
       system, and (b) will operate properly with a modified version
       of the Library that is interface-compatible with the Linked
       Version.

   e) Provide Installation Information, but only if you would otherwise
   be required to provide such information under section 6 of the
   GNU GPL, and only to the extent that such information is
   necessary to install and execute a modified version of the
   Combined Work produced by recombining or relinking the
   Application with a modified version of the Linked Version. (If
   you use option 4d0, the Installation Information must accompany
   the Minimal Corresponding Source and Corresponding Application
   Code. If you use option 4d1, you must provide the Installation
   Information in the manner specified by section 6 of the GNU GPL
   for conveying Corresponding Source.)

  5. Combined Libraries.

  You may place library facilities that are a work based on the
Library side by side in a single library together with other library
facilities that are not Applications and are not covered by this
License, and convey such a combined library under terms of your
choice, if you do both of the following:

   a) Accompany the combined library with a copy of the same work based
   on the Library, uncombined with any other library facilities,
   conveyed under the terms of this License.

   b) Give prominent notice with the combined library that part of it
   is a work based on the Library, and explaining where to find the
   accompanying uncombined form of the same work.

  6. Revised Versions of the GNU Lesser General Public License.

  The Free Software Foundation may publish revised and/or new versions
of the GNU Lesser General Public License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns.

  Each version is given a distinguishing version number. If the
Library as you received it specifies that a certain numbered version
of the GNU Lesser General Public License "or any later version"
applies to it, you have the option of following the terms and
conditions either of that published version or of any later version
published by the Free Software Foundation. If the Library as you
received it does not specify a version number of the GNU Lesser
General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.

  If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is
permanent authorization for you to choose that version for the
Library.

EGENIX.COM PUBLIC LICENSE AGREEMENT                        VERSION 1.1.0

1.  Introduction

    This "License Agreement" is between eGenix.com Software, Skills
    and Services GmbH ("eGenix.com"), having an office at
    Pastor-Loeh-Str. 48, D-40764 Langenfeld, Germany, and the
    Individual or Organization ("Licensee") accessing and otherwise
    using this software in source or binary form and its associated
    documentation ("the Software").

2.  License

    Subject to the terms and conditions of this eGenix.com Public
    License Agreement, eGenix.com hereby grants Licensee a
    non-exclusive, royalty-free, world-wide license to reproduce,
    analyze, test, perform and/or display publicly, prepare derivative
    works, distribute, and otherwise use the Software alone or in any
    derivative version, provided, however, that the eGenix.com Public
    License Agreement is retained in the Software, or in any
    derivative version of the Software prepared by Licensee.

3.  NO WARRANTY

    eGenix.com is making the Software available to Licensee on an "AS
    IS" basis.  SUBJECT TO ANY STATUTORY WARRANTIES WHICH CAN NOT BE
    EXCLUDED, EGENIX.COM MAKES NO REPRESENTATIONS OR WARRANTIES,
    EXPRESS OR IMPLIED.  BY WAY OF EXAMPLE, BUT NOT LIMITATION,
    EGENIX.COM MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY
    OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT
    THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.

4.  LIMITATION OF LIABILITY

    EGENIX.COM SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF
    THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES
    OR LOSS (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF
    BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS
    INFORMATION, OR OTHER PECUNIARY LOSS) AS A RESULT OF USING,
    MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF,
    EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

    SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF
    INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE EXCLUSION OR
    LIMITATION MAY NOT APPLY TO LICENSEE.

5.  Termination

    This License Agreement will automatically terminate upon a
    material breach of its terms and conditions.

6.  Third Party Rights

    Any software or documentation in source or binary form provided
    along with the Software that is associated with a separate license
    agreement is licensed to Licensee under the terms of that license
    agreement. This License Agreement does not apply to those portions
    of the Software. Copies of the third party licenses are included
    in the Software Distribution.

7.  General

    Nothing in this License Agreement affects any statutory rights of
    consumers that cannot be waived or limited by contract.

    Nothing in this License Agreement shall be deemed to create any
    relationship of agency, partnership, or joint venture between
    eGenix.com and Licensee.

    If any provision of this License Agreement shall be unlawful,
    void, or for any reason unenforceable, such provision shall be
    modified to the extent necessary to render it enforceable without
    losing its intent, or, if no such modification is possible, be
    severed from this License Agreement and shall not affect the
    validity and enforceability of the remaining provisions of this
    License Agreement.

    This License Agreement shall be governed by and interpreted in all
    respects by the law of Germany, excluding conflict of law
    provisions. It shall not be governed by the United Nations
    Convention on Contracts for International Sale of Goods.

    This License Agreement does not grant permission to use eGenix.com
    trademarks or trade names in a trademark sense to endorse or
    promote products or services of Licensee, or any third party.

    The controlling language of this License Agreement is English. If
    Licensee has received a translation into another language, it has
    been provided for Licensee's convenience only.

8.  Agreement

    By downloading, copying, installing or otherwise using the
    Software, Licensee agrees to be bound by the terms and conditions
    of this License Agreement.


    For question regarding this License Agreement, please write to:

              eGenix.com Software, Skills and Services GmbH
              Pastor-Loeh-Str. 48
              D-40764 Langenfeld
              Germany

This is omniORB 4.1.6.

omniORB is copyright Apasphere Ltd, AT&T Laboratories Cambridge and
others. It is free software. The programs in omniORB are distributed
under the GNU General Public Licence as published by the Free Software
Foundation. See the file COPYING for copying permission of these
programs. The libraries in omniORB are distributed under the GNU
Lesser General Public Licence. See the file COPYING.LIB for copying
permission of these libraries.

We impose no restriction on the use of the IDL compiler output. The
stub code produced by the IDL compiler is not considered a derived
work of it.

Pexpect Copyright © 2008 Noah Spurrier

Permission is hereby granted, free of charge, to any person obtaining a 
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
USE OR OTHER DEALINGS IN THE SOFTWARE.

http://pexpect.sourceforge.net/

Copyright © 2006 Sébastien Gruhier (http://xilinus.com, http://itseb.com)

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Copyright © 2005-2010 Sam Stephenson

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Copyright (c) 2005-2008 Thomas Fuchs (http://script.aculo.us, http://mir.aculo.us)

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

http://madrobby.github.com/scriptaculous/license/