> 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-1.md). # Subsystem example 1 1. My entity has 2 local codes, 1111 and 2222. * 1111 will connect with remotes 3333, 4444 and 5555 * 2222 will connect with remotes 7777 and 8888 2. My subsystems will be called: * If they are OWN * With remotes 3333, 4444, 5555, the own subsystem S (semiannual). * With remotes 7777, 8888, the own subsystem A (annual) * If they are FOREIGN * With remote 3333, FOREIGN subsystem 3 * With remote 4444, FOREIGN subsystem 4 * With remote 5555, FOREIGN subsystem 5 * With remote 7777, FOREIGN subsystem 7 * With remote 8888, FOREIGN subsystem 8 3. The sent – received keys and their versions: * With the remotes of OWN subsystem S, I generate and send them 45 keys * With the remotes of OWN subsystem A, I generate and send them 65 keys. * Each RSA remote has sent me 22 keys.


Subs	Type	Local	Remote	Keys	Key 1 Operational	Key 2 Operational	Key 3 Active	Comments	Order
S	OWN	1111	0000	RSA	43	44	45	Exports to order 4, 5 and 6	1
S	OWN	2222	0000	RSA	43	44	45	Exports to order 8	2
A	OWN	2222	0000	RSA	63	64	65	Exports to order 10, 11	3
S	OWN	1111	3333	RSA	43	44	45	Exported from order 1	4
S	OWN	1111	4444	RSA	43	44	45	Exported from order 1	5
S	OWN	1111	5555	RSA	43	44	45	Exported from order 1	6
S	OWN	2222	5555	RSA	43	44	45	Exported from order 2	8
A	OWN	2222	7777	RSA	63	64	65	Exported from order 3	10
A	OWN	2222	8888	RSA	63	64	65	Exported from order 3	11
3	FOREIGN	1111	3333	RSA	20	21	22	The subsystem that the remote indicated to us	16
4	FOREIGN	1111	4444	RSA	20	21	22	The subsystem that the remote indicated to us	17
5	FOREIGN	1111	5555	RSA	20	21	22	The subsystem that the remote indicated to us	18
5	FOREIGN	2222	5555	RSA	20	21	22	The subsystem that the remote indicated to us	20
7	FOREIGN	2222	7777	RSA	20	21	22	The subsystem that the remote indicated to us	22
8	FOREIGN	2222	8888	RSA	20	21	22	The subsystem that the remote indicated to us	23

You can now see that, for example, the records with order 1, 4, 5 and 6 contain the same keys; that is, we have generated the same keys for several remotes. The same happens with those of order 2, 8, or also with 3, 10 and 11. **The keys are not lost; once exported to a remote, they remain there.** What happens if we generate keys for an own RSA local subsystem with local code xxxx + remote code zeros, generate one version, do not export it to all the remotes we had in that subsystem, and then generate a new key version in the own RSA local subsystem with local code xxxx + remote code zeros? In principle, nothing happens, because those remotes keep the last exchanged key, that is, the key with a lower version. It is as if in the record for order 1 the key of version 45 were active and in those of order 4, 5, 6 version V44 were active. However, it may happen that, if we do this, we cycle through all 99 options and end up overwriting the remote that was in that group. Example. In the record for order 4, we have exported only key 45, and in the record for order 1 we have generated 99 key versions starting from V45. If we generate one more, we will overwrite the label and key of v1, and therefore that remote that did not receive an export will stop working. --- # 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-1.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.