> 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/instalacion/architecture.md). # Architecture All Jobs are executed within the same dedicated Subsystem. In this way, there is no interference with the other Jobs in the System, since the application programs do not compete with them either for occupancy of Activity Levels or for the increase in paging between main memory and auxiliary storage. This Subsystem has its own Memory Pools. And all jobs are executed within it, including the Subsystem's own monitor. No Job that exceeds its Time-Slice is allowed to move to another Pool, such as \*BASE, but instead it will remain in the Subsystem's own pool of editran. The total number of Jobs occupying Activity Level simultaneously will be 5 plus the number of processes handling the different lines. The programs are all executed using the same Job Description, also specific to the product. These are programs that proportionally spend more time waiting for an event than consuming CPU time, with very short execution cycles. A Class is also provided, specifically designed for the needs of the application's environment programs. Since they are burst-oriented programs, they need to enter execution quickly. That is why they are defined with the same default priority as printer transcribers. The largest possible Time-Slice (program execution cycle) is half that of an "average" interactive program. To speed up leaving the Execution Level, the environment is defined with no paging expected. This does not prevent the system from paging if it considers it necessary. There is a message queue specific to the application. Thus, any message generated by any of the Jobs in the environment will always be located in the same queue. The same is true for the Output Queue. The application includes its own Spool Queue and all Jobs write to it. The application has its own User Profile for the execution of all the Jobs in the environment. It is not a Profile intended to be used from a Workstation to log into the System, so neither its membership in any Group Profile is defined nor does it have any startup program or initial menu. --- # 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/instalacion/architecture.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.