Activation Record Sample Clauses

Activation Record. An activation record is where a C subroutine stores its local data, saved registers and return address, etc. A typical DSP563CCC activation record consists of the following elements and is illustrated in Figure 4-2 1. Parameter data space. Information passed to C subroutines is stored in a parameter data space which is similar to the local data space (see Figure 4-2). However, the data is in reverse order and each parameter is referenced via a negative offset from the stack pointer. Actual parameters are pushed onto the activation record in reverse order by the calling subroutine. 2. Return address — which is pushed on the DSP’s system stack high (ssh) register. This is the return address to the calling subroutine. The return Program Area 3. address is not saved for subroutines that have been determined to be a leaf. A leaf subroutine is one that makes no subroutine calls. 4. Local data space. The location of C variables that have a lifetime that extends only as long as the subroutine is active and that could not be explicitly promoted to register storage class by the optimizer. 5. Register spill and compiler temporary space. This area is utilized by the compiler to store intermediate results and preserve registers.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs

Related to Activation Record

  • Education Record An education record as defined in the Family Educational Rights and Privacy Act and its implementing regulations, 20 U.S.C. 1232g and 34 C.F.R. Part 99, respectively.

  • Education Records Educational Records are official records, files and data directly related to a student and maintained by the school or local education agency, including but not limited to, records encompassing all the material kept in the student’s cumulative folder, such as general identifying data, records of attendance and of academic work completed, records of achievement, and results of evaluative tests, health data, disciplinary status, test protocols and individualized education programs. For purposes of this DPA, Education Records are referred to as Student Data. Personally Identifiable Information (PII): The terms “Personally Identifiable Information” or “PII” has the same meaning as that found in U.C.A § 53E-9-301, and includes both direct identifiers (such as a student’s or other family member’s name, address, student number, or biometric number) and indirect identifiers (such as a student’s date of birth, place of birth, or mother’s maiden name). Indirect identifiers that constitute PII also include metadata or other information that, alone or in combination, is linked or linkable to a specific student that would allow a reasonable person in the school community, who does not have personal knowledge of the relevant circumstances, to identify the student with reasonable certainty. For purposes of this DPA, Personally Identifiable Information shall include the categories of information listed in the definition of Student Data.

  • Activation We will notify the Xxxxxx of your request to receive electronic billing information. The presentment of your first electronic bill may vary from Xxxxxx to Xxxxxx and may take up to sixty (60) days, depending on the billing cycle of each Xxxxxx. While your electronic bill feature is being activated it is your responsibility to keep your accounts current. Each electronic Xxxxxx reserves the right to accept or deny your request to receive electronic bills.

  • Electronic Visit Verification ("EVV A. To ensure: 1. the EVV system is used to verify the provision of services governed under 40 TAC, Chapter 68 or its successor; 2. only authorized people access the Contractor's EVV account; 3. all data elements required by HHSC or HHSC's designee are uploaded or entered and maintained in the EVV system completely, accurately, and prior to submitting the claim; 4. that each time services governed by 40 TAC Chapter 68 or its successor are delivered to an individual, the Contractor's staff uses an HHSC-approved EVV system; and 5. service delivery documentation is immediately available for review by HHSC when requested. B. Equipment provided to Contractor by HHSC, HHSC’s designee, or an HHSC-approved EVV vendor, must be returned in good condition when the equipment is no longer needed under this Contract. In the context of this agreement, “good condition” means Contractor must not place any marks or identifying information on the equipment and may not alter information on the equipment including logos and serial numbers. If the equipment is lost, stolen, marked, altered or damaged by Contractor, Contractor may be required to pay the replacement cost for each piece of equipment that is lost, stolen, marked or damaged. Replacement costs for lost, stolen, marked or damaged equipment may be assessed periodically. If Contractor recovers previously lost or stolen equipment for which Contractor paid the replacement cost in the prior 12 months, Contractor may return the equipment and be reimbursed for the replacement costs within 12 months of the date HHSC, HHSC’s designee or an HHSC-approved EVV vendor (as applicable) received payment in full from the Contractor. This is provided the equipment is returned in good condition as specified above. C. HHSC may perform EVV compliance oversight reviews to determine if Contractor has complied with EVV compliance requirements as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC EVV website or EVV Policy Handbook. D. If the Contractor determines an electronic record in the EVV system needs to be adjusted at any time, the Contractor will make the adjustment in the EVV system using the most appropriate EVV reason code number(s), EVV reason code description(s) and enter any required free text when completing visit maintenance in the EVV system, if applicable. E. Contractor must begin using an HHSC-approved EVV system prior to submitting an EVV relevant claim. F. All claims for services required to use EVV (EVV claims) must match to an accepted EVV visit transaction in the EVV Aggregator (the state’s centralized EVV database) prior to reimbursement of an EVV claim. Without a matching accepted EVV visit transaction, the claim will be denied. G. Contractor must submit all EVV related claims through the Texas Medicaid Claims Administrator, or as otherwise described in the EVV Policy posted on the HHSC EVV website or in the EVV Policy Handbook. H. Contractor must complete all required EVV training as outlined in the EVV Policy posted on the HHSC EVV website or EVV Policy Handbook: • Prior to using either an EVV vendor system or an EVV proprietary system and • Yearly thereafter. I. Contractor and, if applicable, the Contractor’s appointed EVV system administrator, must complete, sign and date the EVV Onboarding Form as outlined in 40 TAC Chapter 68 or its successor, EVV Policy posted on the HHSC website or EVV Policy Handbook.

  • XXX Hosting 10.1 XXX Hosting is not required for resale in the BellSouth region.

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

  • Electronic invoicing The WAWF system provides the method to electronically process vendor payment requests and receiving reports, as authorized by Defense Federal Acquisition Regulation Supplement (DFARS) 252.232- 7003, Electronic Submission of Payment Requests and Receiving Reports.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization.

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