> 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/remote-entity.md). # Remote entity The screen that allows remote entities to be managed is displayed: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:08:02 REMOTE ENTITY | ----------------------------------------------------------------------------- | | | | | | | | | A ---> ADD | | | | B ---> DELETE | | | | C ---> QUERY | | | | M ---> MODIFY | | | | | | OPTION : C | | REMOTE CODE: | | | | | | | | | ----------------------------------------------------------------------------- ``` If you want to query, delete or modify, without specifying a code: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:08:29 REMOTE ENTITIES | ----------------------------------------------------------------------------- | SELECTION CRITERIA: | | REMOTE CODE.: * ******* * | | S ENTITY DESCRIPTION VER CRI CIFR AUTE S.LOC S.REM | | - --------- -------------------- --- --- ---- ---- ----- ----- | | A00099940 THE SAME CICS 5.3 N AES3 DES M L | | A0009995B CICS/VSE 5.0 N | | A00099960 TELDAT JESUS1 5.1 S AES3 RSA 1 2 | | A0009997A 5.0 N | | A00099980 DESC A9998 REMOTE 5.3 S TD3C DES C I | | A3333333A HELLO 5.2 N | | A6666666A IPJ AND FMP 5.2 N | | B0009999C CICS TEST INDRA SSI 5.0 N | | C00099120 CONNECT IGNACIO 5.2 N | | E0009998S IMS-TEST S.N.C.E. 5.0 S TD3C DES | | H0002323A JUANITO'S PC 5.0 N | | H00099910 TEST ENCR SNCE HP 5.0 S TD3C DES | | L00099910 L00099910 5.2 N | | | | EXIT, ADVANCE, SELECT | ----------------------------------------------------------------------------- ``` Selecting that screen or specifying a code on the previous one: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:08:43 REMOTE ENTITY | ----------------------------------------------------------------------------- | USER:CICSSITD F-H:20260414-130726 | | EDITRAN REMOTE CODE....: A 0009994 0 | | | | DESCRIPTION................: THE SAME CICS | | REMOTE EDITRAN VERSION(N.N): 5.3 | | | | | | | | -- PRESENTATION SECURITY -- | | CRYPTOGRAPHY (Y/N).......: N | | DATA ENCRYPTION ALGORITHM.: AES3 AUTHENTICATION ALGORITHM....: DES | | LOCAL SUBSYSTEM...........: M REMOTE SUBSYSTEM..........: L | | LOCAL KEY: | | REMOTE KEY: | | | | | | | | | | EXIT | ----------------------------------------------------------------------------- ``` * **USER**. Contains the last user who modified the record. It is common to all profile records. * **D-T:** Date and time of the last modification. * **EDITRAN REMOTE CODE**: editran remote entity identification number. With this code it will be recognized by all interconnected entities compatible with editran. * **DESCRIPTION**: name of the remote entity. It is an informational parameter. * **REMOTE EDITRAN VERSION**: This data cannot be modified if there are dependent presentation sessions for the remote. The following values can be specified: (5.0, 5.1, 5.2 and 5.3) if the remote entity is going to use editran/G V-x.x (the same). Recommendation: Regularly check with the remote entity the version installed at both ends. Both should indicate the lower one. * **CRYPTOGRAPHY**: It can have two values: 'N' when you do not want to use cryptography during upload/download (default value). 'S' when cryptography is used. Below, all the parameters involved in the cryptographic system are listed and described. Review the [Annex D. Cryptography system in Onesait · Editran, Cryptography System](/documentacion-editran/ibm-editran-v5.3-cics-en/utilities-and-codes/appendix-d.-cryptography-system-in-onesait-editran.md) to understand, above all, the possibilities of editran cryptography. * **DATA ENCRYPTION ALGORITHM**: Indicates whether data should be encrypted during upload/download. It can have the following values: > - 'Spaces' When you do not want to encrypt data during upload/download. > - TD3C If you want to encrypt data during upload/download (triple keys). Only allowed with remote editran/g version > 4.1. > - AES1 If you want to encrypt data during upload/download (simple AES). Only allowed with remote editran/g version > 5.1. > - AES2 If you want to encrypt data during upload/download (double AES). Only allowed with remote editran/g version > 5.1. > - AES3 If you want to encrypt data during upload/download (triple AES). Only allowed with remote editran/g version > 5.1. > > ⚠️This field will appear exactly as is (with the indicated data) in the presentation session, while in the transmission session it will be spaces (\*). > > ℹ️ Note (\*) If the remote has EDITRAN/P and EDITRAN/G separately. > > We enter: > > `DATA ENCRYPTION ALGORITHM : TD3C AUTHENTICATION ALGORITHM: DES` > > The remote has to enter: > > In EDITRAN/P: > > `DATA ENCRYPTION ALGORITHM : AUTHENTICATION ALGORITHM: DES` > > In EDITRAN/G: > > `DATA ENCRYPTION ALGORITHM : TD3C AUTHENTICATION ALGORITHM: DES` * **AUTHENTICATION ALGORITHM:** Indicates the algorithm used to encrypt the session key, and the exchanged data to authenticate the endpoints. It can have the following values: > 'Spaces' When you do not want to authenticate the endpoints (option not valid if you want to encrypt data during upload/download). > > * DES If you want to authenticate the ends with the DES algorithm. > * RSA If you want to authenticate the endpoints with RSA algorithm (valid only for Cryptography versions 3.00 and 4.00 in editran/P). * **LOCAL/REMOTE SUBSYSTEMS**: These parameters only take effect when CRYPTOGRAPHIC VERSION is '3.0' or '4.0' and the authentication algorithm is RSA. The local subsystem and the remote subsystem for managing key exchange with EDITRAN/GC (option 6 of the main menu) must be specified. These parameters can be replaced by the specification of the LOCAL KEY and REMOTE KEY parameters detailed below; when both fields are specified, LOCAL/REMOTE SUBSYSTEM will be used to obtain the keys. * **LOCAL KEY**.: The Label or tag of an auxiliary key will be specified. If the Authentication algorithm is 'DES', the Label of the auxiliary 'EXPORTER' key will be specified, and if the Authentication algorithm is 'RSA', the Label or tag of the local private key will be specified. * **REMOTE KEY**: The Label or tag of an auxiliary key will be specified. If the Authentication algorithm is 'DES', the Label of the auxiliary 'IMPORTER' key will be specified, and if the Authentication algorithm is 'RSA', the Label or tag of the remote public key will be specified. ℹ️The values of the data for a remote entity are passed to the presentation sessions of that entity, when they are created, as default values. ℹ️The removal of the profile of a remote presentation entity will only be carried out if there are no presentation sessions associated with that entity. ℹ️Passing the values of the remote profile parameters to the associated presentation sessions may lead to inconsistencies between the session data. Therefore, this operation has some restrictions, which are indicated below: ℹ️The DESCRIPTION, COMPRESSION and CRC parameters are passed directly to the sessions that had the same value as in the remote profile before the modification. ℹ️ The cryptography parameters are only modified in the remote profile and are not transferred to the sessions under any circumstances. ℹ️The remote endpoint version is only passed to the sessions if they have the same value as the remote profile and the new value is higher than the previous one. --- # 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/remote-entity.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.