> 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-cics-en/utilities-and-codes/introduction.md).

# Introduction

Editran is a "software" product that allows the transmission of information formatted and stored in files or databases called BUFFERS.

The information to be sent to a given Remote (destination of the information) will carry the Identification of that destination. This Identification is called the editran SESSION and is made up of the editran Installation Code of the Local, Remote, and an editran Application Code (which allows the transmission of various types of information to the same destination). This Identification is part of either the name of the BUFFER file or the records that contain the information.

Likewise, the information carries a Sequence Number in such a way that it allows control of the information sequence and avoids losses. This Sequence Number, together with the Session, is the only information that editran requires in order to send information to another editran accessible through the communications network.

For the Local editran Installation to communicate with other Remote Installations, it is necessary to define a set of elements required for Communication. The elements that must be defined or created are:

* Characteristics of the "GENERAL LOCAL ENVIRONMENT". This is a set of parameters that can be defined within the product itself, allowing it to know the installation where the product will be operating, in addition to the Identification of the Local editran Installation to the others.
* Characteristics of the "SECONDARY LOCAL ENVIRONMENT (SUBENVIRONMENT)". This is optional and as many as desired may be created. The Local Subenvironment code is defined so that the installation can present itself as that environment.
* Characteristics of "SESSIONS". These are the parameters that define each Remote Installation with the Application Codes that will be used with it. These parameters are defined by the Installation Administrator. It is allowed to create, delete, or modify them. As many Sessions as desired may be defined.
* BUFFER files. These are the files or databases that contain the information with the SESSION and the Sequence Number. They also contain a special record (the first one) where editran collects and leaves information related to the transmission (Number of Records to Send or Receive, Number of Records Sent or Received, Transmission Dates and Times, etc.). These files are created by the User or by the Application Interfaces provided by Indra. For more details on these files, see [Definition and Management of Buffer Files](/documentacion-editran/ibm-editran-v5.3-cics-en/definition-and-management-of-buffer-files.md).


---

# 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-cics-en/utilities-and-codes/introduction.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.