> 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-iseries-en/administracion-y-operacion/functional-features-of-onesait-editran-5.3.1/introduction-to-functional-features.md). # Introduction to functional features To work with Editran 5.3.1, 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, for the others. Nine characters are used for identification, known as the NIF format (XNNNNNNNX; where X are alphanumeric characters and N are numeric digits). * Secondary local environment (Sub-environment): This is optional, and as many secondary environments as desired can be created. With sub-environments, 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 with six alphanumeric characters. Do not confuse it with Editran ones, which are called transmission. In some way, it defines the nature of the information to be exchanged. * Presentation session: Identified by the local entity + the remote entity + the presentation application. The information contained in this profile comes, to a large extent, from the three previous profiles corresponding to it. A presentation session can consist of up to 20 transmission sessions, depending on the operating mode, or, in other words, the information to be exchanged can be transmitted at the same time through up to 20 circuits. To control a presentation session, the send and receive presentation state file is used, which, for each session, reflects the states it goes through, 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 are used to allow or deny the requests made and to establish differences in the processes executed. Example: If a send request arrives and the state is "not loaded", the load and then the send are ordered, but if it is "loaded", the send is ordered directly. In a log file, the messages generated by the various components of Editran 5.3.1 are recorded. This file can be consulted and listed by applying various selection criteria. An Editran operator command for a presentation session causes a JOB to be launched, invoking one of the four unique Editran procedures, I1PREEMI, I2PREREC, I3POSEMI or I4POREC, 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 CL or by the application. With batch CLs supplied in the installation, the same functions as those of the interactive operator can be invoked. In Editran, these procedures must be specified in the profiles of the transmission sessions that are to be controlled by Editran 5.3.1. In these procedures, some main programs are invoked directly, which can call others and so on. These called programs can perform general Editran functions, general functions according to the operating mode, compatibility or native 5.3.1, or they can perform specific functions. In the latter case, they are called "converter" programs and are specified in the profile of the corresponding presentation session, each one associated with a pre/post send/receive process. At the end of the pre/post send/receive processes, user-specified programs can also be invoked, likewise specified in the profile of the presentation session. It is possible to work with Editran 5.3.1 in compatibility mode and in native 5.3.1 mode. The operating mode is determined by the remote Editran version in the presentation session profile. If this version is 5.3.1, it works in native mode; otherwise, it works in compatibility mode. --- # 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-iseries-en/administracion-y-operacion/functional-features-of-onesait-editran-5.3.1/introduction-to-functional-features.md?ask=&goal= ``` `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.