Serial Number File Sample Clauses

Serial Number File. This edit box shows the currently selected Serial Number File, or else indicates "None Selected". If you try to select a nonexistent file, the selection will revert to "None Selected". On startup the edit box, by default, shows the filename that was in effect the last time the QUIT button was clicked. You can select a new Serial Number File in the following ways: • Single Click - Lets you directly edit the filename in the edit box. Pressing Enter will check for the existence of the file. If not found, the selected file gets set to "None Selected". If the file exists, the serial number and its properties are displayed on screen. • Double Click or …Click - Opens a standard file browser and lets you 68 Cyclone for STMicro - User Manual choose from existing files by disk, directory, name, and extension.
View SourceView Similar (2)

Related to Serial Number File

  • Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.

  • ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery. 6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC. 6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.

  • SCHEDULE OF RESERVED NAMES Except to the extent that ICANN otherwise expressly authorizes in writing, and subject to the terms and conditions of this Specification, Registry Operator shall reserve the following labels from initial (i.e., other than renewal) registration within the TLD. If using self-­‐allocation, the Registry Operator must show the registration in the RDDS. In the case of IDN names (as indicated below), IDN variants will be identified according to the registry operator IDN registration policy, where applicable.

  • Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to CLEC-1 via an agreed medium with CONNECT:Direct being the preferred transport method. The Daily Usage Feed will be a variable block format (2476) with an LRECL of 2472. The data on the Daily Usage Feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. 6.2.2 Data circuits (private line or dial-up) may be required between BellSouth and CLEC-1 for the purpose of data transmission. Where a dedicated line is required, CLEC-1 will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. CLEC-1 will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit successfully ongoing will be negotiated on a case by case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to CLEC-1. Additionally, all message toll charges associated with the use of the dial circuit by CLEC-1 will be the responsibility of CLEC-1. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the parties. All equipment, including modems and software, that is required on CLEC-1 end for the purpose of data transmission will be the responsibility of CLEC-1.

  • Local Number Portability The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. PNP is currently being worked in industry forums. The results of these forums will dictate the industry direction of PNP. BellSouth will provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.