> 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/readme.md). # Editran platform The Indra Editran platform is structured into two essential components: * **Communications Platform (editran/P**). It includes all common services directly related to communication facilities (protocol, interfaces with TCP transmission services, local networks, etc.). * **Generic Application Interface Module (editran/G**). It isolates the communication services provided by editran/P from user applications, serving as the link between them and the transmission processes ![scheme](https://2807498471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2W4cn5C1WDTJzDOR25es%2Fuploads%2Fgit-blob-c6c3c2a149a9e49ae8fbb75775e1b8ed5bc2d34f%2Fesquema.png?alt=media) ## Description Editran transmits files, with a specific structure, from a local end to a remote one. These files are called send and receive buffers. To obtain send buffers from conventional application files and, conversely, to obtain these application files from receive buffers, it is necessary to use load and unload programs which, together, can be called the application interface. The current Generic Application Interface, hereinafter Editran/G, has been developed with the dual objective of greatly increasing the functionality of the existing interfaces and at the same time remaining compatible with the previous ones, so that an entity that installs the latest version of Editran/G will be able to: * Dispense with the previous interfaces. * Exchange data with entities that have EDITRAN/G with a previous version, in compatibility mode with that version. * Exchange data with entities that have the same version of EDITRAN/G, both in compatible mode (same functionality as the previous interfaces with improvements in the process) and in native mode (extended functionality). ## Send and receive buffers These are the temporary files used by Editran during sending or receiving. A buffer file contains data corresponding to a single transmission session. The record length can be (including the key) from 13 to 9999. When the remote end is a HOST, only the values 252 or 4050 are valid. The buffers are composed of: * A first control record with the key sequence number set to zero. This record contains, among others, the following data and may affect an interface: * Total number of records. * Number of confirmed records. * Indicator of complete sent or received. * Indicator of availability for Editran. * Exchange session number. * Several data records with key sequence number consecutive from 1 to the total number exchanged. ## Integration with Editran/G To work with editran/G it is necessary to maintain a profile file with information about: * Local entity. 9 numeric characters are used for identification. * Remote entity. Same as above. * Presentation application. Identified by 6 alphanumeric characters. It is used to define the nature of the information to be exchanged. * Presentation session. Identified by a name that we recommend defining with the code (or name) of the remote entity + the presentation application (for example, 9999-PRUEBA). 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 editran transmission sessions or, in other words, the information to be exchanged can be transmitted split across up to 20 circuits at the same time. The presentation session goes through different states that reflect the moment in which file sending and receiving is found. In the Onesait Editran /G Operator section, the different states and the operations that are allowed or not in each case are explained. In a log file, the messages generated by the various editran/G components are recorded. This file can be consulted and listed by applying various selection criteria. There are commands provided in the installation with which the same functions can be invoked as from the operator menu. Editran/G can operate in **compatible mode with versions 4.1, 5.0 and 5.1, and in native mode with versions 5.2**. The operating mode is determined by the version of the remote editran/G in the Presentation profile. ### General characteristics When operating in native mode, there are general functions (specified in the presentation profiles) and specific functions (determined by the converters used). General functions include, among others: * Ability to process send application files with fixed-length, variable, hybrid records and/or binary files. * A presentation session can use up to 20 editran transmission sessions; hence the identification of the presentation application does not correspond to that of the transmission application defined in editran. This can also happen in the case that there is only one transmission session associated with a presentation session. * The send application information can be subjected to several optional presentation functions (cryptography, compression and EBCDIC/ASCII translation) and is loaded into specific buffers, up to a maximum of 20, depending on the number of transmission sessions specified and the chosen splitting criterion. * The presentation session number between two ends is tracked, so that it is incremented with successive exchanges. This number will be passed to the exchange session number in the send and receive buffers, so transmission will not be allowed if it does not match at both ends. * editran/P will send to the remote side using the transmission sessions specified in local editran/G, which must be in agreement with those defined in remote editran/G. In these transmission sessions the presentation functions to be performed by editran/P, cryptography, compression and/or CRC, could be defined, but it would not make much sense if they have already been performed on the application data. * At the remote end, the information will be received in buffers, up to a maximum of 20, depending on the transmission sessions used. Within this information there will be header data so that remote editran/G can check that the options used by the sender are consistent with those of the receiver, and information about the characteristics of the received information. The information from the receive buffer or buffers is unloaded into as many application files as those used in the send load at the other end, after having performed the presentation functions in reverse. ### Specific characteristics The specific functions are associated with the version of remote editran/G indicated in the presentation profiles. That is, when a 5.2 installation communicates with an entity with a lower version, it will only be able to use the functionalities compatible with that version. Below, the main specific functionalities of each version are listed. For more detailed information, consult the new functionalities documents. #### Version 3.0, 3.1 * The maximum number of files that can be transmitted is 9999 between homogeneous environments (Unix, Windows) and 99 for the rest. * It transmits files in fixed or variable format from 1 to 99999 bytes per record. Between homogeneous environments they can also be exchanged in binary mode. * The logical transmission unit (or batch) is the file. That is, application synchronisms are not incorporated. * Compression and data alphabet are at presentation level, not per file. * The possibility of RSA authentication is added. #### Version 4.0 * The maximum number of files that can be transmitted is 9999 between homogeneous environments (Unix, Windows) and 99 for the rest. * Sending files in binary mode to any environment is allowed. * Features such as compression and translation are applied from this version at file level. * Optional translation on reception is added. * The user may define tables to adapt editran character sets to the local ones of each entity. #### Version 4.1 * Verification of the signature of transmitted files. * Triple DES cryptography. * A file is generated per Presentation with the list of files sent/received in the last transmission made. * Integration with the editran/GC subsystem for external exchange of RSA keys. #### Version 5.0 * There is no limit on the number of files that can be sent in each transmission. * There is no limit on the size of the application file. Files larger than 2 Gbytes are supported. * It is not necessary to define the alphabet of the remote entity. #### Version 5.1 * Addition of transmissions with remote download confirmation. #### Version 5.2 * Security improvement: AES encryption and 2048- and 4096-bit RSA keys. * Integration with the Editran/FF module for control in the sending of signed files. * New license file format to improve management in entities with several local codes. * The possibility of generating a daily report of all transmitted files is added. * Logging of users who modify the Editran configuration. --- # 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/readme.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.