CPUs Sample Clauses

CPUs. Each core is recognized as a CPU. For computers that have more than 8 CPUs, additional Computer licenses must be purchased based upon the amount of CPUs that you are using. For example, if you are using Hyperion Data Integration Management on 12 CPUs, you need to purchase 2 Computer licenses; if you are using Hyperion Data Integration Management on 17 CPUs, you need to purchase 3 Computer licenses. These programs may be used solely in connection with moving data into and out of a Hyperion Data Store(s) (data/metadata repository(ies) delivered with the Hyperion programs.) These programs may not be used to extract data from a non-Hyperion Data Store(s) to load a custom data warehouse (a data warehouse not built solely from data from a Hyperion Data Store(s). The Hyperion Data Integration Management Computer license allows for such program to 1) connect to the following relational databases only: Oracle, Sybase, IBM DB2, MS SQL Server and 2) source from and write to an unlimited number of flat file/XML files. Hyperion Data Integration Management Adapters for SAP BW, SAP R3, PeopleSoft and Siebel must be licensed separately to allow Hyperion Data Integration Management to connect to these additional sources. • When you purchase a license for the Data Warehouse Business Adapter program you must have the appropriate licenses for each operational application used as a source (e.g., Oracle, SAP, PeopleSoft, Siebel). A license to the Data Warehouse Adapter program does not provide a license or the right to use the operational applications, a license to the Data Warehouse Adapter program provides only a connector to them. • Application licensing prerequisites as specified in the Applications Licensing Table which may be accessed at xxxx://xxxxxx. com/con tracts. • The number of Hyperion program option licenses must match the number of licenses of the associated Hyperion program. • The license for the Hyperion Planning – System 9 programs includes a limited use license for both the Hyperion Essbase – System 9 and Hyperion Financial Reporting – System 9 programs. Such limited use license means that the Hyperion Essbase – System 9 and Hyperion Financial Reporting – System 9 programs may only be used to access data from the Hyperion Planning – System 9 program. Specifically, the Hyperion Essbase – System 9 program cannot be used to create Essbase cubes that do not contain data used by the Hyperion Planning – System 9 program and the Aggregate Storage option component of...
Sample 1
AutoNDA by SimpleDocs
CPUs. ‌ A CPU orchestrates the execution of the objects which are deployed on it. It provides facilities for scheduling threads, and delegating operation calls to appropriate object processes. The CPU infrastructure process can be seen in Figure 10. The VrtCpu process is parametrised over an identifier for the CPU, and finite set depl that contains a record of all the deployed objects. The single state variable lastThr holds the previously allocated thread identifier; it is incremented each time a new thread is created. This is a simplistic semantics for thread identified allocation, and could be replaced with a more sophisticated algorithm that similarly ensures uniqueness. The CPU process has three actions that define the behaviour of the thread scheduler (ThrSched), thread identifier manager (ThrMgr ) and the operation call manager (Op- Mgr ). The thread scheduler ThrSched simply ensures that only one thread is active at a time by offering exec events, and then awaiting a yield event which must come from the same thread. The thread identifier manager offers a new identifier over newThr by incrementing lastThr; following this, it also increments the state variable. The behaviour  →  OpMgr = µ X • call?(o, f , c) → lCall!(o, f , c) X depl  a o ∈ d rCall.cpu!mk-BusCallMsg(o, f , c) → X  →  Q ret?(p, t, v) → depl lRet!(p, t, v) X .cpu! BusRetMsg(p, t, v) → X rRaet p ∈ mk-d  Q cCall.cpu?mk-BusCallMsg(o, f , c) → lCall!(o, f , c) → X Q cRet.cpu?mk-BusRetMsg(p, t, v) → lRet!(p, t, v) → X Table 8: Operation call and return manager of the operation manager is rather more involved, and thus it is expanded in Table 8, which we describe shortly. The CPU process main action interleaves the behaviour of ThrSched, ThrMgr, and Op- Mgr. Thus, composing a suitably instantiated CPU process with a collection of deployed objects allows the CPU to orchestrate the execution of the objects. Such an instantiation and composition is illustrated in Section 4.9. ∈ The operation manager is shown in Table 8. It consists of a recursive external choice over various possibilities for calls to and returns from object processes and busses. The first two cases deal with local operation call and return requests. The first possibility is the receipt of a call request from a local deployed object on channel call, which provides an object identifier o, operation identifier f , and call information c. If the object to be called is deployed locally (o depl) then the call is simply passed on t...
Sample 1
CPUs. The CyberGraph- ics Font Software may not be shared between locations or business entities. Each additional location and/or entity must purchase a separate license to be used in accordance with the terms of the CyberGraphics Font Software License. License upgrades may be purchased for use with additional devices. The upgrade price is calculated as a percentage of the original price of the software. To determine the number of devices, add up all CPUs, workstations, printers, and other devices that use the fonts. The following is cumulative: 1 - 6 devices (standard license) 7 -12 devices: add 50 percent 13-60 devices: add 20% for each 6 devices 61-150 devices: add 15% for each 6 devices 151-300 devices: add 10% for each 6 devices over 300 devices: add 5% for each 6 devices Very large or unlimited uses of the CyberGraphics Font Software will require a custom license agreement. Some states or jurisdictions do not allow the exclusion or limitations of implied warranties and incidental, consequential or special damages. The exclusions or limitations contained in the CyberGraphics Font Soft- xxxx License Agreement may not apply to you. Restrictions to exclusions and/or limitations of the Cyber- Graphics Font Software License Agreement shall only be effective to the minimum extent permitted by your state or jurisdiction and only if required by your state or jurisdiction. Under no circumstances shall the exclusions and/or limitations of the CyberGraphics Font Software License Agreement be greater than thirty
Sample 1
CPUs. This Workgroup license description supersedes any definition or terms of use for CPU licenses stated in the Agreement, Exhibit A or purchase order. For the avoidance of doubt, each copy of the Jaguar CTS® component of the Program is also limited to use by a maximum of two (2) CPUs on one (1) Machine only. Jaguar CTS may be accessed and used by (a) an unlimited number of “Internet Seats” (i.e., external Seats outside your organization accessing the Program via the Internet) and (b) by an unlimited number of internal Seats (meaning your employees and contractors) using Jaguar CTS on such Machine in connection with their performance of duties for you.
Sample 1
CPUs. All fractions of a number are to be rounded up to the next whole number. This definition only applies to those programs with “BEA” in the program name.
Sample 1
CPUs. (3.1.1) The utilisation of all CPUs (servers, clients) processors is less than 20% under normal operating conditions at take-over.
Sample 1

Related to CPUs

  • Vesting Dates The ISOs shall vest as follows, subject to earlier vesting in the event of a termination of Service as provided in Section 6 or a Change in Control as provided in Section 7: ISOs for

  • Performance Vesting Within sixty (60) days following the completion of the Performance Period, the Plan Administrator shall determine the applicable number of Performance Shares in accordance with the provisions of the Award Notice and Schedule I attached thereto.

  • Performance Shares The Performance Shares earned by the Grantee will be determined and delivered to the Grantee as soon as practicable subsequent to the determination of the Corporation’s financial results for the Performance Cycle and approval by the Plan Administrator. The corresponding shares of the Corporation’s common stock will be purchased on the open market.

  • Performance Stock Units The Company may grant to Executive performance stock units (“PSUs”) pursuant to the Incentive Plan. All PSUs are subject to and conditioned on approval of the grant and its terms by the Board. All granted PSUs shall vest as provided in the applicable PSU grant notice and grant agreement (“PSU Agreement”). All PSUs shall be subject to the terms and conditions of the Incentive Plan and a PSU Agreement in a form prescribed by the Company, which Executive must sign as a condition to receiving the PSUs.

  • Performance Units Subject to the limitations set forth in paragraph (c) hereof, the Committee may in its discretion grant Performance Units to any Eligible Person and shall evidence such grant in an Award Agreement that is delivered to the Participant which sets forth the terms and conditions of the Award.

  • Vesting Date All remaining shares of Restricted Stock will become vested on the Vesting Date.

  • Award of Performance Stock Units The Company hereby grants to you, effective as of the Grant Date, an Award of Performance Stock Units for that number of Performance Stock Units communicated to you and set forth in the Company’s records (the “PSUs”), on the terms and conditions set forth in such communication, this Agreement and the Plan. Each PSU represents the right to receive one share of Stock, subject to the terms and conditions set forth herein.

  • Vesting and Lapse of Restrictions Subject to Sections 2.2(a) and 2.2(c), the Award shall vest and Restrictions shall lapse in accordance with the vesting schedule set forth on the Grant Notice.

  • RSUs The Continuing Stock Units shall continue to vest in accordance with the terms of the Original RSU Award Documents, on the same basis as such stock units would have become vested if Executive had remained employed under this Agreement through the Scheduled Expiration Date. Except as otherwise expressly provided herein, all such Continuing Stock Units shall be subject to, and administered in accordance with, the Original RSU Award Documents. Any of Executive’s restricted stock unit awards that have not become vested on or before the Termination Date, and that are outstanding at the Termination Date, but which are not Continuing Stock Units, shall automatically terminate on the Termination Date. Notwithstanding any term or provision of the Original RSU Award Documents:

  • Service Vesting Except as otherwise provided in this Section 3, the Restricted Shares will be forfeited as to the unvested portion of the Award if the Participant does not remain continuously in the employment of the Company through the specified lapsing dates set forth in Section 2 above.

Time is Money Join Law Insider Premium to draft better contracts faster.