> 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/documentacion-editran-editran-sepa-v3-open-en/separador-ficheros-planos-y-xml.md).

# Flat file and XML file separator

XML files are not designed to be stacked one after another within a single physical file, since the file as a whole is not suitable, for example, when validating against its schema. However, in response to some clients that do receive files generated this way, Editran/SEPA offers the functionality to convert each logical XML file one by one into its corresponding flat file, leaving these in turn all together again in the output file.

Similarly, the converter can process flat input files that include several logical files. In this case, the result of the conversion will be a file whose content may be a single logical XML file or several, depending on how the parameter has been configured `param.juntar.xml` described in the section [5 Onesait Ecosystems Configuration · Editran/SEPA](#5-configuración-de-onesait-ecosystems--editransepa).

To use this functionality, which requires a specific license, the following must be configured:

**Unix**

In file `SEPA/scripts/EntornoSepa` the value of the variable must be changed `VARIOS_LOGICOS` to `1`

```sh
# -----------------------------------------------------------
# ------------ INSTALLATION DEFINITIONS ------------------
# -----------------------------------------------------------
DIR_SEPA=/opt/editran/SEPA
PARAM_EDITRAN="${DIR_SEPA}"/scripts/ParametrosEditran
SO_SEPA="Linux" # Linux | AIX | Sun | HP
VARIOS_LOGICOS=1 # 0.- one physical file and one logical file |
                 # 1.- one physical file with more than one logical file
# -----------------------------------------------------------
```

**Windows**

In file `SEPA/scripts/EntornoSepa.sh` the value of the variable must be changed `VARIOS_LOGICOS` to `1`

```bat
rem -------------------------------------------------------------
rem INSTALLATION DEFINITIONS
rem -------------------------------------------------------------
set DIR_SEPA=C:\EditranSEPA
rem VARIOS_LOGICOS: 0.- one physical file and one logical / 1.- one physical file with more than
rem one logical
set VARIOS_LOGICOS=1
rem -------------------------------------------------------------
```

**iSeries and z/OS**

Instead of starting Editran/SEPA using `start.sh` and `stop.sh`, the alternative scripts included in the folder must be used `/scripts`: `startSeparador.sh` and `stopSeparador.sh`. These scripts must be configured following the converter's own manuals for iSeries and z/OS.

This functionality involves the creation of temporary auxiliary files which, once the conversion is finished, are deleted. Their name is that of the input file followed by the current date in milliseconds and they are created in the temporary directory defined by default on each system. It is possible to modify this location by assigning a new value to the parameter `java.io.tmpdir` of the Java virtual machine (as described in the section [5 Onesait Ecosystems Configuration · Editran/SEPA](#5-configuración-de-onesait-ecosystems--editransepa)).

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.editran.onesait.com/documentacion-editran/documentacion-editran-editran-sepa-v3-open-en/separador-ficheros-planos-y-xml.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.