Source and target file and record types - Connect_ETL - 9.13

Connect ETL Data Transformation Language (DTL) Guide
Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect (ETL, Sort, AppMod, Big Data)
Version
9.13
Language
English
Product name
Connect ETL
Title
Connect ETL Data Transformation Language (DTL) Guide
Copyright
2023
First publish date
2003
Last updated
2023-09-11
Published on
2023-09-11T19:01:45.019000

Connect ETL supports the following source and target file types and record types.

File Type/Record Type /INFILE /OUTFILE /INPIPE /OUTPIPE /INBUFFER1 /OUTBUFFER1
STREAM CRLF √ √ √ √ √ √
STLF √ √ √ √ √ √
STCR √ √ √ √ √ √
XML √ √
FIXED √ √ √ √ √ √
VARIABLE √ √ √ √ √ √
VARIABLE LITTLEENDIAN √ √ √ √ √ √
VARIABLE DISTRIBUTABLE √ √ √ √
MFFIXED √ √
MFVARIABLE √ √
MFLINESEQUENTIAL √ √
INDEXED2 √ √
MAINFRAME FIXED √ √ √
MAINFRAME FTPBINARY3 √ √
MAINFRAME VARIABLE √ √ √
MAINFRAME VARIABLE BLOCKED √ √ √
MAINFRAME VARIABLE DISTRIBUTABLE √ √ √
MAINFRAME VSAM4 √
FORTRANUNFORMATTED √ √ √ √ √ √
TABLEAU √
APACHEAVRO √
APACHEPARQUET √
QLIKVIEW √

1 For input and output buffers, Connect ETL supports the record formats that correspond to the specified file types.

For additional information on supported file types and record types, see the Connect help topic, File/record formats reference.

2 Connect ETL supports the following index organizations: Micro Focus indexed, AcuCobol Vision, and C-ISAM, UniKix VSAM.

3 Connect ETL supports mainframe variable record files without record descriptor words (RDWs) as source. These files are generated by FTP when transferring a mainframe variable record file in BINARY mode without the LOCSITE RDW option.

Note: As a MAINFRAME FTPBINARY file does not have an RDW, it may be impossible to identify and recover from field level data corruption. If feasible when using FTP, transfer the mainframe variable record file in BINARY mode with the LOCSITE RDW option.

When specifying the MAINFRAME FTPBINARY file type, you must associate one and only one positional record layout with the source file. The positional record layout can be a Connect ETL record layout or a COBOL copybook record layout. The positional record layout can contain variable length array fields provided that each variable length array field has a determined_by_field.

Note: A delimited record layout cannot be associated with the source file. As such, header layouts are not permitted, and field separator specifications are irrelevant. Unicode byte order marks (BOM) are not supported.

4 Connect ETL supports the following VSAM file types, which are supported by Clerity MTP and UniKix TPE: KSDS, ESDS, and RRDS. Clerity MTP and UniKix TPE were formerly known as TRANS, Unikix and SUN MTP: KSDS, ESDS, and RRDS.