> 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/reinstallation/introduction.md).

# Introduction

The reinstallation process for editran 5.3 can be broken down into two lines of action; the first consists of installing the product itself, and the second refers to the changes that must be made to the applications that use editran as a result of calls to the interfaces with editran and the use of the product's own resources.

To perform migrations, whether between phases of the same version or between different versions, it is recommended to follow these steps:

* If the version and phase that were installed are unknown, check them with INDRA so that it is known in advance which migration will need to be carried out.
* To find out about the new resources (programs, files, transactions, etc.) that have been created from the version-phase currently installed to the version-phase you are about to install, consult the manual [About Editran 5.3 - Versioning Information](/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/sobre-editran-5.3-informacion-de-versionados.md). In it, all functionalities are organized by phases-versions. You must locate the currently installed phase and check from it all the new resources to define (this will save you from rereading all the documentation to learn the new resources). If you acquire products developed in phases earlier than the one you had installed, you must likewise verify those definitions.
* Extension of limits in transmitted files.
  * The primary and secondary space of dynamic file allocation is extended to 7 digits.
  * The length of the application file name is increased and the format of the ZTBGFCAR file list is modified. This affects the applications (see point 2)
* The JCLs for migration from one phase to another of the same version normally adapt the profile files by initializing new fields, without affecting existing data.
* The documentation available on INDRA's website corresponds to the latest available phase of the product.
* When a new phase is received, within the same version, if JCLs are received, they must be readapted with the ZTXINST CLIST so that it uses the appropriate names for each entity.
* Migration to intermediate development phases is not possible; that is, migration will be performed to the latest released phase.
* If a new version is received, a license file will be received. The ZTBLJG02 JCL will be run to incorporate the product license into the editran/P and editran/G profile files.

Below is a table with the different product version-phases: 

<table data-header-hidden><thead><tr><th width="123.061767578125"></th><th width="120.09869384765625"></th><th width="137.2181396484375"></th><th width="118.946533203125"></th><th width="113.0205078125"></th><th width="114.66650390625" valign="top"></th></tr></thead><tbody><tr><td>Opening Date</td><td>Closing Date</td><td>editran 5.0 Phase</td><td>editran 5.1 Phase</td><td>editran 5.2 Phase</td><td valign="top">editran 5.3 Phase</td></tr><tr><td>08/06/2007</td><td>31/03/2008</td><td>Phase 0</td><td> </td><td> </td><td valign="top"> </td></tr><tr><td>01/05/2008</td><td>15/06/2009</td><td>Phase 2</td><td> </td><td> </td><td valign="top"> </td></tr><tr><td>15/06/2009</td><td>30/09/2011</td><td> </td><td>Phase 0</td><td> </td><td valign="top"> </td></tr><tr><td>01/10/2011</td><td>01/10/2014</td><td> </td><td>Phase 1</td><td> </td><td valign="top"> </td></tr><tr><td>01/10/2014</td><td>14/04/2016</td><td> </td><td><p>Phase 3</p><p>End of development</p><p>End of version</p></td><td> </td><td valign="top"> </td></tr><tr><td>14/04/2016</td><td>08/11/2017</td><td> </td><td> </td><td>Phase 0</td><td valign="top"> </td></tr><tr><td>08/11/2017</td><td>14/10/2023</td><td> </td><td> </td><td>Phase 1,2</td><td valign="top"> </td></tr><tr><td>14/10/2023</td><td>10/11/2024</td><td> </td><td> </td><td><p>Phase 3</p><p>End of development</p><p>End of version</p></td><td valign="top"> </td></tr><tr><td>10/11/2024</td><td>10/03/2025</td><td> </td><td> </td><td> </td><td valign="top">Phase 0</td></tr></tbody></table>

&#x20;


---

# 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/reinstallation/introduction.md?ask=<question>&goal=<endgoal>
```

`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.