> 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/key-manager/introduction/subsystem-example-3.md). # Subsystem example 3 In the following example, a case is shown in which several keys have already been exchanged by the two entities (V1, V2, V4). In addition, it is shown that key V3 was generated, but was not exported at the time to that remote B (6789). State changes are shown in bold.


Subsystem Entity A=1234	Key status	Operation	Network	Operation	Key status	Subsystem Entity B 6789
Subsystem X Own RSA Type Local code 1234 Remote code 0000	V2 is lost V3-OPERATIONAL V4-OPERATIONAL V5-ACTIVE	Generate key (V5)			(already existed) V1-OPERATIONAL V2-OPERATIONAL V4-ACTIVE	Subsystem X External RSA Type Local code 6789 Remote code 1234
Subsystem X Own RSA Type Local code 1234 Remote code 6789	V1 is lost V2-OPERATIONAL V4-ACTIVE V5-GENERATED	Export V5 key from the previous subsystem			(already existed) V1-OPERATIONAL V2-OPERATIONAL V4-ACTIVE	Subsystem X External RSA Type Local code 6789 Remote code 1234
Subsystem X Own RSA Type Local code 1234 Remote code 6789	V2-OPERATIONAL V4-ACTIVE V5-GENERATED	Send V5 key Before issuance	A issues	Receives key
Subsystem X Own RSA Type Local code 1234 Remote code 6789	V2-OPERATIONAL V4-ACTIVE V5-SENT	After issuance		After reception	V1-is lost V2-OPERATIONAL V4-ACTIVE V5-RECEIVED	Subsystem X External RSA Type Local code 6789 Remote code 1234
		Receives confirmation file	B issues	Before issuance Issues confirmation	V2-OPERATIONAL V4-ACTIVE V5-RECEIVED	Subsystem X External RSA Type Local code 6789 Remote code 1234
Subsystem X Own RSA Type Local code 1234 Remote code 6789	V2-OPERATIONAL V4-OPERATIONAL V5-ACTIVE	After reception		After transmission	V2-OPERATIONAL V4-OPERATIONAL V5-ACTIVE	Subsystem X External RSA Type Local code 6789 Remote code 1234

Until the last step, all the sessions that passed between both ends in which subsystem X was indicated (local in A and remote in B) worked with key V4. From the moment V5 is active at both ends, they start working with this last one. Note that initially V1, V2, and V4 can be activated manually at both ends. Later, V1 is lost in entity A (it can no longer operate with V1). Until V5 is active at both ends, there are only 2 key sets and not 3, with which to operate. --- # 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/key-manager/introduction/subsystem-example-3.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.