> 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/appendix/return-codes-returned-by-the-encryption-interface.md).
# Return codes returned by the encryption interface
**Return codes and reasons for editran key management**
Once the “active” label has been extracted, its associated key (FICHKRSA, FICHKDES or CKDS) is queried and, in case of error, other return codes/reasons occur.
For example, if in the batch interface when it loads, the label does not exist (active label+version, indicated in the ZTBPFGC file, key management), in the FICHKRSA file or in CKDS there will be an error on load or download, and displays, for example:
```
LOG Editran/G: ZTG0175: ZTBGBG10: ERROR ENCRYPTING THE APPLICATION FILE
Display in job for DES: ZTBSBD02: Error in key generation. (return 97, reason 59)
Display in job for RSA: ZTBSBR04: Error in signature generation. (return 103, reason 16)
```
If the same case occurs in CICS, or in RSA key management, messages such as the following appear (reason 13 = eibresp2 = notfnd):
```
Editran/G log: ZTP0197: CRYPTOGRAPHY ERROR XXXXXX: 97 - 13 (ERRX)
Editran/GC display: PROGRAM: XXXXXXXX, RETURN=xxxxxxxx, REASON=00000013
```
In CICS, IT MAY HAPPEN that the label provided by key management is not found in FICHKRSA or FICHKDES-CKDS, AND IT REALLY EXISTS in those files.
The reason is that, sometimes, especially when there are numerous records in the VSAMs (batch processes), these files are not "AUTOMATICALLY REFRESHED IN CICS", so it may happen that the program does not find the label and a few minutes later it does.
It is therefore recommended to REFRESH THE FILE in the CICS teleprocessing monitor, so that when actions are taken including keys in those files, they are then closed and reopened in CICS.
---
# 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/appendix/return-codes-returned-by-the-encryption-interface.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.
