> 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-ims-en/operacion/primerospasos/control-de-actividad-de-onesait-editran/operador.md). # Operator This screen is accessed with option 1 of the Activity Control menu or with option 2.1 of the general menu. All operator functions are ordered from it without accessing other screens. These operator functions can also be ordered from an application JCL ``` 21/06/26 12:52:59 OPERATOR EDITRAN 5.3 ------------------------------------------------------------------------------ 1 LOAD SENDING PRESENTATION 2 PROCESS PRESENTATION AFTER SENDING 3 SEND PRESENTATION 5 INTERRUPT SENDING PRESENTATION 6 INITIALIZE RECEIVING PRESENTATION 7 DOWNLOAD RECEIVING PRESENTATION 8 RECEIVE PRESENTATION 9 INTERRUPT RECEIVING PRESENTATION C GENERIC QUERY OF PRESENTATION STATES T QUERY TRANSMISSION SESSIONS K TRANSMISSION CONNECTION REQUEST L TRANSMISSION RELEASE REQUEST R NETWORK RESTART OPTION : 1 LOCAL CODE : 0 0009998 0 REMOTE CODE : 0 0009994 0 APPLICATION : TEST ``` Enter the desired option and the presentation session formed by the remote entity and the presentation application. With PF3 you return to the general menu. For any of the options shown, you can type only the option, which will display a screen with all the sessions defined in the profile file. You can also select selectively, that is, by putting a '\*' in the application either before or after it, which will display a screen with all the sessions containing the common characters. Once on that screen, place an 'S' on the lines corresponding to the desired sessions, which will carry out the selected request. ``` 21/06/26 OPERATOR EDITRAN 12:53:49 LOAD SENDING PRESENTATION 5.3 S PRESENTATION SESSION STATE V TRANSMI PROCESS RESULT - -------------------------- ------------ --- ------ -------------------- 000099980 000099940 PRTCP1 FINISHED 5.0 PRTCP1 000099980 000099940 PRTCP2 FINISHED 5.0 PRTCP2 000099980 000099940 PRTCP3 FINISHED 5.2 PRTCP3 000099980 000099940 PRTCP4 FINISHED 5.1 PRTCP4 000099980 000099940 PRTCP5 FINISHED 5.0 PRTCP5 000099980 000099940 PRTCP6 FINISHED 5.0 PRTCP6 000099980 000099940 PRTCP7 FINISHED 5.0 PRTCP7 000099980 000099940 PRTCP8 FINISHED 5.1 PRTCP8 000099980 000099940 PRTCP9 FINISHED 5.2 PRTCP9 000099980 000099940 PRTC10 FINISHED 5.0 PRTC11 000099980 000099940 PRTC14 FINISHED 5.2 PRTC14 000099980 000099940 PRUEBA TRANSMITTING 5.2 PRUEBA 000099980 000099940 PRUEB1 NOT LOADED 5.2 PRUEB1 000099980 000099940 PRUEFF FINISHED 5.2 PRUEFF 000099980 000099940 PRUE04 NOT LOADED 5.2 PRUE04 000099980 000099940 PRUE25 NOT LOADED 5.2 PRUE25 000099980 000099940 PRUE51 NOT LOADED 5.2 PRUE51 ``` The processes carried out in each invoked function depend largely on the data existing in the profile of the corresponding presentation session, and are in general terms the following: ## **1-Load sending presentation** * In addition to the operator, this function can be requested by application JCL. The state of the sending presentation session is validated (that is, the state 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 on the “Send state query” screen). At the end of the process it changes to "sending". * If Accumulative load type is specified in the presentation session, loading is allowed in the "sending" state. In this type of load only a single transmission session is allowed. If, when performing the load, the process is transmitting, a new load will not be allowed. * The single pre-send procedure is launched (in installation ZTBGP1), which can also be requested from an application JCL. The JOB sheet and following sheets are taken from the profile of the presentation session. All the operations mentioned below are performed in the execution of the said procedure. * The pre-send Converter program is invoked and one or more send buffers are obtained with the "loaded" state. ## **2-Process presentation after sending** * In addition to the operator, this function can be requested by application JCL. * The process is carried out if the session state is "sent" or "suspended". At the end of the process it is set to "finished". * The single post-send procedure is launched (in installation ZTBGP3), during whose execution the Converter program is invoked * If "delete buffer after sending" is specified in the presentation session profile, the session records are deleted. ## **3-Send presentation** * In addition to the operator, it can be requested by application JCL. * The presentation session state must be "not loaded", "finished", "loaded", "suspended" or "sending". If "not loaded" or "finished", it carries out the pre-send process as seen in 1, so that it would become "loaded". ## **5-Interrupt sending presentation** * This is about interrupting the ongoing sending, which must be in the "sending" or "suspended" state. The session state changes to "suspended". Interruption of a session in "finished" state is allowed if the buffers have not been deleted in the previous post-send process, changing the state to "suspended", in which presentation sending is already allowed. ## **6-Initialize receiving presentation** * In addition to the operator, this function can be requested by application JCL. * The state of the receiving presentation session is validated (that is, the state 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 on the "Receive state query" screen). At the end of the process it changes to "receiving". * The single pre-receive procedure is launched. The JOB sheet and following sheets are taken from the profile of the presentation session. The operations mentioned below are performed in the execution of the said procedure. * The pre-receive Converter program is invoked. One or more receive buffers are obtained with "initialized" state. ## **7-Download receiving presentation** * In addition to the operator, this function can be requested by application JCL. * The process is carried out if the session state is "received" or "suspended". At the end of the process it is set to "finished". The process is allowed if the state is "finished" and the receive buffers have not been deleted in the previous download. * If there are several transmission sessions in the presentation session, at this point the actual number of sessions used by the sending remote can be known (data contained in a header record) and the remaining ones are removed from the presentation session status record. When the request for the last one arrives, the process of downloading the presentation is triggered. * In any case, the single post-receive procedure is launched (in installation ZTBGP4), during whose execution the Converter program and the receive exit are invoked, if they exist in the profile of the presentation session. * If "delete buffer after receiving" is specified in the presentation session profile, the session records are deleted. ## **8-Receive presentation** * In addition to the operator, it can be requested by application JCL. * The presentation session state must be "initialized", "finished", "suspended" or "receiving". If "initialized" or "finished", it carries out the pre-receive process as seen in 6, so that it would become "initialized". * Once "initialized", they are sent to the A2R transmission module for all the presentation transmission sessions, since it is not known for sure how many the sender will use. The same is done for "suspended", since there is an intention to continue with a previously interrupted session, and it changes to "receiving", in case any transmission session has been interrupted without Editran's knowledge. The session state changes to "receiving". ## **9-Interrupt receiving presentation** * This is about interrupting the ongoing reception, which must be "receiving". The session state changes to "suspended". ## **C-Generic query of presentation session states** * Do not enter the local entity, the remote entity, or the presentation application, to query the states of all presentation sessions. * Enter the local entity, to query the states of the presentation sessions associated with a local environment. * 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 state of a specific presentation session. ``` 21/06/26 OPERATOR EDITRAN 12:57:20 GENERIC QUERY OF PRESENTATION STATES 5.3 PRESENTATION SESSION SEND START/END RECEIVE START/END -------------------------- ---------- -------------- ---------- -------------- 000099980 000099940 PRTCP1 FINISHED 20/01/25-11:12 FINISHED 20/01/25-11:21 000099980 000099940 PRTCP2 FINISHED 20/01/25-11:15 FINISHED 20/01/25-11:22 000099980 000099940 PRTCP3 FINISHED 20/01/25-11:12 FINISHED 20/01/25-11:20 000099980 000099940 PRTCP4 FINISHED 20/01/25-11:15 FINISHED 20/01/25-11:21 000099980 000099940 PRTCP5 TRANSMITTING 20/01/25-11:15 INITIALIZING 20/01/25-11:21 000099980 000099940 PRTCP6 FINISHED 20/01/25-11:15 FINISHED 20/01/25-11:21 000099980 000099940 PRTCP7 FINISHED 20/01/25-11:15 FINISHED 20/01/25-11:21 000099980 000099940 PRTCP8 FINISHED 20/01/25-11:16 FINISHED 20/01/25-11:21 000099980 000099940 PRTCP9 FINISHED 20/01/25-11:15 FINISHED 20/01/25-11:20 000099980 000099940 PRTC10 FINISHED 20/01/25-11:16 FINISHED 20/01/25-11:21 000099980 000099940 PRTC14 FINISHED 20/01/25-11:16 FINISHED 20/01/25-11:21 000099980 000099940 PRUEBA TRANSMITTING 15/01/25-15:21 INITIALIZING 00/00/00-00:00 000099980 000099940 PRUEB1 NOT LOADED 18/02/20-15:46 FINISHED 22/06/16-10:03 000099980 000099940 PRUEFF FINISHED 13/12/17-14:36 INITIALIZING 19/02/15-12:27 000099980 000099940 PRUE04 NOT LOADED 00/00/00-00:00 INITIALIZING 00/00/00-00:00 000099980 000099940 PRUE25 NOT LOADED 00/00/00-00:00 INITIALIZING 00/00/00-00:00 000099980 000099940 PRUE51 TRANSMITTING 18/00/25-00:00 INITIALIZING 00/00/00-00:00 ``` ℹ️You can page with PF7 and PF8. With ENTER, the states are updated. All presentation sessions that meet the specified selection criterion and are in profiles appear, even if they do not appear in the state file. With PF3 you return to the operator menu. ## **T-Query transmission sessions** * The query can be made in two ways: > - GENERIC: The Local Code, Remote Code and Application fields will be filled in partially or completely or will use values preceded or followed by \*. The following screen is shown, one line per session that meets the selection criteria and is active (connected, in the process of connecting, or pending transmission). ``` 22/06/26 SESSION QUERY EDITRAN 10:05:53 5.3 LOCAL REMOTE APPL. S.SEND C.SEND S.RECV C.RECV T.CON NET.TR --------- --------- ------ --------- --------- --------- --------- ----- ------ 000099980 000099940 PRTCP0 1 SESSION 0 1 SESSION 0 I ZTCP 000099980 000099940 PRTCP1 5 SENDING. 325 1 SESSION 0 I ZTCP 000099980 000099940 PRTCP2 5 SENDING. 275 1 SESSION 0 I ZTCP 000099980 000099940 PRTCP3 1 SESSION 0 1 SESSION 0 I ZTCP 000099980 000099940 PRTCP4 5 SENDING. 150 1 SESSION 0 I ZTCP 000099980 000099940 PRTCP5 1 SESSION 0 1 SESSION 0 I ZTCP 000099980 000099940 PRTCP6 1 SESSION 0 1 SESSION 0 I ZTCP 000099980 000099940 PRTCP7 1 SESSION 0 1 SESSION 0 I ZTCP 000099980 000099940 PRTCP8 1 SESSION 0 1 SESSION 0 I ZTCP 000099980 000099940 PRTCP9 1 SESSION 0 1 SESSION 0 I ZTC1 000099980 000099940 PRTC11 1 SESSION 0 1 SESSION 0 I ZTCP 000099980 000099940 PRTC12 1 SESSION 0 1 SESSION 0 I ZTCP 000099980 000099940 PRTC13 1 SESSION 0 1 SESSION 0 I ZTCP 000099980 000099940 PRTC14 1 SESSION 0 1 SESSION 0 I ZTCP 000099980 000099940 PRUEB2 0 DISCON. 0 0 DISCON. 0 I ZTC1 ``` SPECIFIC for a particular session: for this it is necessary to type the 3 codes in full. The session will be shown even if the session is not active. The screen that appears is the following: ``` ------------------------------------------------------------------------------ | 22/06/26 EDITRAN MANAGER EDITRAN | | 10:10:26 SESSION QUERY 5.3 | ------------------------------------------------------------------------------ | | | LOCAL CODE: 000099980 REMOTE CODE: 000099940 APPLICATION: PRTCP1 | | | | CONNECTION TYPE : I NETWORK TRANSACTION : ZTCP | | | | SEND STATE : IN SESSION SEND COUNTER : 0 | | | | RECEIVE STATE : IN SESSION RECEIVE COUNTER : 0 | | | | | | | | | | | | | | | | | | | | | | | ------------------------------------------------------------------------------ ``` ℹ️In both cases, pressing ENTER refreshes the content of the screen and PF3 returns to the Operator screen. In all the following functions, except in *Network Restart* in which none of the codes should be entered, a generic or specific request can be made for a session with the same criteria as for the session query. With a specific request, the requested function is carried out. With a generic request, a screen like the following example is shown with all sessions that meet the selection criteria: In the specific case of release, in the generic request only the sessions that meet the selection and are also connected will be shown. ## **K-Transmission connection request** * To manually establish the physical connection with the remote side. For the connection to be processed, we must be within the transmission schedule defined for the session. ``` 22/06/26 CONNECTION REQUEST EDITRAN 10:23:34 5.3 S LOCAL REMOTE APPLICATION PROCESS RESULT - --------- --------- ---------- ---------------------------------------------- 000099980000099940 PRPSD2 000099980000099940 PRTCP0 000099980 000099940 PRTCP1 THE CONNECTION HAS BEEN REQUESTED 000099980000099940 PRTCP2 000099980000099940 PRTCP3 000099980000099940 PRTCP4 000099980000099940 PRTCP5 000099980000099940 PRTCP6 000099980000099940 PRTCP7 000099980000099940 PRTCP8 000099980000099940 PRTCP9 000099980000099940 PRTC11 000099980000099940 PRTC12 000099980000099940 PRTC13 000099980000099940 PRTC14 000099980 000099940 PRUEBA THE CONNECTION HAS BEEN REQUESTED 000099980 000099940 PRUEB1 ``` * By placing “S” in the selection field on the left, the connection request for the corresponding transmission session is requested, reporting the result of the request in the message on the right. ## **L-Transmission release request** * To be able to manually release a connection. In the generic request only the connected sessions or those in the process of connecting will be shown ``` 22/06/26 RELEASE REQUEST EDITRAN 10:42:35 5.3 S LOCAL REMOTE APPLICATION PROCESS RESULT - --------- --------- ---------- ---------------------------------------------- 000099980000099940 PRTCP0 000099980 000099940 PRTCP1 THE RELEASE HAS BEEN REQUESTED 000099980000099940 PRTCP2 000099980000099940 PRTCP3 000099980000099940 PRTCP4 000099980 000099940 PRTCP5 THE RELEASE HAS BEEN REQUESTED 000099980000099940 PRTCP6 000099980000099940 PRTCP7 000099980000099940 PRTCP8 000099980000099940 PRTCP9 000099980000099940 PRTC11 000099980000099940 PRTC12 000099980000099940 PRTC13 000099980000099940 PRTC14 000099980000099940 PRUEBA 000099980 000099940 PRUEB2 ``` By placing “S” in the selection field on the left, the release request for the corresponding transmission session is requested, reporting the result of the request in the message on the right. ## **R-Network restart.** All connected sessions or those pending connection that are not transmitting or pending transmission are released. --- # 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-ims-en/operacion/primerospasos/control-de-actividad-de-onesait-editran/operador.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.