> 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/open-v5.2.1-en/novedades/evolucion.md). # Editran evolution The evolution of the optional presentation and application functions is presented here, in the different versions of Editran up to the version consulted here ## Onesait Editran V2.0 * Totals control. An option that has been used very little, consisting of placing a numeric field in each transmission block (normally an amount) corresponding to the logical records within the block. Total records are included by segments so that special synchronization is performed and the receiver checks that the total corresponds to the sum of the detail amounts in the segment. * Compression. Three or more repeated characters are replaced by 3 before transmission. The inverse operation is performed on reception. * CRC. A cyclic redundancy code is added to the message on transmission and checked on reception. ## Onesait Editran V2.1 * Totals control, compression and CRC. * Optional cryptography. Interface with several hardware and software cryptography products. * Parameter notification. The remote editran version is added to the session profile. If it is V2.1, the calling end notifies the remote end of the session parameters, cryptography, compression, totals control, CRC, transmission length, etc. (in an SAP message), which the remote end verifies and accepts or rejects. If it is V1.0 or V2.0, both ends must agree on the parameters used in the transmission. ## Onesait Editran V2.2 * Compression, CRC and cryptography. * Totals control is replaced by Application or Batch Synchronization, since it is understood that application functions should be in the interfaces and not in editran, which, on the other hand, has sufficient mechanisms to ensure the integrity of the information. * The Transmission Interruption Procedure appears, executed by editran when a transmission is interrupted. * The most notable feature of this version is the change in the length of the session identifier, which goes from 6 to 12 characters. ## Onesait Editran V3.0 * Code extension (NIF): The editran codes are increased, going from 6 numeric digits to 9 digits, of which the first and last are alphanumeric and the rest numeric. That is, N.I.F. format (Tax Identification Number). * Multi-environment, allowing editran to operate with different local identifiers. ## Onesait Editran V3.1 * This latest version has the same functionalities as editran 3.0, but taking the year 2000 effect into account. Incorporation of 4 digits in dates (YEAR 2000). ## Onesait Editran V4.0 * editran/P V2.2 incompatibility. An important feature of this version is that it is not compatible with editran/P versions lower than 3.0. editran/G versions 2.1, 3.0 and 3.1 remain compatible with editran/G 4.0. * distributed editran. * Local-remote address rotation (x25, tcp). ## Onesait Editran V4.1 * Indication of the editran Version in the editran Administrator and Operator. * Incorporation of the Triple DES algorithm into editran cryptography mode 3.0. * Incorporation of the source code into the user data of TCP/IP connections to enable the definition of more than 10 sub-environments per application with a single remote. * Control in the transmission start request message (SCP) of the synchronization of the contents of the Local and Remote buffers. * Translation on reception according to the presentation profile. * editran/G V1.0 and V2.0 incompatibility. editran/G versions 2.1, 3.0, 3.1 and 4.0 remain compatible with editran/G 4.1. * New parameter for validating the calling remote address. * Incorporation of a new (optional) module for managing transmissions (editran/GT, Windows only) * New Windows functionality for X25 with EICON cards, which allows configuring the card to be used, if there is more than one, and the card port if there is more than one port per card. ## Onesait Editran V5.0 * Expansion in the number of local and remote lines. The number of IP lines has been increased from 3 to 6 so that, in the event of failures, there may be more alternative routes. * Automatic version update. A protocol has been implemented whereby editran entities exchange their versions. If both are 5.0 or higher, they will update the version in the profiles to the lowest installed version of the two. * Validations before starting reception that avoid some problems that were detected until now in the download after transmission. Specifically, it is validated that the version being loaded is known and that if the file comes compressed and/or encrypted there is a usage license. * Incorporation of a new (optional) module for file transmission through the SWIFT network. * Backup in connection types. For each session a main network protocol is defined, but optionally other networks can also be defined that will be used as backup for failed connections. * Application files larger than 2GBytes are supported. ## Onesait Editran V5.1 * The maximum number of concurrent transmissions is 500. The limit of concurrent sessions in previous versions was 100. It has been increased to 500, which will be the new default value for the "Maximum number of sessions" field in the local profile. * Incompatibility with V3.1 This version can only communicate with remote entities that have editran V4.0 installed at a minimum. If the installation of version 5.1 is a software upgrade and profiles are migrated, whenever sessions appear with a version lower than 4.0 they will be registered with the lowest possible version (4.0). * Activity control for connected sessions. The protocol establishes a new inactivity timeout that controls whether, if a session is connected but there is no data traffic for a given period, it is released. The default timeout value is 600 s, which the user can modify by defining the EDI\_TOUT\_IDLE environment variable. Once the timeout expires, the release is recorded in the log with the following message: "Release due to inactivity timeout" * Alphabet negotiation during session establishment. In V5.1 the protocol has been modified so that the alphabet is negotiated between entities whenever possible, removing from the user the responsibility of knowing that data from the remote installation. To maintain compatibility with version 5.0 or lower, the alphabet field has been kept in the editran/P profile, but it must be taken into account that it is only used when the connection is outgoing. If the remote entity is the one calling, regardless of the version and the value of the field, the connection is accepted and communication takes place in its alphabet. --- # 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/open-v5.2.1-en/novedades/evolucion.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.