> 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-iseries-en/gestor-de-claves/definitions-and-screens.md).

# Definitions and screens

To access the exchange key management, type the command EDIGC52

The main menu of the exchange key management is as follows:

<figure><img src="https://2621858476-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F80nfuaOloGPZthms7LSJ%2Fuploads%2Fgit-blob-d971f5463c95e3e48d3157e143e50318457427a2%2Fimage%20(193).png?alt=media" alt=""><figcaption></figcaption></figure>

The different options are detailed below (records in file PERGC52):

* There are n records of own RSA keys. The key for each one is the source code and the created subsystem. Within each one, the name of the labels (private and public) and a list of the 3 latest versions (versions range from 01 to 99) of active or operational keys is specified (option 1).

Key: R(RSA) + L(local) + NIF.LOC + ZEROS + local sub-entity

* When the RSA records of own keys are "exported" to a given remote entity, what is being done is "exporting" the key whose label is that of the active version, in short, associating the own keys with a specific remote entity (option 2).

Key: R(RSA) + L(local) + NIF.LOC + remote NIF + local sub-entity

* When the RSA records of remote keys are "imported" from a remote entity, we must know which subsystem it is in order to register it (option 3). From there, the import is automatic; the remote end determines the active version.

Key: R(RSA) + R(remote) + NIF.LOC + remote NIF + remote sub-entity


---

# 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-iseries-en/gestor-de-claves/definitions-and-screens.md?ask=<question>&goal=<endgoal>
```

`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.
