> 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-administrator/local-and-remote-communication-lines.md). # Local and remote communication lines ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:36:46 LOCAL AND REMOTE LINES | ----------------------------------------------------------------------------- | | | A ---> CREATE A LINE (SPECIFY ALL DATA) | | | | B ---> DELETE A LINE (ONLY IF THERE ARE NO ONGOING CONNECTIONS) | | | | C ---> CONSULT LINES | | | | M ---> MODIFY LINES (IF THERE ARE NO ONGOING CONNECTIONS) | | | | I ---> SWAP ORDER BETWEEN 2 LINES (WITHOUT ONGOING CONNECTIONS) | | | | | | OPTION.......................................: C | | OWNER (L)OCAL,(R)EMOTE.......................: | | CGO (OWNER: L = ZEROS, R = REMOTE CGO).: | | LINE TYPE (I)P, (P)ROXY.....................: | | LINE TYPES LOCAL PROP.:(P)ROXY). REMOTE PROP.:(I)P | | | | | ----------------------------------------------------------------------------- ``` In this option, all local or remote lines are created, deleted, modified, swapped in order, and consulted. Local lines must be created before creating the transmission sessions that use them. Remote lines must be created before creating the transmission sessions that use them (if done from the transmission session with a remote that does not exist, only creating a line is allowed). On deletions, deletion is not allowed if there are connected sessions, regardless of whether they use the described line or not. To be able to communicate with a remote side we will need: * If the connection is IP, at least one remote IP line (regardless of whether that destination is a remote PROXY). To that IP we will reach directly (in which case we will not need anything else) * Through a local proxy (in which case we will need a local proxy line). In the case of consultation, deletion or modification, generic criteria can be used (for example, by entering only consultation, it shows all PX lines and part of the remote IPs we have; by pressing PF8 we will get all the remotes). ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:37:03 COMMUNICATION LINES | ----------------------------------------------------------------------------- | SELECTION CRITERIA: | | OWNER: * LINE TYPE.: * CODE.....: * ******* * | | S OWNER TYPE NUM LINE CHARACTERISTICS | | - --------- --- --- ------------------------------------------------------- | | LOCAL PX 001 010.055.000.017 -07775 | | LOCAL PX 002 010.055.000.017 -07779 | | LOCAL PX 003 010.055.000.017 -09999 | | LOCAL PX 004 010.055.000.052 -07781 | | A00099940 IP 001 172.022.242.193 -07777 | | A00099940 IP 002 asanjosexp.indra.es -07777 | | A00099940 IP 003 127.000.000.001 -07777 | | A00099960 IP 001 172.026.130.035 -07777 | | A0009997A IP 001 111.011.011.111 -07777 | | A00099980 IP 001 MADZOSIMSPRUE.INDRA.ES -07777 | | A00099980 IP 002 172.022.242.195 -07777 | | A00099980 IP 003 172.022.242.195 -07778 | | B0009999C IP 001 000 -00033 | | | | EXIT, ADVANCE, SELECT | ----------------------------------------------------------------------------- ``` The lines shown can be local (proxy) or remote (ip) * In the case of local lines, the owner code (local code) is left as zeros. In the case of remote lines, the owner code must be included (remote code). * In all cases, the internal editran line number is shown. * In the case of local lines, you are asked whether you want to monitor the line (see local environment 1.3.1 and (see [Monitoring of local communication lines](/documentacion-editran/ibm-editran-v5.3-cics-en/statistics-and-monitoring/monitoring-of-local-communication-lines.md)) * In the case of local PX lines, logs, configuration, and gateway status can be queried through a different port than usual (see chapter 1.4) * In the case of local PX, ip + port of the local proxy * In the case of remote IPs, ip + port of the editran or remote proxy. From the previous screen, you can select to display the full content (detail screens). In the case of creation, the owner, code, and line type must be specified. You directly access the detail screens. ``` ------------------------------------------------------------------------------ | OWNER: L LINE TYPE.: P CODE.....: 0 0000000 0 REFERENCE NO.: 001 | | PROXY LINE: IP ADDRESS OF THE PROXY + PROXY PORT | | IP ADDRESS (DNS/IP ADDR) PORT | | ---------------------------------------------------------------- ------ | | 172.026.130.019 07779 | | | MONITOR PX (Y/N).....: N DIALOG PORT (LOG) PX....: 07775 | ------------------------------------------------------------------------------- |-----------------------------------------------------------------------------| | OWNER: R LINE TYPE.: I CODE.....: 0 0009996 0 REF. NUMBER.: 001 | | IP LINE: REMOTE IP ADDRESS + REMOTE PORT | | IP ADDRESS (DNS/IP ADDR) PORT | | ---------------------------------------------------------------- ------ | | 172.022.071.075 07777 | ------------------------------------------------------------------------------- ``` In the case of swapping the order of 2 lines, the owner, code, and line type must be specified. A generic screen is accessed: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:37:03 COMMUNICATION LINES | ----------------------------------------------------------------------------- | SELECTION CRITERIA: INDICATE LINE NUMBERS (ORDER) TO CHANGE.: 001 004 | | OWNER: R LINE TYPE.: I CODE.....: 0 0009991 0 | | S OWNER TYPE NUM LINE CHARACTERISTICS | | - --------- --- --- ------------------------------------------------------- | | 000099910 IP 001 172.022.164.069 -07777 | | 000099910 IP 002 EDITRAN.INDRA.ES -05555 | | 000099910 IP 003 172.022.164.069 -07778 | | 000099910 IP 004 172.022.164.066 -08888 | | 000099910 IP 005 ASANJOSEXP.INDRA.ES -07777 | | 000099910 IP 006 172.022.071.129 -07777 | | 000099910 IP 007 172.022.164.080 -07777 | | 000099910 IP 008 MONTILLA.INDRA.ES -07777 | | 000099910 IP 009 192.168.015.001 -07777 | | | | | | | | | | | | EXIT, SELECT | ------------------------------------------------------------------------------- ``` On that screen, you can consult the detail screen or change the order of 2 lines. Changing the order of 2 lines means that the one; * The one with the higher reference takes the lower reference and vice versa, while keeping its content. * All sessions with both undergo an order change. * All sessions with one reference are modified with the new reference, but keep the same content; that is, they continue calling through the same place. On deletions, deletion is not allowed if there are sessions that only have one line of the owner-type to be deleted. * LOCAL editran/PROXY FIELDS (owner L, type P) and * TCP FIELDS: (owner R, code xxxxxxxxx, type I): * TCP/IP ADDRESSES. In z/OS lower than 1.4, DNS names longer than 24 bytes cannot be used, since the interface does not support them. DNS names or the IP address itself, including the dots, must be specified (in nnn.nnn.nnn.nnn format, where nnn are values between 000 and 255). In addition, the port must be specified (the port on which the device to be connected listens with a listener). If DNS names are coded, they must be resolved by the entity's own name server. * LOCAL editran/PROXY FIELDS (owner L, type P): * MONITOR Y/N: Indicates whether you want to monitor the line (see [Monitoring of local communication lines](/documentacion-editran/ibm-editran-v5.3-cics-en/statistics-and-monitoring/monitoring-of-local-communication-lines.md)) * LOCAL editran/PROXY FIELDS (owner L, type P): * DIALOG PORT (LOG). Port for querying logs, statuses, and proxy gateway configuration (see chapter 1.4). It must be different from the line's "editran" listening port (PORT parameter). --- # 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-administrator/local-and-remote-communication-lines.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.