File Structure Sample Clauses

File Structure. The population of Data Flow files in different use cases is provided in the Online RGMA Data Flow Catalogue as different variations. • Files have been developed with consistent sets of data. This allows RGMA Data Flows to be made up of Data Groups so that changes can be limited to specific Data Groups, rather than being separately applied to each of the RGMA Data Flows. • The Data Groups are the records which are included in the RGMA Data Flow formats. The diagram below illustrates the file structure which consists of: o A header record o Transaction records (followed by a number of associated detail records) o A trailer record. Record Identifer Transaction type Record Identifer Header Transaction TRANSACTION Transaction Trailer Record RECORD Record Data Item Value Data Item Value Data Item Value Separator • Complete Data Groups are used in the definition of the records. The Data Groups include Data Items which, though not required as part of the minimum data, could be used to satisfy commercial arrangements, and to provide extra Data Items which can be populated for exception processing and updates. The use of standard Data Groups means any change can be applied once to the formats, and only the business rules need to be adjusted in the different uses thus minimising the impact of change. The overhead of RGMA Data Flows allowing for data which some organisations will not use, is minimised by having variable length fields and not using field separators which are in the standard set of characters. • Files have a core which can be used by all Market Participants. This allows Suppliers to change their MAM with minimal changes to their records and means of communication, while allowing for commercial additions to the core data resulting in Market Participants being able to provide tailored functionality. • The file will be as one stream of data with the defined codes providing delimiters between Data Items and Data Groups. Any spaces between data and delimiters will be significant. • There is no identified requirement for record sequence numbers, but record sequencing within a transaction is significant.
View SourceView Similar (2)
File Structure. The Producing Party shall produce the following sets of files with 26 each production.
View Source

Related to File Structure

  • 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.

  • 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.

  • SEC Filings and Press Releases To Agent and Lenders, promptly upon their becoming available, copies of: (i) all Financial Statements, reports, notices and proxy statements made publicly available by any Credit Party to its security holders; (ii) all regular and periodic reports and all registration statements and prospectuses, if any, filed by any Credit Party with any securities exchange or with the Securities and Exchange Commission or any governmental or private regulatory authority; and (iii) all press releases and other statements made available by any Credit Party to the public concerning material changes or developments in the business of any such Person.

  • Pre-Closing Tax Returns From and after the Closing, Peabody shall prepare or cause to be prepared all Tax returns required to be filed by the Peabody Transferred Subsidiaries or, other than Tax returns related to Income Taxes, with respect to the Peabody Contributed Assets for any Pre-Closing Tax Period (the “Peabody Prepared Returns”), and Arch shall prepare or cause to be prepared all Tax returns required to be filed by the Arch Transferred Subsidiaries or, other than Tax returns related to Income Taxes, with respect to the Arch Contributed Assets for any Pre-Closing Tax Period (the “Arch Prepared Returns”). Except as otherwise required by applicable Law, each of Peabody and Arch shall prepare such Tax returns in accordance with past practice. Peabody and Arch shall each deliver to the JV Company all Peabody Prepared Returns and Arch Prepared Returns, together with all supporting documentation, no later than ten days prior to the due date for filing such Tax return, and, if any Peabody Prepared Return or any Arch Prepared Return would reasonably be expected to result in or otherwise affect material Taxes of any JV Entity in any Post-Closing Taxable Period, Peabody or Arch, as the case may be, shall also deliver such Tax return, together with all supporting documentation to Arch or Peabody, as the case may be, no later than ten days prior to the due date for filing such Tax return, for review and reasonable comment by the JV Company and Arch or Peabody, as the case may be, and the party filing such Tax return shall incorporate any reasonable comments received no later than five days prior to the due date for filing such Tax return. Peabody and Arch shall use commercially reasonable efforts to determine which of Peabody, Arch or the JV Company shall file such Tax return. If after complying with the immediately preceding sentence in good faith, Peabody and Arch are unable to agree on which of Peabody, Arch or the JV Company is responsible for filing such Tax return, then the JV Company shall be responsible for filing such Tax return. If the JV Company files any Tax return pursuant to this Section 6.21(a)(i) and if such Tax return shows Taxes as due and owing, Peabody or Arch, as applicable, shall pay the amount of Contributor Taxes with respect to such Tax return to the JV Company no later than the due date for filing such Tax return and the JV Company shall remit such Taxes to the applicable Governmental Authority. If either Peabody or Arch files any Tax return pursuant to this Section 6.21(a)(i), such Tax return shows Taxes as due and owing, and such Taxes were specifically included in Peabody Net Working Capital or Arch Net Working Capital, as the case may be, as finally determined pursuant to Section 3.5(c), then the JV Company shall pay the amount of such identified Taxes to Peabody or Arch no later than the due date for filing such Tax return and Peabody or Arch, as the case may be, shall remit such Taxes to the applicable Governmental Authority.

  • Existence; Business and Properties (a) Do or cause to be done all things necessary to preserve, renew and keep in full force and effect its legal existence, except, in the case of a Subsidiary of the Borrower, where the failure to do so would not reasonably be expected to have a Material Adverse Effect, and except as otherwise permitted under Section 6.05, and except for the liquidation or dissolution of Subsidiaries if the assets of such Subsidiaries to the extent they exceed estimated liabilities are acquired by the Borrower or a Wholly Owned Subsidiary of the Borrower in such liquidation or dissolution; provided, that Subsidiary Loan Parties may not be liquidated into Subsidiaries that are not Loan Parties and Domestic Subsidiaries may not be liquidated into Foreign Subsidiaries (except in each case as permitted under Section 6.05). (b) Except where the failure to do so would not reasonably be expected to have a Material Adverse Effect, do or cause to be done all things necessary to (i) lawfully obtain, preserve, renew, extend and keep in full force and effect the permits, franchises, authorizations, Intellectual Property, licenses and rights with respect thereto necessary to the normal conduct of its business, and (ii) at all times maintain, protect and preserve all property necessary to the normal conduct of its business and keep such property in good repair, working order and condition (ordinary wear and tear excepted), from time to time make, or cause to be made, all needful and proper repairs, renewals, additions, improvements and replacements thereto necessary in order that the business carried on in connection therewith, if any, may be properly conducted at all times (in each case except as permitted by this Agreement).