> 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/modo-de-uso/integracion/tratamiento-de-ficheros-con-warnings.md).

# Handling files with warnings

By default, the scripts included with the installation are programmed so that flat files obtained from a conversion that remain incomplete (the result of the conversion will be a Warning) will be considered by Editran/SEPA as correct and therefore will be sent. This situation occurs when the file to be converted is XML and does not contain optional data according to that format which, however, are mandatory for the flat-file standard to which it is converted.

To modify this behavior and mark those files as invalid, the following change will be made in `PRVEMISEPA` and in `PSTRECSEPA`:

**Windows:**

We modify:

```bat
IF NOT %ERRORLEVEL% == 0 (
 IF NOT %ERRORLEVEL% == 36 (
  echo Error converting file %1
  echo Error=%ERRORLEVEL%
  goto Error
 )
)
```

For:

```bat
IF NOT %ERRORLEVEL% == 0 (
   echo Error converting file %1
   echo Error=%ERRORLEVEL%
   goto Error
)
```

**UNIX:**

We modify:

```sh
if [ ${error} -ne 0 -ne 36 ]; then
 echo "Error converting the file ${fichconvert}"
```

For:

```sh
if [ ${error} -ne 0 ]; then
 echo "Error converting the file ${fichconvert}"
```


---

# 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/modo-de-uso/integracion/tratamiento-de-ficheros-con-warnings.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.