> 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/introduccion-a-las-caracteristicas-funcionales.md).

# Introduction to the functional features

To operate with Editran, it is necessary to maintain a profile file with information about:

* General local environment: A set of parameters is defined within the product itself that allow it to know the installation where the product will be running, in addition to the identification of the local Editran installation, toward the others.
* Secondary local environment (Subenvironment): This is optional, and as many secondary environments as desired can be created. With the subenvironments, they can present themselves to other remote systems as if they were another entity.
* Remote entity: All remote clients with which we are going to interconnect with the product will be defined.
* Presentation application: Identified by six alphanumeric characters. Do not confuse it with transmission ones. In some way, it defines the nature of the information to be exchanged.
* Presentation session: Identified by the local entity, remote entity, and presentation application. The information contained in this profile comes, to a large extent, from the three previous profiles that correspond to it.

A presentation session can consist of up to 20 transmission sessions, depending on the operating mode, or what is the same thing, the information to be exchanged can be transmitted at the same time through up to 20 channels.

To control a presentation session, the file of transmission and reception presentation states is used, which, for each session, reflects the states it goes through and which will be discussed later. The presentation states are the result of the set of transmission states, they change as the processes occur, and they serve to allow or deny the requests made and to establish differences in the processes executed. Example: If a transmission request arrives and the state is "not loaded," the loading and then the transmission are ordered, but if it is "loaded," the transmission is ordered directly.

In a Log file, the messages generated by the various components of Editran are recorded. This file can be queried and listed by applying various selection criteria.

Editran has an interactive component with which profiles are updated and consulted, operator commands are issued, and the Log and state files are consulted. An Editran operator command for a presentation session causes a JOB to be launched, invoking one of the Editran procedures, ZTBGP1, ZTBGP2, ZTBGP3, ZTBGP4 or ZTBGP6, or the name given to them in the installation and specified in the profile of the corresponding presentation session. These procedures can also be launched with a batch JCL. The exception procedure, ZTBGP5 in the installation, is only launched from the Editran transmission module.

With batch JCLs supplied in the installation, the same functions can be invoked as by the interactive operator. In Editran, these procedures must be specified in the profiles of the transmission sessions that are going to be controlled by Editran.

In these procedures, some main programs are invoked directly, which can call others and so on. These called programs can perform general functions of Editran, or they can perform specific functions. In the latter case, they are referred to as "converter" programs. At the end of the pre/post emission/reception and exception processes.


---

# 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/introduccion-a-las-caracteristicas-funcionales.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.