> 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/transmission-operator.md). # Transmission Operator It is used to manage Transmission Sessions (connections, messages, start or end of transmissions or receptions). ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN MANAGER EDITRAN 5.3 | | 18:19:45 TRANSMISSION OPERATOR | ----------------------------------------------------------------------------- | | | | | | | | | 1 ---> SESSION QUERY | | 2 ---> CONNECTION REQUEST | | 3 ---> RELEASE REQUEST | | 4 ---> NETWORK RESTART | | | | | | | | | | OPTION : | | SESSION : | | | | ('*' in generic request) | | | | | | | ----------------------------------------------------------------------------- ``` * **SESSION QUERY**. Performs a query of the active sessions that exist at that moment. * **CONNECTION REQUEST**. To manually establish the physical connection with the remote and be able to start the transmission process. Request not allowed when the Operation Mode is Server. * **RELEASE REQUEST**. To be able to manually release a session that is connected or pending connection. It is necessary not to be transmitting or receiving. * **NETWORK RESTART**. Options to take down-activate TCP connections, For any of the options described above (except in session query and network restart), the SESSION field can be typed in a generic way, so a screen will appear with all the sessions registered in the profile file. It can also be selected selectively, that is, by entering a '\*' 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 entered in the 'SE' field of the desired sessions, which will perform the selected request. ``` CODE CODE SE SESSION SOURCE DESTINATION APP. PROCESS -- --------------------------------- --------- --------- ------ ------------- x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xnnnnnnnx xnnnnnnnx xxxxxx xxxxxxxxxxxxx x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xnnnnnnnx xnnnnnnnx xxxxxx xxxxxxxxxxxxx x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xnnnnnnnx xnnnnnnnx xxxxxx xxxxxxxxxxxxx x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xnnnnnnnx xnnnnnnnx xxxxxx xxxxxxxxxxxxx ``` In the session query, the following screen will appear: ``` STATUS COUNTER STATUS COUNTER SE SESSION TRANSMISSION TRANSMISSION RECEPTION RECEPTION -- ---------------------------------- --------- ---------- --------- --------- x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxx nnnnnnnnnn xxxxxxxxx nnnnnnnnn x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxx nnnnnnnnnn xxxxxxxxx nnnnnnnnn x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxx nnnnnnnnnn xxxxxxxxx nnnnnnnnn x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxx nnnnnnnnnn xxxxxxxxx nnnnnnnnn x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxx nnnnnnnnnn xxxxxxxxx nnnnnnnnn x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxx nnnnnnnnnn xxxxxxxxx nnnnnnnnn ``` If we type 'S' in the 'SE' field, the following screen will appear with information about the status of that Session: ``` ----------------------------------------------------------------------------- | 24/06/2026 TRANSMISSION OPERATOR EDITRAN 5.3 | | 18:23:14 SESSION QUERY | ----------------------------------------------------------------------------- | SESSION : 000099940000099980000079 | | LOCAL CODE : 000099940 REMOTE CODE: 000099980 APPLICATION : 000079 | | TIME OUT INDICATORS | | CONNECTION : NOTIFICATION : | | SAP WAIT: | | TRANSMISSION : E RECEPTION : | | TRANSMISSION RECEPTION | | STATE : 5 TRANSMITTING 1 IN SESSION | | COUNTER : 175 0 | | | | SESSION : S SESSION ESTABLISHED | | CONNECTION : S CONNECTION MADE | | A1P SENT : S A PRE-TRANSMISSION HAS BEEN GENERATED | | A2P SENT : N | | LOCAL-REMOTE CALL: L Connection request made at local end | | | | TCP PORT : 1E62 LOGICAL CHANNEL : 1761 | | | | | ----------------------------------------------------------------------------- ``` In the network restart, the following menu is displayed: ``` ----------------------------------------------------------------------------- | 24/06/2026 TRANSMISSION OPERATOR EDITRAN 5.3 | | 18:23:37 NETWORK RESTART | ----------------------------------------------------------------------------- | | | | | 1 - ACTIVATION OF TCP LISTENER ATTENTION: THIS REQUEST WILL ACTIVATE | | ALL EDITRAN LISTENER TRANSIDS THAT WERE NOT ACTIVE | | | | | | 2 - STOPPING TCP LISTENER ATTENTION: THIS REQUEST STOPS : | | - ALL EDITRAN LISTENER TRANSIDS (DO NOT TYPE PORT) | | - A SINGLE EDITRAN LISTENER TRANSID (TYPE PORT) | | | | | | | | | | | | OPTION : | | PORT : ONLY WITH OPTION 2, NOT REQUIRED | | | | | | | ----------------------------------------------------------------------------- ``` * **TCP LISTENER ACTIVATION**. Valid only for TCP/IP. Two modes are offered: generic (activates all listeners that exist in the EZACONF, by activating the ZTBZ) and specific (activates a listener transid that must be in the EZACONF). In the generic option, the transaction should not be typed, whereas in the specific one, it should. The CICS sockets must have been started previously. If generic or specific is specified and there are already active LISTENER transids, editran will detect the duplication and will not allow 2 transids to act on the same port. * **TCP LISTENER STOP**. Valid only for TCP/IP. This request may require specifying a port (which will match the one specified in the EZACONF for an editran LISTENER). If there is an active editran listener transid (running) on that port, it will stop it (the process may take up to 1 minute, although it allows the operator to continue, informing them that their request is in progress). If none exists, it will report the result (if it is a specific stop). --- # 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/transmission-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.