File Search Reports File search reports have been obtained from each Uniform Commercial Code filing office identified with respect to such Grantor in Section 2 hereof, and such search reports reflect no liens against any of the Collateral other than those permitted under the Credit Agreement.
NOTIFICATIONS AND SUBMISSION OF REPORTS Unless otherwise stated in writing after the Effective Date, all notifications and reports required under this IA shall be submitted to the following entities: Administrative and Civil Remedies Branch Office of Counsel to the Inspector General Office of Inspector General U.S. Department of Health and Human Services ▇▇▇▇▇ Building, Room 5527 ▇▇▇ ▇▇▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇ Telephone: (▇▇▇) ▇▇▇-▇▇▇▇ Facsimile: (▇▇▇) ▇▇▇-▇▇▇▇ LFAC: ▇▇▇▇▇▇▇ ▇. ▇▇▇▇▇, DPM ▇▇▇▇ ▇▇▇▇▇▇▇▇▇▇▇ ▇▇. ▇-▇▇▇ ▇▇▇▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇ Telephone: (▇▇▇) ▇▇▇-▇▇▇▇ Email: ▇▇.▇▇▇▇▇@▇▇▇▇▇.▇▇▇ Unless otherwise specified, all notifications and reports required by this IA may be made by electronic mail, overnight mail, hand delivery, or other means, provided that there is proof that such notification was received. Upon request by OIG, LFAC may be required to provide OIG with an additional copy of each notification or report required by this IA in OIG’s requested format (electronic or paper).
Preparation of Reports The Servicer shall prepare and deliver such additional reports as required under this Agreement, including a copy of each Semi-Annual Servicer’s Certificate described in Section 4.01(c)(ii), the annual Servicer’s Regulation AB Certificate described in Section 3.03, and the Annual Accountant’s Report described in Section 3.04. In addition, the Servicer shall prepare, procure, deliver and/or file, or cause to be prepared, procured, delivered or filed, any reports, attestations, exhibits, certificates or other documents required to be delivered or filed with the SEC (and/or any other Governmental Authority) by the Issuer or the Depositor under the federal securities or other applicable laws or in accordance with the Basic Documents, including, but without limiting the generality of foregoing, filing with the SEC, if applicable and required by applicable law, a copy or copies of (i) the Monthly Servicer’s Certificates described in Section 3.01(b)(i) (under Form 10-D or any other applicable form), (ii) the Semi-Annual Servicer’s Certificates described in Section 4.01(c)(ii) (under Form 10-D or any other applicable form), (iii) the annual statements of compliance, attestation reports and other certificates described in Section 3.03, and (iv) the Annual Accountant’s Report (and any attestation required under Regulation AB) described in Section 3.04. In addition, the appropriate officer or officers of the Servicer shall (in its separate capacity as Servicer) sign the Depositor’s annual report on Form 10-K (and any other applicable SEC or other reports, attestations, certifications and other documents), to the extent that the Servicer’s signature is required by, and consistent with, the federal securities laws and/or any other applicable law.
SUBMISSION OF REPORTS All applicable study reports shall be submitted in preliminary form for approval by the State before a final report is issued. The State's comments on the Engineer's preliminary report must be addressed in the final report.
File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.