PC Keys Sample Clauses

PC Keys. The ―PC keys‖ function is designed to generate RSA key pair files in S4_RSA_PUBLIC_KEY and S4_RSA_PRIVATE_KEY format on the local computer and download them to the hardware or for other purposes. Choose the directory where the files are to be saved, fill in the ―public key file name‖ and ―private key file name‖ and then click the ―Generate‖ button to generate specified key pairs by software as shown in Figure 6-10;
AutoNDA by SimpleDocs

Related to PC Keys

  • Viewing By strict appointment through the selling Agents, JD Commercial, 00 Xxxxxxxx Xxxxx, Bideford, North Devon. EX39 1TW TEL: (01237) 424053 / 07868 846357 E-MAIL: xxxxx@xx-xxxxxxxxxx.xx.xx JD COMMERCIAL, 00 XXXXXXXX XXXXX, website : xxx.xx-xxxxxxxxxx.xx.xx BIDEFORD, NORTH DEVON, EX39 1TW email : xxxxx@xx-xxxxxxxxxx.xx.xx

  • EXTRADITION Treaty on extradition. Signed at Buenos Aires June 10, 1997; entered into force June 15, 2000. TIAS ; 2159 UNTS 129. FINANCE Agreement relating to investment guaranties under section 413(b)(4) of the Mutual Security Act of 1954, as amended. Signed at Buenos Aires December 22, 1959; entered into force provisionally December 22, 1959; definitively May 5, 1961. 12 UST 955; TIAS 4799; 411 UNTS 41. Agreement regarding the consolidation and re- scheduling of certain debts owed to, xxxxxx- xxxx by or insured by the United States Gov- ernment and its agencies, with annexes. Signed at Buenos Aires April 8, 1986; entered into force May 19, 1986. NP Swap agreement between the United States Treasury and the Central Bank of the Argen- tine Republic/Government of the Argentine Republic, with related letter and amendment. Signed at Washington and Buenos Aires Feb- ruary 23, 1988; entered into force February 23, 1988. TIAS Swap agreement between the United States Treasury, the Central Bank of the Argentine Republic/Government of the Argentine Repub- lic, with memorandum of understanding. Signed at Washington and Buenos Aires Octo- ber 19, 1988; entered into force October 19, 1988. TIAS Agreement regarding the consolidation and re- scheduling or refinancing of certain debts owed to, guaranteed by, or insured by the United States Government and its agencies, with annexes. Signed at Buenos Aires Decem- ber 14, 1989; entered into force January 22, 1990. NP Agreement regarding the consolidation and re- scheduling of certain debts owed to, xxxxxx- xxxx by, or insured by the United States Gov- ernment and its agencies, with annexes. Signed at Buenos Aires December 5, 1990; entered into force January 16, 1991. NP Agreement regarding the consolidation and re- scheduling or refinancing of certain debts owed to, guaranteed by or insured by the United States Government and its agencies, with annexes. Signed at Washington December 6, 1991; entered into force February 10, 1992. NP Agreement regarding the consolidation and re- scheduling of certain debts owed to, xxxxxx- xxxx by or insured by the United States Gov- ernment and its agencies, with annexes. Signed at Washington January 13, 1993; entered into force March 8, 1993. NP Agreement regarding the reduction of certain debts related to foreign assistance owed to the Government of the United States and its agen- cies, with appendices. Signed at Washington and Buenos Aires January 13 and 15, 1993; entered into force February 14, 1993. NP

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • Access to Personnel Records (a) Upon receiving the permission of the Chief Constable or designate, an employee may review the contents of his or her personnel file provided that such review is in the presence of a person authorized for such a purpose by the Chief Constable.

  • Project Records ‌ As further described below, Project records include but are not limited to Grantee, financial, and voucher records. All Project records must be retained for a period of three (3) years after final payment under this Grant. All Project records are subject to audit pursuant to Section P of this Grant Agreement. Upon completion of the third year of record retention, the Grantee shall submit all Project records to CARB. Hardcopy of electronic records are suitable. Acceptable forms of electronic media include hard drives, CDs, DVDs, and flash drives. Other forms of electronic media may be allowed based on prior written concurrence from CARB.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Access to Personnel Files All employees shall be allowed access to their personnel files during normal working hours for inspection and/or copies of documents which will be provided by the Employer. Such inspection shall be made subject to prior arrangement with the Employer.

  • Contractor Key Personnel ‌ The Contractor shall assign a Corporate OASIS Program Manager (COPM) and Corporate OASIS Contract Manager (COCM) as Contractor Key Personnel to represent the Contractor as primary points-of-contact to resolve issues, perform administrative duties, and other functions that may arise relating to OASIS and task orders solicited and awarded under XXXXX. Additional Key Personnel requirements may be designated by the OCO at the task order level. There is no minimum qualification requirements established for Contractor Key Personnel. Additionally, Contractor Key Personnel do not have to be full-time positions; however, the Contractor Key Personnel are expected to be fully proficient in the performance of their duties. The Contractor shall ensure that the OASIS CO has current point-of-contact information for both the COPM and COCM. In the event of a change to Contractor Key Personnel, the Contractor shall notify the OASIS CO and provide all Point of Contact information for the new Key Personnel within 5 calendar days of the change. All costs associated with Contractor Key Personnel duties shall be handled in accordance with the Contractor’s standard accounting practices; however, no costs for Contractor Key Personnel may be billed to the OASIS Program Office. Failure of Contractor Key Personnel to effectively and efficiently perform their duties will be construed as conduct detrimental to contract performance and may result in activation of Dormant Status and/or Off-Ramping (See Sections H.16. and H.17.).

  • Employee Access to Personnel File An employee shall have the right to read and review his/her personnel file on reasonable notice and by written request to the Human Resources Manager. An employee may request and shall receive a copy of any record or document contained in the employee’s personnel file.

Time is Money Join Law Insider Premium to draft better contracts faster.