> 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/parametrizacion-onesait-ecosystems-editran.md).

# Editran parameterization

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

* Original data language: Binary
* Translate on sending: No
* Translate on reception: No
* Sending conversion table: Spaces.
* Reception conversion table: Spaces
* Before sending (a new procedure is provided)
* After reception (a new procedure is provided)

The product allows several files to be received and merged into a single one. In this SEPA transformation case, this is not possible, and therefore you must specify Single file on reception NO (and adjust the output DSNAME if there is one).

In addition, in the case of receptions, it is recommended to proceed as follows:

The product allows n files to be received in each transmission. The user has several options for handling the field PHYSICAL FILE NAME OF RECEIPT APPLICATION in Editran/G profiles:

1. Do not specify anything. In this case, if n files are received, they are downloaded with a default name. Example of receiving 2 files:

> Prefix.lll.Rxnnnnnn.Rnnx.Aaaaaaa.Rmmmmnn
>
> Prefix: File Installation Prefix (Editran/G General local environment)
>
> lll: Alias (Editran/P General or Secondary Local Environment)
>
> Rxnnnnnn: An R and the first 7 characters of the remote code.
>
> Rnnx: An R and the last 3 characters of the remote code.
>
> Aaaaaaa: An A and the name of the submission application
>
> Rmmmmnn: An R and 4 digits of the Exchange Session number and two digits of the application file sequence number.
>
> In this case, it is recommended to indicate the following in PHYSICAL NAME (to differentiate several files in the same transmission and so that the final flat files end up without the last pointer, .XML:
>
> Prefix.lll.R%R.nnx.A%A.R%N%C.XML

2. That the user specifies a fixed dsname (note the limitation mentioned above that several files were received and downloaded to a fixed one). In this case, it is recommended to specify dsname-fixed.xml
3. That the user specifies a dsname with variables. In this case, it is recommended to specify dsname-with-variables.xml

Note that, in all cases, the name received up to now + .XML has been indicated.

Please note that now, the files downloaded by the application are XML and the converter will turn them into fixed-format files so that your application can process them; therefore, what we will try to do is leave your application the same DSNAMEs as what it received up to now.

In the ZTBGFDAT file (explained later), if nothing is indicated in the output DSNAME, it means that the file downloaded by the application was called xx.XML and the one transformed to flat file will be called xx, so the user application will process the same files it has processed up to now (identical DSNAMEs).


---

# 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/parametrizacion-onesait-ecosystems-editran.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.