> 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/download-cics-version/operations-to-perform-upon-receiving-the-product/software-reception.md). # Software reception Editran can be received in different ways: * Via editran (usually for reinstalls). * Via XMIT (new installations without connectivity to INDRA). When an entity receives editran, it normally receives several files, depending on the different Editran products it has contracted and, within each product, depending on the software received (for example, JCLs, executables, etc.). Also, editran license files may be received. There are therefore different types of files in terms of format: sources, JCL, executables and licenses. According to their content, there are the following products, in addition to the main editran/P and editran/G package: 1. TCP/IP. TCP/IP communications interface. 2. DES or AES. Cryptography. DES or AES key algorithm. Within this option, the following sub-options may occur: 1. The client needs to have ICSF. In this case, it is only necessary to receive editran DES or AES APIs for ICSF. 2. RSA Cryptography. RSA key algorithm. The RSA algorithm requires DES functions, which will run on ICSF. 3. TDES. Triple DES cryptography. Delivered with the DES algorithm. 4. AES. Triple AES cryptography. Delivered with the AES algorithm. 5. LZW. editran/G data compression with the LZW algorithm. 6. Editran/E. Statistics, monitoring, and alarms. For alarms, it requires receiving software for host and software for UNIX-WINDOWS. 7. Editran/FF. Electronic file signature. 8. Editran/PROXY. editran TCP/IP-to-TCP/IP data gateway. Requires receiving software for host and software for UNIX-WINDOWS. When an entity receives software, it will normally be divided according to the contracted products. 👉 An example would be the following: Version 5.3 phase 00 has been loaded via editran, which corresponds to: 1. editran/P+/G JCLs (JCLs and procedures). 2. editran/P and G executables. 3. ICSF CRYPTOGRAPHY API executables. 4. ICSF CRYPTOGRAPHY JCLs. 5. License file 5.3 for ENTITY XXX (9999) (editran/P, editran/G, TCP, DES, Triple DES, AES, RSA). In the previous example, the editran/P and editran/G standard has been loaded in the first two files. The CRYPTO API software is included in files 3 and 4. Finally, a license file is included that allows the use of the software described above.", These files are divided into 3 types: * JCLs (files 1 and 4). * Executables (files 2 and 3). * License (file 5). ℹī¸ Sometimes, an entity does not require a license, since it already has one in force and only wants to update software from a more recent phase of the same editran version it has in production. Other times, the only software received is the license, which is about to expire. ## License receipt If a license is received, it means it will be updated. In this case: * If a version higher than 5.0 phase 0 is received, run JCL ZTBLJG02 with the received file, so that it is incorporated into VSAM ZTBPFPE and ZTBGFPER. ## Receipt of new version Receiving the new version always implies receiving the following: * editran/P and editran/G JCLs. * Executables. * License for the new version. * Other (JCLs – executables), contracted products (if they were not loaded in the previous ones). ## Receipt of new phase In this case, only what has been modified between the production phase and the updated phase should be delivered. However, if more than one phase has elapsed between the two, the normal practice is to update all the software again, so as to avoid errors due to lack of updating. In this case, the license will arrive only if needed for expiration reasons. --- # 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/download-cics-version/operations-to-perform-upon-receiving-the-product/software-reception.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.