> 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-iseries-en/editran-ff/use-of-file-lists-by-editran./editran-parameterization.md).

# EDItran parameterization

When files (XML) are transmitted, these files are in UTF-8 and cannot be translated, therefore in EDItran sessions that use this type of files, it is required to indicate:

* Original data language: Binary
* Translate on send: No
* Translate on reception: No
* Send conversion table: Spaces.
* Receive conversion table: Spaces
* Before sending (a new procedure is provided)
* After receipt (no procedure is provided; it is executed by indicating the Editran/FF Verification type = X in the IGA session)

In the case of receptions, it is recommended to act as follows:

EDItran allows receiving n files in each transmission. The user can indicate in the profiles, in PHYSICAL NAME OF THE APPLICATION RECEIPT FILE:

· That the user indicates a fixed name.

· That the user indicates a binary name (ifs).


---

# 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-iseries-en/editran-ff/use-of-file-lists-by-editran./editran-parameterization.md?ask=<question>&goal=<endgoal>
```

`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.