ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to NGTelecom via CONNECT: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 ODUF will be distributed to Image Access 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 (one hundred seventy-five (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 (1) dataset per workday per OCN. If BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to OneTone 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 (one hundred seventy-five (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
ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to Metro Teleconnect 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 BellSouth determines the Secure FTP Mailbox is nearing capacity levels, BellSouth may move the customer to CONNECT:Direct file delivery.
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.
ODUF Physical File Characteristics. 6.2.1 The ODUF will be distributed to Direct Telephone via CONNECT:Direct, Connect: Enterprise Client or another mutually agreed medium. The ODUF feed will be a variable block format (2476) with an LRECL of 2472. 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 ODUF will be distributed to National Telecom 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 (one hundred seventy-five (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 (1) 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.
ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to Universal Telecom, Inc 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 (one hundred seventy-five (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 willbe addressed during negotiations of thesdtiributionmedium.There will be a maximum of one (1) dataset per workday per OCN. If AT&T determines the Secure FTPMailbox is nearing capacity levels, AT&T maymove the customer to CONNECT:Direct file delivery.
ODUF Physical File Characteristics. 6.2.1 ODUF will be distributed to Momentum via CONNECT: Direct. 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 BellSouth determines that CONNECT: Direct is nearing capacity levels, BellSouth may move Momentum to Secure File Transfer Protocol (FTP) Mailbox delivery, and the purchase of any FTP software will be the responsibility of Momentum.
