> 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/administrador-de-onesait-editran/entidad-remota.md). # Remote entity This screen is accessed with option 2 of the administrator menu, 1.2 of the general menu, and by performing or canceling the invoked function. ``` ------------------------------------------------------------------------------ | 21/06/26 ADMINISTRATOR EDITRAN | | 11:21:16 REMOTE ENTITY 5.3 | ------------------------------------------------------------------------------ | | | | | | | A ADD | | | | B DELETE | | | | C QUERY | | | | M MODIFICATION | | | | | | | | OPTION : M | | REMOTE CODE : 0 0009994 0 | | | | | | | | | ------------------------------------------------------------------------------ ``` Enter the desired option and the remote entity code. The following screen will appear: ``` 21/06/26 11:21:53 REMOTE ENTITY MODIFICATION EDITRAN 5.3 ------------------------------------------------------------------------------ REMOTE CODE : 0 0009994 0 NAME: REMOTE 9994 VERSION: 5.3 CONNECTION TYPE : I (I=TCP/IP) USE TCP/IP PROXY (S/N): S SEND BUFFER : 262144 RECEIVE BUFFER : 262144 CORE TRANSACTION: ZTB1 REMOTE IP ADDRESS (TCP/IP) PORT 172.022.242.193 07777 editran.indra.es 07779 ``` * **REMOTE CODE**: Editran User Entity Identification Number. With this code it can be recognized by all Entities interconnected with Editran. * **NAME**: Name of the remote entity. It is an informational parameter. * **VERSION**: The following values can be specified: 5.0, 5.1, 5.2 and 5.3 if the remote entity is going to use Editran V-x.x (the same). Recommendation: Regularly check with the remote entity the version installed at both ends. Both should indicate the lower one. * **CONNECTION TYPE**: By default I (I=TCP/IP), it cannot be modified. * **USE TCP/IP PROXY**: Indicates that outgoing TCP/IP connection requests will be made through the Proxy defined on the remote side. Incoming calls will pass through the Proxy, or arrive directly, regardless of the value of this parameter * **SEND/RECEIVE BUFFER**: Buffer assigned to the socket in outgoing TCP connections (Send / Receive buffer size). In incoming connections, the BUFFER parameter from the ZTBPFLIS configuration file of the 'listener' is applied. This parameter will be used as a general value for the sessions and may be customized in them. If this field is not filled in, the buffer will take the size defined by default in the TCPCONFIG macro of the PROFILE.TCPIP file (TCPSENDBfrsize and TCPRCVBufrsize). In the receive buffer, a value greater than the TCPMAXRCVBufrsize of the TCPCONFIG macro cannot be entered. * **CORE TRANSACTION**: Editran core (default ZTB1). It is the transaction that supports data traffic. It is passed to the Sessions when they are created and can take different values per session. In the modification of the remote entity, the new value will be passed to those sessions whose core matched that of the remote entity. * **REMOTE IP ADDRESS**: The remote IP address will be specified in dotted decimal notation (format nnn.nnn.nnn.nnn, with nnn values between 000 and 255), or the name associated with the address. * **PORT**: The port through which the remote entity handles connection requests will be specified. ℹ️Press ENTER to create the record. Press PF3 to exit. The values of a remote entity's data are passed to that entity's presentation sessions, when they are created, as default values. The other options can be performed for a specific remote entity, in which case it will appear the same as for creation, but with the fields protected. If it is done generically, the following screen will appear: ``` 21/06/26 11:22:47 REMOTE ENTITY MODIFICATION EDITRAN 5.3 ------------------------------------------------------------------------------ S ENTITY DESCRIPTION VER CORE.TRAN USE PROXY - --------- -------------------- --- -------- ---------- A0000000A CICSSITD 04100410--- 5.0 ZTB2 S A00000000 CICSSITD 04100410--- 5.0 ZTB2 S A0000001A ....+....04100410..2 5.0 ZTB2 S A00099910 UNIX AIX 5.0 ZTB1 S A0009993S 5.0 ZTB1 N A00099930 5.2 ZTB1 N A0009994P REMOTE BATCH CREATION, . 5.0 ZTB1 N A00099940 NAME A9994 REMOTE 5.0 ZTB1 N A00099960 PC ANTONIO 5.1 ZTB1 S A00099980 US OTHERS04100410 5.3 ZTB1 N A1111111A A1A1A1A1A041004101A1 5.0 ZTB2 N A2222222A TEST REMOTE PG 5.2 ZTB2 N B00099930 5.2 ZTB1 N B00099980 US OTHERS04100410 5.0 ZTB2 N B2222222A B2B2B2B2B041004102B2 5.0 ZTB2 S C00099910 LINUX CENTOS 5.0 ZTB2 S C3333333C CCCCCCCCC04100410CCC 5.0 ZTB2 S ``` A specific one is selected by typing an “S” in the left column of the line corresponding to that entity, after which the specific screen will appear. The profile of a presentation remote entity will only be deleted if there are no presentation sessions associated with that entity. The values of the remote's data are transferred to the corresponding fields of the presentation sessions, when these are created, as default values. In case the fields are not populated **SEND BUFFER, RECEIVE BUFFER or CORE TRANSACTION**, these will be taken from the environment --- # 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/administrador-de-onesait-editran/entidad-remota.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.