> 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-comun-z-os-en/sobre-editran-5.3-informacion-de-versionados/changes-in-onesait-editran-v5.3-phase-1-compared-to-onesait-editran-v5.3-phase-0.md).
# Changes in Onesait Editran V5.3 Phase 1 compared to Onesait Editran V5.3 Phase 0
## Phase 1
### Issues
The following issues have been fixed:
* **Adaptation to the handling of ESS warnings 03 and 04**
> The handling of warning codes 03 and 04 returned by the ESS is changed so that they are no longer considered errors. From this version onward, they are only reported to the customer as warnings.
### Features
* **Do not allow modification of active transmission sessions**
> Modification of transmission sessions is not allowed when they are not in an idle state, avoiding inconsistencies during use.
* **Simplification of the Issuance file parameters.**
> The parameters Original data alphabet and Translate on issuance are removed from the Remote Entity, Application, and Session administrator, so that the configuration of these aspects is managed exclusively through the parameters defined on the Issuance files screen.
* **Update of cryptography messages**
> Messages related to cryptography are updated to provide clearer information during issue diagnosis.
* **Batch processes**
> Batch processes stop accessing Editran/P profiles in order to avoid contention during execution
* **Expansion of data structures**
> The length of the following files is modified:
>
> * ZTBFFSAL, which changes from FB 300 to VB 1077.
> * ZTBFFCER, which changes from FB 3925 to VB 1024.
>
> As a result of this modification, the post-reception procedure is also adapted to work with the new structure of the ZTBFFSAL file.
### IMS
#### IMS issues
* **Validations in Editran/FF**
> The following validations are added on the General application parameters screen:
>
> * If Application type = Issuance (E) and Signature type = XAdES (X), only the XAdES signature template field may be filled in.
> * If Application type = Reception (R) and Signature type = XAdES (X), only the XAdES signature verification policy field may be filled in.
>
> In any other case, the corresponding validation error will be reported.
* **Rule creation**
> On the Create a rule screen, the Total number of signatures and Required number of groups fields no longer appear locked during creation, allowing them to be edited.
* **Quick download**
> An issue is fixed whereby a reception request (A2R) could be lost when a quick download was performed and the session had not yet been released.
* **Automatic reception**
> An issue is fixed whereby, under certain circumstances, the automatic reception indicator could be lost when receiving a file while the system was not prepared for it.
#### IMS functionalities
* **License inquiry**
> The license inquiry is modified so that, when the type of any of the products is X, the message is displayed:
>
> "ENTITY CODE AND PRODUCTS CORRECT. TYPE X PARTIAL LIC.".
* **Error message improvement**
> A more descriptive error message is provided when ZTBGFCAR is not reported in file queues during execution of the pre-issuance process.
### CICS
#### CICS issues
* **Trace logging optimization**
> The generation of traces is modified to show a single message, avoiding duplicate messages.
* **Additional information in EXCI messages**
> In Editran/G messages executed in EXCI mode, information corresponding to RESP and RESP2 codes is added, making error diagnosis easier.
* **Application file inquiry**
> The application file inquiry is fixed to allow entering file names in lowercase.
* **Communication lines**
> The Local and remote communication lines screen allows DNS names to be entered using lowercase characters.
* **Key exchange**
> An error is fixed that prevented key exchange with a remote when the license did not include the use of compression on the remote side.
#### CICS functionalities
* **Download acknowledgment optimization**
> The operation of the download acknowledgment process is optimized to improve its performance.
* **Status inquiry**
> The status inquiry includes two new data items:
>
> * Result of the remote download.
> * Presentation identifier.
* **Terminology change**
> On the administration screens, the term Internal session is replaced with Transmission session, standardizing the terminology used in the application.
* **Remove default value '0' in Editran/GC subsystems**
> The value '0' assigned by default to the Subsystem field in GC is removed.
* **Replacement of the NIF field**
> On the Editran screens, the NIF field is removed and replaced by the CGO (Code) field.
---
# 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-comun-z-os-en/sobre-editran-5.3-informacion-de-versionados/changes-in-onesait-editran-v5.3-phase-1-compared-to-onesait-editran-v5.3-phase-0.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.