Clearing Functions Sample Clauses

Clearing Functions. The clearing functions enable the Customer and their clients to manage position information. These functions are made available via a GUI. This enables back offices to correctly record, report, manage and reconcile their open interest. These functions also provide end users with a number of reports. The functions available are: • Position keeping — the automatic maintenance of positions as post-trade functions are performed • Position search — the ability to review current and historical position data • Settlement instruction entry, edit and search — the management of long and short positions • Position transfer instruction entry, edit and search — the movement of volume between position accounts • Exercise instruction entry, edit and search — nomination of options positions for exercise • Automatic Exercise instruction edit and search — position selection criteria for options expiry processing • Tender Deletion instruction entry, edit and search — manual deletion of positions awaiting delivery Commercial in Confidence • Margin Exclusion Instruction entry, edit and search — manual omission of delivery positions from margin calculationDelivery instruction entry edit and search — manual early notification of an intention to deliver
AutoNDA by SimpleDocs
Clearing Functions. 5.1 All clearing functions, including order tickets, time stamps, confirmations and statement generation shall be conducted by the Clearing Firm or such other clearing operation (including Web Street, should it become self-clearing) as Web Street may in its sole discretion designate.

Related to Clearing Functions

  • CERTIFYING FUNCTION Department of Information Resources acting as the owner of the DIR Contracts hereby certifies the eligibility of the DIR Customer to use the DIR Contracts.

  • MANAGEMENT FUNCTIONS B.1 The Association recognizes that the management of the Hospital and the direction of working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement and, without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to: (a) maintain order, discipline and efficiency; (b) hire, assign, retire, discharge, direct, promote, demote, classify, transfer, lay- off, recall, and suspend or otherwise discipline nurses, provided that a claim of discharge or discipline without just cause may be the subject of a grievance and dealt with as hereinafter provided; (c) determine, in the interest of efficient operation and high standards of service, job rating and classification, the hours of work, work assignments, methods of doing the work, and the working establishment for the service; (d) generally to manage the operation that the Hospital is engaged in and, without restricting the generality of the foregoing, to determine the number of personnel required, methods, procedures, and equipment in connection therewith; (e) make, enforce, and alter from time to time reasonable rules and regulations to be observed by the nurses which are not inconsistent with the provisions of this Agreement. B.2 These rights shall not be exercised in a manner inconsistent with the provisions of this Agreement.

  • CUSTOMER SERVICE FUNCTIONS The Servicer shall handle all Customer inquiries and other Customer service matters according to the same procedures it uses to service Customers with respect to its own charges.

  • MIXED FUNCTIONS An employee engaged for more than two hours during one day or shift on duties carrying a higher rate than his or her ordinary classification shall be paid the higher rate for such day or shift. If for two hours or less during one day or shift he or she shall be paid the higher rate for the time so worked.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Additional Functions Upon receipt of Proper Instructions, the Custodian shall take all such other actions as specified in such Proper Instructions and as shall be reasonable or necessary with respect to Repurchase Agreement transactions and the Securities and funds transferred and received pursuant to such transactions, including, without limitation, all such actions as shall be prescribed in the event of a default under a Repurchase Agreement.

  • Duties and functions 23.2.1 The Independent Engineer shall discharge its duties and functions substantially in accordance with the terms of reference set forth in Schedule 16. 23.2.2 The Independent Engineer shall submit regular periodic reports (at least once every month) to the Authority in respect of its duties and functions set forth in Schedule 16.

  • Training Fund Employers and/or individuals who manage, operate, assist or own, either partially or wholly, a company or companies working non-union in the construction industry on Mainland Nova Scotia within the craft jurisdiction of xxx Xxxxxxxxxx Local 83 shall not be eligible to be appointed to serve, or to continue to serve, as trustees on any trust fund referred to within this Collective Agreement. This provision shall apply to management trustees and union trustees alike. 30.01 Subject to the approval of xxx Xxxxxxxxxx Joint Training Fund Trustees, direct costs for upgrading the safety training of Union members described in Article 2.01 of this Agreement in Occupational Health and Safety courses required by Nova Scotia law, shall be paid by the fund.

  • Performance of Government Functions Nothing contained in this contract shall be deemed or construed so as to in any way estop, limit, or impair the City from exercising or performing any regulatory, policing, legislative, governmental, or other powers or functions.

  • Future Functionality You agree that Your purchases are not contingent on the delivery of any future functionality or features, or dependent on any oral or written public comments made by Us regarding future functionality or features.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!