> 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-cics-en/operacion/onesait-editran-activity-control/operator.md). # Operator It is used to manage Presentation Sessions (loads, unloads, emissions, receptions, interruptions). ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN MANAGER EDITRAN 5.3 | | 12:38:38 PRESENTATION OPERATOR | ----------------------------------------------------------------------------- | | | 1 ---> LOAD PRESENTATION FOR EMISSION | | 2 ---> PROCESS PRESENTATION AFTER EMISSION | | 3 ---> EMIT PRESENTATION | | 5 ---> INTERRUPT EMISSION PRESENTATION | | | | 6 ---> INITIALIZE RECEPTION PRESENTATION | | 7 ---> UNLOAD RECEPTION PRESENTATION | | 8 ---> RECEIVE PRESENTATION | | 9 ---> INTERRUPT RECEPTION PRESENTATION | | | | C ---> GENERIC QUERY OF PRESENTATION STATES | | | | OPTION.......: C | | LOCAL CODE.: 0 0009994 0 | | REMOTE CODE: | | APPLICATION...: | | | | | ----------------------------------------------------------------------------- ``` For any of the options described above (except the status query), the SESSION can be typed in a generic way, which will display a screen with all the sessions registered in the profile file. It can also be selected selectively, that is, by putting an '\*' followed by the other characters, which will display the following screen with all the sessions that end with the common characters. Once on that screen, an 'S' will be placed in the 'SE' field of the desired sessions, which will carry out the selected request. ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN/G OPERATOR EDITRAN 5.3 | | 12:39:01 LOAD PRESENTATION FOR EMISSION | ----------------------------------------------------------------------------- SELECTION CRITERIA: LOCAL CGO..: 0 0009994 0 REMOTE CGO.: * ******* * APPLICATION.: ****** SE PRESENTATION SESSION DESCRIPTION STATUS V TRANS. -- -------------------------- -------------------- ------------ --- ------ s 000099940 A00099940 EDTRF2 SES:A00099940-EDTRF2 FINISHED 5.2 EDTRF2 000099940 A00099940 PRBSWC SNVIO NOMINAS NOT LOADED 5.1 SWIFTC 000099940 A00099940 PRUEBA SWIFT TESTS NOT LOADED 4.1 SWIFTA 000099940 A00099940 TELEGC NOT LOADED 5.2 TELEGC 000099940 A00099960 TEXTOS PCX28 TESTS NOT LOADED 4.1 TEXTOS 000099940 A0009997A APLICA VARIOUS SESSION TEST NOT LOADED 4.1 APLI01 000099940 A0009997A TELECA TPPP NOT LOADED 4.1 TELECA 000099940 A00099980 ABEURA SES:A00099980-ABEURA FINISHED 5.2 ABEURA 000099940 A00099980 ABEURP SES:A00099980-ABEURP FINISHED 5.2 ABEURP 000099940 A00099980 PRUEBA ?00000000 NOT LOADED 4.1 PRUEBA 000099940 A00099980 TELECA TELELOAD ARGENTINA NOT LOADED 4.1 TELECA 000099940 A00099980 TELEGC SES:A00099980-TELEGC FINISHED 5.2 TELEGC 000099940 A00099980 000001 KI.EGDI.Y%Y%X%D.H%H NOT LOADED 4.1 000001 EXIT, ADVANCE, SELECT ``` In the status query, the following screen will appear: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN/G OPERATOR EDITRAN 5.3 | | 12:39:12 GENERIC QUERY OF PRESENTATION STATES | ----------------------------------------------------------------------------- SELECTION CRITERIA: LOCAL CGO..: 0 0009994 0 REMOTE CGO.: * ******* * APPLICATION.: ****** PRESENTATION SESSION EMISSION START / END RECEPTION START / END -------------------------- ---------- -------------- ---------- -------------- 000099940 A00099940 EDTRF2 FINISHED 19/01/23-15:08 INITIALIZES 00/00/00-00:00 000099940 A00099940 PRBSWC NOT LOADED 00/00/00-00:00 INITIALIZES 00/00/00-00:00 000099940 A00099940 PRUEBA NOT LOADED 01/03/13-13:43 INITIALIZES 11/12/14-16:53 000099940 A00099940 TELEGC NOT LOADED 00/00/00-00:00 INITIALIZES 00/00/00-00:00 000099940 A00099960 TEXTOS NOT LOADED 00/00/00-00:00 INITIALIZES 00/00/00-00:00 000099940 A0009997A APLICA NOT LOADED 29/09/10-17:17 INITIALIZES 21/01/10-16:31 000099940 A0009997A TELECA NOT LOADED 21/09/05-16:44 INITIALIZES 20/04/11-08:40 000099940 A00099980 ABEURA FINISHED 05/09/23-13:43 FINISHED 05/09/23-13:42 000099940 A00099980 ABEURP FINISHED 05/09/23-13:43 FINISHED 05/09/23-13:42 000099940 A00099980 PRUEBA NOT LOADED 00/00/00-00:00 INITIALIZES 28/10/02-10:22 000099940 A00099980 TELECA NOT LOADED 12/05/09-17:54 INITIALIZES 00/00/00-00:00 000099940 A00099980 TELEGC FINISHED 05/09/23-08:32 RECEIVING 05/09/23-08:32 000099940 A00099980 000001 NOT LOADED 25/03/11-12:37 INITIALIZES 25/09/12-12:27 ``` 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: ## Load emission presentation. * In addition to the operator, this function can be requested by application JCL and by editran/P (A8P generated from a type 8 A5P). * The state of the emission presentation session is validated (or, in other words, 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 screen 2.1.1 "Emission status query"). At the end of the process it changes to "emitting". * If Accumulative load type is specified at presentation-session level, loading is allowed in state ''emitting''. The characteristics of this type of load are: a single transmission session is required, specific files cannot be used. If when performing the load the process is transmitting, it will not allow a new load. * The single pre-emission procedure is launched (in ZTBGP1 installation), which can also be requested from an application JCL. The JOB tab and subsequent ones are taken from the profile of the first editran transmission session. All the operations mentioned below are performed in the execution of the said procedure. * If the session state is "finished" and it has been specified that the presentation session number is to be incremented, 1 is added to it. 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 emission buffer(s). In this case, it must match the one recorded in the reception buffers on the remote side. * The pre-emission Converter program is invoked. Depending on the characteristics of each Converter, several application and/or presentation processes may be performed. In any case, one or more emission buffers are obtained with state "loaded" although still not available for editran/P. * editran/P is notified of the preparation of the buffers via as many A8R messages as transmission sessions have been loaded, changing them to state "emitting". * The pre-emission user program is invoked, if it exists in the profile. * In the CICS environment: Before loading, a DELETE/DEFINE is performed for the specific emission buffers, taking the "back" and primary space from the presentation session profile. The physical file name and record length are taken from the corresponding editran transmission session profile. It is also done for matrix files, if they do not exist, and with the parameters associated with the first transmission session defined in the presentation session; if they already exist, the records that may exist from previous loads associated with the session are deleted. * In the event that buffers are DEFINEd, the primary space is taken as the sum of those specified in the transmission sessions within the presentation session, and the secondary space as 50% of the primary. For the dynamic allocation of intermediate files, the space is calculated based on these same amounts, so it is recommended that the primary space in profiles be specified according to the actual amount of information to be emitted. ## Process post-emission presentation. * In addition to the operator, this function can be requested by application JCL and by editran/P (A3P launched at the end of the emission of each transmission session). * The process is performed if the session state is "emitted" 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/P, it indicates the end of emission of only one of them whose state becomes "emitted". When the request for the last one arrives, the presentation process is triggered. * In any case, the single post-emission procedure is launched (in ZTBGP3 installation), during whose execution the Converter program and the post-emission user program are invoked, if they exist in the presentation session profile. * If the presentation session profile specifies deleting buffer after emission", DELETE is performed for specific buffers and the session records in the matrix ones are deleted. ## Emit presentation. * In addition to the operator, it can be requested by application jcl and by editran/P (with A1P of one of the possible transmission sessions from a remote editran/P request, or as a consequence of a type 1 A5P) * The presentation session state must be "not loaded", "finished", "loaded", "suspended" or "emitting". If "not loaded" or "finished" it performs the pre-emission process as seen in 1. - and it would move to "loaded". * Once "loaded", A1R's are sent to editran/P for all the transmission sessions that make up the presentation. The same is done for "suspended", since this indicates the intention to continue with a previously interrupted session, and for "emitting", in case any transmission session has been interrupted without editran/G's knowledge. The session state changes to "emitting". ## Interrupt emission presentation. * It consists of interrupting the current emission, which must be in state "emitting" or "suspended", for which EDP's are sent to editran/P for all the transmission sessions of the presentation. editran/P returns control of the emission buffers to editran/G. The session state changes to "suspended". Interruption of a session in state "finished" is allowed if the buffers have not been deleted in the previous post-emission process, changing the state to "suspended", in which presentation emission is already allowed. ## Initialize reception presentation. * In addition to the operator, this function can be requested by application JCL and by editran/P (AAP generated from a type A A5P). * The state of the reception presentation session is validated (or, in other words, 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 screen 2.1.2 "Reception status query"). At the end of the process it changes to "receiving". * The single pre-reception procedure is launched. The JOB tab and subsequent ones are taken, in the CICS environment, from the profile of the first editran transmission session, and in the IMS environment from the presentation session profile. The operations mentioned below are performed in the execution of the said procedure. * If the session state is "finished" and it has been specified that the presentation session number be incremented, 1 is added to it. 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(s). In this case, it must match the one recorded in the emission buffers on the remote side in the next exchange. * The pre-reception Converter program is invoked. One or more reception buffers are obtained with state "initialized" although still not available for editran/P. * The notification of the initialization of the reception buffers AAR is sent to editran/P and it changes to state "receiving". * The pre-reception user program is invoked, if it exists in the profile. * In the CICS environment, initialization is done by DELETE/DEFINE of the specific reception buffers taking the "volser" and primary space from the presentation session profile. The physical file name and record length are taken from the corresponding editran transmission session profile. It is also done for matrix buffers if they do not exist and with the parameters associated with the first transmission session that comprises the presentation; if they already exist, all data records that may exist from previous sessions are deleted. The definition or deletion is carried out for the maximum number of transmission sessions defined in the corresponding presentation profile, since the number that the sender will use is not known in advance. ## Unload reception presentation. * In addition to the operator, this function can be requested by application JCL and by editran/P (A4P from the completion of each reception or by type 4 A5P). * The process is performed 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 reception buffers have not been deleted in the previous unload. * If there are several transmission sessions in the presentation and the request comes from editran/P, it indicates the end of reception of only one of them whose state becomes "received"; at this point editran/G can know the actual number of sessions used by the remote sender (data that comes in a header record) and removes from the presentation session state record those that are surplus. When the request for the last one arrives, the presentation unload process is triggered. * In any case, the single post-reception procedure is launched (in ZTBGP4 installation) in which the Converter program, the post-emission user program and the reception exit are invoked, if they exist in the presentation session profile. * If the presentation session profile specifies deleting buffer after reception, DELETE is performed for specific buffers and the session records in the matrix ones are deleted. ## Receive presentation. * In addition to the operator, it can be requested by application JCL and by editran/P (with A2P of one of the possible transmission sessions from a remote editran/P request, and from a type 2 A5P) * 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. - and it would move to "initialized". * Once "initialized", A2R are sent to editran/P for all the 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 there is an intention to continue with a previously interrupted session, and for "receiving", in case any transmission session has been interrupted without editran/G's knowledge. The session state changes to "receiving". ## Interrupt reception presentation. * It consists of interrupting the current reception, which must be "receiving", for which EDR's are sent to editran/P for all the transmission sessions of the presentation. editran/P returns control of the reception buffers to editran/G. The session state changes to "suspended". ## Generic query of presentation session states. * Allows querying the state of the emission and reception of the presentation sessions. --- # 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-cics-en/operacion/onesait-editran-activity-control/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.