> 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/interfaz-generica-de-aplicacion/anexo-d.-ficheros-generacionales/ficheros-de-aplicacion-de-recepcion-generacionales.md).

# Generation reception application files

Whenever you want the received files to remain as generational files, you must indicate that the reception file is not to be deleted if it exists. (Delete\_if\_exists = “N”).

For the received files to be placed in a generation group, in the place corresponding to the reception file, the DSN of the generation group is defined, to which a “(+n)” is added, where n ranges from 1 to 255, that is, for example, “DSN(+1)”.

Depending on whether it is received in a single file (single file on receipt), one or more generations can be created in the same download to store the received files.

**Important note**

It is important to note that if the profiles parameter “Delete\_if\_exists” has the value “S” and the DSN of the generation group is specified without parentheses in the place of the single file, Editran assumes that it is a non-generational file and therefore all generations of the group are deleted along with their definition. In this case, when attempting to catalog the reception file created in the process, an error is detected that Editran records in the LOG with the message “ZTG0182.- Possible error in profile definition: generational file”.

As is obvious, the model of the generation group has to be consistent with the characteristics of the received files


---

# 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/interfaz-generica-de-aplicacion/anexo-d.-ficheros-generacionales/ficheros-de-aplicacion-de-recepcion-generacionales.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.