> 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/interfaz-generica-de-aplicacion/caracteristicas-funcionales-de-onesait-editran/caracteristicas-generales-de-onesait-editran.md). # General features of Onesait Editran Editran procedures include the DDs of the following files: * Editran profiles (CICS). * Editran states (CICS). * Editran/G log. It can be omitted if you do not want messages to be recorded in it. * ZTBGFLIS: Listings obtained during procedure execution. * ZTBGFPRI: Extended messages referring to dynamic reservations of application, intermediate, and buffer files, and messages issued by the different programs involved in the process if they are not sent to the system log. * ZTBGFINT: Internal reader to enable the execution of another job started by a user program. * ZTBGFMSJ: If this DD is specified in a procedure, the extended messages referring to dynamic file reservations will be listed in ZTBGFPRI. If it is not specified, these messages will not be listed. * In addition, for the CICS environment, Editran profiles: Data is taken from the transmission sessions that make up the presentation session. It ensures communication with a specific copy of Editran (remember that in the local environment profile are the CICS name and the interfaces transaction name, ZTBI by default). * For cryptography, signing, alarms, statistics, key management, file queues, and other functionalities, etc., consult the corresponding manuals. When a procedure finishes executing, a message is sent to the teleprocessing monitor where Editran runs, indicating whether it completed successfully or unsuccessfully, which may entail, depending on the case, a send or receive request. The completion of a subsequent procedure invoked by the Editran presentation module operator or by application JCL is not communicated to the Editran transmission module. When the subsequent send or receive processes end, optional deletion of the buffers can be performed. If you choose not to delete the buffers in the subsequent processes, keep in mind that no remote request to start a new presentation session will be accepted until, from local Editran, a load/send or initialization/receive request is made, since a remote request would make the data you want to preserve from the previous session disappear. *Notes on buffers for the CICS environment:* In the send load and receive initialization processes, a DELETE/DEFINE CLUSTER of the buffers can be performed using data from the profiles of the corresponding presentation session. The specific buffers are always deleted/defined. Therefore, they must be specified to CICS as CLOSE, ENABLED. The Editran transmission module is responsible for opening them in CICS when it receives control from the Editran presentation module and for closing them when it returns control. For matrix buffers there are two possible modes of operation: * Non-simultaneous updating of the Editran transaction module and the Editran presentation module. It is defined by the user with SHAREOPTION (2,3). The size of the control interval will be that which makes maximum use of the disk track; in this way the number of disk accesses is reduced and therefore the session loading speed is increased. The entire set of presentation sessions must be loaded before any of them begins sending. Automation should not be used in the pre-send phase. * Simultaneous updating of the Editran presentation module and the Editran transmission module. The file definition is performed in the Editran presentation module with SHAREOPTION (3,3); the concurrency control system in the update of matrix buffers has been changed so that they are defined without CISIZE, allowing the default to be used. Matrix buffers are defined automatically only if they do not exist. If they already exist, the records from the previous session are deleted, if applicable. The use of EXCII buffers is recommended. --- # 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/interfaz-generica-de-aplicacion/caracteristicas-funcionales-de-onesait-editran/caracteristicas-generales-de-onesait-editran.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.