> 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/proxy/caracteristicas-principales.md). # Main features The increasingly widespread implementation of the TCP/IP protocol in the product is associated with new needs that arise as a result of the use of the Internet. The Internet brings a large number of advantages to end-to-end communication, but it also adds a series of uncertainties such as, for example, the issue of communications security. Here arises the need to use products such as *firewalls* that allow us to control, as far as possible, security uncertainties and other products such as Editranpx, specifically developed for the application and which will prevent most attacks on *DoS* (Denial of Service), *bombing, etc*., thus protecting the *HOST* from the possible dangers of placing it in the demilitarized zone. Below, some of the features that make Editranpx an essential element in a public TCP/IP network will be detailed. * Multiplatform > EditranPX is available for Microsoft Windows operating systems and for UNIX operating systems, such as Solaris, Linux..., thus allowing the appropriate platform to be chosen for each need. * Optimization (MultiThreading) > One of the main concerns when designing Editranpx has been the search for the greatest possible efficiency. In this way, Editranpx is built so that it creates a thread of execution for each connected client, allowing both that one connection does not affect the others and that maximum efficiency is achieved in multiprocessor systems. * TimeOut > There is a *TimeOut* independent and prior to the connection with the application on the HOST that will close the connection to a client when it connects, but does not send any data. In this way, it prevents the HOST from being attacked through an attempt at *DoS* for lack of free connections. * Bombing > In addition to having a *TimeOut*, Editranpx has a system that prevents multiple connection attempts from the same client with the intention of trying a *DoS*. These connections will never reach the internal Editran, preventing it from being loaded and, furthermore, when an attempt at *bombing* the connection with the offender is disconnected. * Security > As already mentioned, Editranpx avoids having to place the application in the demilitarized zone or DMZ, since that is where Editranpx will go; thus security is increased, since the application remains on the internal network, outside the DMZ. * Editran protocol validation > One of the main characteristics of Editranpx is that *recognizes* the product protocol and in this way it will prevent connections that do not comply with the protocol from reaching the application, thus doing preliminary work and relieving it of the same. * Syslog generation > Editranpx has its own log generation system and also uses the system syslog, which allows it to be stored or the same log to be sent to another machine --- # 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/proxy/caracteristicas-principales.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.