> 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/operation-example.md).
# Operation example
Suppose 2 entities with tax ID: 000099920 (local) and another 000099940 (remote).
Both agree to exchange their keys through the TELEGC application.
In both cases, the administrators define an Editran/P session through which keys will be sent.
Definition of the profile for local RSA and remote RSA
The administrator of the LOCAL entity 000099920 DECIDES to create the SUBSYSTEM ‘P’. This information must be communicated to the administrator of the remote entity 000099940, so that the latter can create a remote RSA record with the subsystem they were told to use and against the local entity 000099920.
In turn, the administrator of the REMOTE entity 000099940 DECIDES to create the subsystem ‘D’. This information must be communicated to the administrator of the local entity 000099920, so that the latter can create a remote RSA record with the subsystem they were told to use and against the remote entity 000099940.
The administrator of 000099920, local, creates the own RSA record with subsystem P (TO GENERATE KEY PAIR).
The administrator of 000099920, local, creates the REMOTE RSA record with subsystem D (TO RECEIVE REMOTE PUBLIC KEY)
The administrator of 000099940, REMOTE, creates the own RSA record with subsystem D (TO GENERATE KEY PAIR).
The administrator of 000099940, REMOTE, creates the REMOTE RSA record with subsystem P (TO RECEIVE REMOTE PUBLIC KEY).
In the AS400 environment, with this option (creating own keys), the procedure that generates keys is launched and associates them with version label 01.
---
# 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/operation-example.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.
.png?alt=media)
.png?alt=media)