> 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/administracion-y-operacion/navigation-between-screens/main-menu/activity-control/editran-g-operator.md). # Editran/G Operator This screen is accessed with option 1 of the general menu. All operator functions are ordered from there without accessing other screens. These operator functions can also be ordered from an application CL or from the application.
Enter the desired option and the presentation session formed by the local entity (if it is spaces, it takes the general local environment), the remote entity and the presentation application, except for option C, which will be acted upon as indicated below. With PF3 you return to the general menu. The processes carried out in each invoked function depend greatly on the data existing in the profile of the corresponding presentation session and are, in general terms, the following: * 1\. Load transmission presentation. * The status of the transmission presentation session is validated (or in other words, the status of all the transmission sessions that make it up). * The load is executed if the session state is "not loaded" or "finished" (see the meaning of the different states in screen 2.1.1. "Broadcast status inquiry". At the end of the process it changes to "transmitting". * The single pre-transmission procedure is launched (in installation P1PREEMI) which can also be requested from an application CL (from editran only the load cannot be requested, but rather the transmission which may have the load associated with it). * If the session state is "finished", 1 is added to the presentation session number as long as INCREMENTO SESION = "S". See also screen 2.1.1. This presentation session number, depending on the converters used, would be passed to the exchange session number of the transmission session control record in the transmission buffer or buffers. In this case, it must match the one recorded in the reception buffers on the remote side. * Depending on the characteristics of each converter, several application and/or presentation processes can be carried out. In any case, one or more transmission buffers are obtained with state "loaded" although still not available for editran. * The application is notified of the preparation of the buffers by means of as many A8R messages as transmission sessions have been loaded, changing them to state "transmitting". * The pre-transmission user program is invoked, if it exists in the profile. * Before performing the load, CLRPFM/CRTPFM is done on the transmission buffers. The physical file name and record length are taken from the corresponding editran transmission session profile * 2\. Process post-transmission presentation. * In addition to by the operator, this function can be requested by application CL and by editran (A3P). * The process is carried out if the session state is "transmitted" or "suspended". At the end of the process it sets it to "finished". * If there are several transmission sessions in the presentation and the request comes from editran, it indicates the end of transmission of only one of them whose state becomes "transmitted". When the request for the last one arrives, the presentation process is triggered. * In any case, the post-transmission single procedure is launched (in installation P3POSEMI) and the post-transmission converter program and user program are invoked, if they exist in the presentation session profile. * If the presentation session profile specifies deleting buffer after transmission, CLRPFM is done for specific ones and the session records are deleted in the matrix buffers. * 3\. Transmit presentation. * In addition to by the operator, it can be requested by application CL and by the application (with A1P of one of the possible transmission sessions) * The presentation session state must be "not loaded", "finished", "loaded", "suspended" or "transmitting". If "not loaded" or "finished", it performs the pre-transmission process as seen in 1.-, so that it would change to "loaded". * Once "loaded", A1Rs are sent to editran for all transmission sessions that make up the presentation. The same is done for "suspended", since it expresses the will to continue with a previously interrupted session, and for "transmitting", in case any transmission session has been interrupted without editran's knowledge. The session state changes to "transmitting". * 4\. Interrupt transmission presentation. This is about interrupting the ongoing transmission, which must be in state "transmitting" or "suspended", for which EDPs are sent to editran for all transmission sessions of the presentation. The application returns control of the transmission buffers to editran. The session state changes to "suspended". * 5\. Initialize reception presentation. * The status of the reception presentation session is validated (or in other words, the status of all the transmission sessions that make it up). * Initialization is executed if the session state is "initialized" or "finished" (see the meaning of the different states in screen 2.1.2. "Reception status inquiry". At the end of the process it changes to "receiving". * The single pre-reception procedure is launched (in installation P2PREREC) which can also be requested from an application CL (from the application only initialization cannot be requested, but rather the reception which may have the initialization associated with it). * If the session state is "finished", 1 is added to the presentation session number as long as INCREMENTO SESION = "S". See also screen 2.1.2. This presentation session number, depending on the converters used, would be passed to the exchange session number of the transmission session control record in the reception buffer or buffers. In this case, it must match the one recorded in the transmission buffers on the remote side in the next exchange. * The pre-reception converter program specified in the corresponding session profile is invoked, if it exists. One or more reception buffers are obtained with state "initialized" although still not available for the application. * The notification of the initialization of the reception buffers AAR is sent to the application and the state changes to "receiving". * The pre-reception user program is invoked, if it exists in the profile. * During initialization, CLRPFM/CRTPFM is done on the reception buffers. The physical file name and record length are taken from the corresponding editran transmission session profile. * In addition to by the operator, this function can be requested by application CL and by editran (A4P). * 6\. Download reception presentation. * The process is carried out if the session state is "received" or "suspended". At the end of the process it is set to "finished". * If there are several transmission sessions in the presentation and the request comes from editran, it indicates the end of reception of only one of them whose state becomes "received"; at this moment editran can know the actual number of sessions used by the remote sender (data coming in a header record) and removes the excess ones from the presentation session status record. When the request for the last one arrives, the presentation download process is triggered. * In any case, the post-reception single procedure is launched (in installation P4POSREC) and the post-transmission converter program and user program are invoked, if they exist in the presentation session profile. * If the presentation session profile specifies deleting buffer after reception, CLRPFM is done. * 7\. Receive presentation. * In addition to by the operator, it can be requested by application CL and by the application (with A2P of one of the possible transmission sessions) * The presentation session state must be "initialized", "finished", "suspended" or "receiving". If "initialized" or "finished", it performs the pre-reception process as seen in 6.-, so that it would change to "initialized". * Once "initialized", A1Rs are sent to editran for all transmission sessions of the presentation, since it is not known for sure how many the sender will use. The same is done for "suspended", since it expresses the will to continue with a previously interrupted session, and for "receiving", in case any transmission session has been interrupted without editran's knowledge. The session state changes to "receiving". * 9\. Interrupt reception presentation. * This is about interrupting the ongoing transmission, which must be "receiving", for which EDRs are sent to editran for all transmission sessions of the presentation. The application returns control of the reception buffers to editran. The session state changes to "suspended". * C. Generic inquiry of presentation session states. * Do not enter either the local entity, the remote entity or the presentation application, to query the states of all presentation sessions. * Enter the remote entity and not the presentation application, to query the states of the presentation sessions of a remote entity. * Enter the presentation application and not the remote entity, to query the states of the presentation sessions of an application. * Enter the remote entity and the presentation application, to query the states of a specific presentation session.
--- # 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/administracion-y-operacion/navigation-between-screens/main-menu/activity-control/editran-g-operator.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.