> 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/caracteristicas-funcionales-de-onesait-editran/caracteristicas-generales.md).

# General features

There are general functions and specific functions, determined by the converters used.

The general functions are, among others:

* Ability to process up to 999,999 sending and/or receiving application files with fixed- or variable-length records, residing in MVS or USS.
* A presentation session can use up to 20 transmission sessions, hence the identification of the presentation application does not correspond to that of the transmission application.
* The presentation session number is tracked between the two endpoints, so it is incremented with successive exchanges. This number will be passed to the "exchange session number" in the sending and receiving buffers, so transmission will not be allowed if it does not match at both ends. There is a parameter in the presentation session profile that allows specifying whether or not the presentation session number is to be incremented.
* Editran will send to the remote side using the transmission sessions specified in local Editran, which must be in agreement with those defined in remote Editran.
* At the remote end, the information will be received in one buffer or in up to 20, depending on the transmission sessions used. Within this information there will be header data so that remote Editran can check that the options used by the sender are consistent with those of the receiver, and information about characteristics of the received information. The information from the reception buffer or buffers is unloaded into a single application reception file or into as many files as those used in the sending load at the other end, after carrying out the presentation functions in reverse.


---

# 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/caracteristicas-funcionales-de-onesait-editran/caracteristicas-generales.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.
