> 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/electronic-signature/requirements.md). # Requirements 1. Have editran version 5.2 or higher. 2. License. Have contracted the editran/FF product. 3. JAVA (see [Manual\_de\_Instalacion\_y\_Usuario-editran-FirmayVerificacion-CICS-IMS\_v7.1.1](/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/editran-ff-instalacion-firma-y-verificacion-v7.1.1.md)). * Have Java 7 or higher correctly installed. * Have the corresponding Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files installed. Be careful whenever Java is updated, because these files may be deleted during the update process and you may have to install them again. This is no longer necessary starting with Java version 8. * If you want to use editran/XAdES to sign, the corresponding software (cryptographic modules) for each cryptographic card you want to use must be installed. * A Java TCP server for UNIX services, which must have an address and a port on which to listen for requests made from editran on MVS. * Access to ZOS UNIX services --- # 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/electronic-signature/requirements.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.