Transfer of Collateral upon Occurrence of Termination Event Upon the occurrence of a Termination Event and the transfer to the Purchase Contract Agent of the Senior Notes, the appropriate Applicable Ownership Interests in the Treasury Portfolio or the Treasury Securities, as the case may be, underlying the Corporate Units and the Treasury Units, as the case may be, pursuant to the terms of the Pledge Agreement, the Purchase Contract Agent shall request transfer instructions with respect to such Senior Notes, the appropriate Applicable Ownership Interests in the Treasury Portfolio or Treasury Securities, as the case may be, from each Holder by written request, substantially in the form of Exhibit D hereto, mailed to such Holder at its address as it appears in the Security Register. Upon book-entry transfer of the Corporate Units or the Treasury Units or delivery of a Corporate Units Certificate or Treasury Units Certificate to the Purchase Contract Agent with such transfer instructions, the Purchase Contract Agent shall transfer the Senior Notes, the appropriate Applicable Ownership Interests in the Treasury Portfolio or Treasury Securities, as the case may be, underlying such Corporate Units or Treasury Units, as the case may be, to such Holder by book-entry transfer, or other appropriate procedures, in accordance with such instructions. In the event a Holder of Corporate Units or Treasury Units fails to effect such transfer or delivery, the Senior Notes, the appropriate Applicable Ownership Interests in the Treasury Portfolio or Treasury Securities, as the case may be, underlying such Corporate Units or Treasury Units, as the case may be, and any distributions thereon, shall be held in the name of the Purchase Contract Agent or its nominee in trust for the benefit of such Holder, until the earlier to occur of: (i) the transfer of such Corporate Units or Treasury Units or surrender of the Corporate Units Certificate or Treasury Units Certificate or the receipt by the Company and the Purchase Contract Agent from such Holder of satisfactory evidence that such Corporate Units Certificate or Treasury Units Certificate has been destroyed, lost or stolen, together with any indemnity that may be required by the Purchase Contract Agent and the Company; and (ii) the expiration of the time period specified in the abandoned property laws of the relevant State in which the Purchase Contract Agent holds such property.
Notification of Error The Trust will notify USBFS of any discrepancy between USBFS and the Trust, including, but not limited to, failing to account for a security position in the Fund’s portfolio, upon the later to occur of: (i) three business days after receipt of any reports rendered by USBFS to the Trust; (ii) three business days after discovery of any error or omission not covered in the balancing or control procedure; or (iii) three business days after receiving notice from any shareholder regarding any such discrepancy.
Notification of Event of Default Borrower shall notify Agent immediately of the occurrence of any Event of Default.
Event of Loss Grantor shall at its expense promptly repair all repairable damage to any tangible Collateral. In the event that any tangible Collateral is damaged beyond repair, lost, totally destroyed or confiscated (an "Event of Loss") and such Collateral had a value prior to such Event of Loss of $25,000.00 or more, then, on or before the first to occur of (i) 90 days after the occurrence of such Event of Loss, or (ii) 10 Business Days after the date on which either Grantor or MLBFS shall receive any proceeds of insurance on account of such Event of Loss, or any underwriter of insurance on such tangible Collateral shall advise either Grantor or MLBFS that it disclaims liability in respect of such Event of Loss, Grantor shall, at Grantor's option, either replace the Collateral subject to such Event of Loss with comparable Collateral free of all liens other than Permitted Liens (in which event Grantor shall be entitled to utilize the proceeds of insurance on account of such Event of Loss for such purpose, and may retain any excess proceeds of such insurance), or pay to MLBFS on account of the Obligations an amount equal to the actual cash value of such Collateral as determined by either the applicable insurance company's payment (plus any applicable deductible) or, in absence of insurance company payment, as reasonably determined by MLBFS. Notwithstanding the foregoing, if at the time of occurrence of such Event of Loss or any time thereafter prior to replacement or payment, as aforesaid, an Event of Default shall have occurred and be continuing hereunder, then MLBFS may at its sole option, exercisable at any time while such Event of Default shall be continuing, require Grantor to either replace such Collateral or make a payment on account of the Obligations, as aforesaid.
Available Relief for a Force Majeure Event 11.7.1 Subject to this Article 11: (a) no Party shall be in breach of its obligations pursuant to this Agreement except to the extent that the performance of its obligations was prevented, hindered or delayed due to a Force Majeure Event; (b) every Party shall be entitled to claim relief in relation to a Force Majeure Event in regard to its obligations, including but not limited to those specified under Article 4.5; (c) For avoidance of doubt, neither Party’s obligation to make payments of money due and payable prior to occurrence of Force Majeure events under this Agreement shall be suspended or excused due to the occurrence of a Force Majeure Event in respect of such Party. (d) Provided that no payments shall be made by either Party affected by a Force Majeure Event for the period of such event on account of its inability to perform its obligations due to such Force Majeure Event.
Assistance in Litigation or Administrative Proceedings Covered Entity shall provide written notice to Business Associate if litigation or administrative proceeding is commenced against Covered Entity, its directors, officers, or employees, based on a claimed violation by Business Associate of HIPAA, the HIPAA Rules or other laws relating to security and privacy or PHI. Upon receipt of such notice and to the extent requested by Covered Entity, Business Associate shall, and shall cause its employees, Subcontractors, or agents assisting Business Associate in the performance of its obligations under the Contract to, assist Covered Entity in the defense of such litigation or proceedings. Business Associate shall, and shall cause its employees, Subcontractor’s and agents to, provide assistance, to Covered Entity, which may include testifying as a witness at such proceedings. Business Associate or any of its employees, Subcontractors or agents shall not be required to provide such assistance if Business Associate is a named adverse party.
Dissolution Event If there is a Dissolution Event before the termination of this Safe, the Investor will automatically be entitled (subject to the liquidation priority set forth in Section 1(d) below) to receive a portion of Proceeds equal to the Cash-Out Amount, due and payable to the Investor immediately prior to the consummation of the Dissolution Event.
Notification of Force Majeure Event 11.5.1 The Affected Party shall give notice to the other Party of any event of Force Majeure as soon as reasonably practicable, but not later than seven (7) days after the date on which such Party knew or should reasonably have known of the commencement of the event of Force Majeure. If an event of Force Majeure results in a breakdown of communications rendering it unreasonable to give notice within the applicable time limit specified herein, then the Party claiming Force Majeure shall give such notice as soon as reasonably practicable after reinstatement of communications, but not later than one (1) day after such reinstatement. Provided that, such notice shall be a pre-condition to the Affected Party’s entitlement to claim relief under this Agreement. Such notice shall include full particulars of the event of Force Majeure, its effects on the Party claiming relief and the remedial measures proposed. The Affected Party shall give the other Party regular reports on the progress of those remedial measures and such other information as the other Party may reasonably request about the Force Majeure. 11.5.2 The Affected Party shall give notice to the other Party of (i) the cessation of the relevant event of Force Majeure; and (ii) the cessation of the effects of such event of Force Majeure on the performance of its rights or obligations/ roles under this Agreement, as soon as practicable after becoming aware of each of these cessations.
Servicer Termination Event For purposes of this Agreement, each of the following shall constitute a “Servicer Termination Event”:
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-‐and-‐ media/announcement-‐2-‐17nov13-‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-‐OARC) <xxxxx://xxx.xxx-‐xxxx.xxx/xxxx/xxxx/xxxx>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
