> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/editran-sepa/descripcion-de-la-funcionalidad/uso-de-listas-de-ficheros-por-onesait-ecosystems-editran.md). # Use of file lists by Editran The product allows the transmission of multiple files in the same session. To send: * Some customers use a file list (ZTBGFCAR, see format Table 1) to perform the uploads, since their files have different names in each one. Therefore, they create a daily list of files for each presentation to be sent. This list is passed to the step prior to sending. Normally, in order to use a single procedure with all remotes, the dsname of the file list is formed with variables recognizable by the procedure (source, remote, and application). * Other customers always use the same dsnames for the files to be sent (the content is different in each transmission), so they choose to indicate the dsname of the files to be sent in the product profiles themselves. To receive: * If nothing is indicated in the application's profiles, it downloads the received files with a default name * If something is indicated in the application's profiles, it downloads the received files with the indicated name * In all cases, the post-reception step, ZTBGLFE, provides the user with a file, which is a list of received and downloaded files (ZTBGFLFE, see format TABLE 2) Table 1. Content of the ZTBGFCAR file, a fixed-length file of 80, whose contents are the application's send files and their characteristics. The content is as follows (one record per file):


Level	Name	Length	Type	Description
1	File format	1	Alphan.	Application file format: ‘R’: Record, ‘M’: Modified
1	Source data language	1	Alphan.	Original language of the data: ‘A’: Ascii, ‘E’: Ebcdic, ‘B’: Binary
1	Translate on send	1	Alphan.	Language in which the data is sent: ‘A’: Ascii, ‘E’: Ebcdic, ‘N’: No translation
1	Compression	1	Alphan.	Compression: ‘F’ Compressed, ‘N’ Uncompressed
1	Filler	1	Alphan.	Separation space
1	Physical name	74	Alphan.	Physical name of the application file
1	Filler	1	Alphan.	Separation space

Table 2. Content of the ZTBGFLFE file (list of received files, which the post-reception procedure currently leaves), fixed-length 130. The content is as follows (one record per file):


Level	Name	Length	Type	Description
1	File area	130	Alphan.
2	Physical name	44	Alphan.	Physical name of the downloaded application file
2	Filler	1	Alphan.	Separator dash
2	Presentation-end date	14	No.	Presentation end date-time in YYYYMMDDHHMMSS format
2	Loaded file type	4	No.	Loaded or output file type ‘FIXED’ ‘VBLE’ ‘VEXP’ ‘BINA’
2	Loaded data language	1	Alphan.	Language of the loaded data: ‘A’: Ascii, ‘E’: Ebcdic, ‘B’: Binary
2	Compression	1	Alphan.	Indicates whether the file was loaded with compression: ‘F’ Compressed, ‘N’ Uncompressed
2	Filler	1	Alphan.	Reserve area
2	Source physical name	44	Alphan.	Physical name of the application file at source
2	App file bytes	12	No	Application file bytes
2	Record length	6	No	LRECL.
2	Filler	1	Alphan.	Reserve area

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/editran-sepa/descripcion-de-la-funcionalidad/uso-de-listas-de-ficheros-por-onesait-ecosystems-editran.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.