Common use of ODUF Physical File Characteristics Clause in Contracts

ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to NuVox via CONNECT: Direct, Connect: Enterprise Client or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to NuVox via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox SPARDI via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox SUN-TEL via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox NuStar via CONNECT: Direct, Connect: Enterprise Client :Direct or Secure File Transfer Protocol (FTP) or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox Cutting Edge via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox Gateway via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox ALTICOMM via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 7.2.1 ODUF will be distributed to NuVox Spectrotel via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox Access Point via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox Xxxx via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox VMT via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. The ODUF feed will be a variable block formatformat (2476) with an LRECL of 2472. The data on the ODUF feed will be in a non-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.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox Easy Telephone via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. 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.

ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NuVox eXpeTel via CONNECT: :Direct, Connect: Enterprise Client or another mutually agreed medium. 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.