> 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/cambios-onesait-editran-v5.1-respecto-a-onesait-editran-v5.0.md).
# Changes in Onesait Editran V5.1 compared to Onesait Editran V5.0
## Phase 1
### Issues.
Modifications have been made:
* Wait 1 second when several files are received; the user downloads with the time variable and it is the same DSNAME as the previously downloaded one
* Avoid retransmitting the same file when a load arrives before the subsequent one finishes.
* Session deletion was not allowed when it was loaded with cryptography 2.2
* Allocation changes. The sw-aloc used to deallocate the application file if the session had space adjustment was left uninitialized.
* The EDP time matches the time of the subsequent A2R, so the buffer was updated to unavailable.
* Send SPC and SRC with the appropriate length
* Changes in the space calculation for the SACO file.
* Translate the file start when there is more than one.
* Problem when downloading as a single file in generation files.
* In the gateway configuration query it only returned one.
* Loop in file retrieval for a session with more than 9999 files.
* Modification in the program that lists sent and received items to output the number of records in application files.
### Functionalities.
* **Mass export of RSA keys.**
* **File access through GESTOR.**
> All file accesses from the programs are unified into managers.
* **Revocation control in Onesait Editran /FF**
> XAdES electronic signature. Include revocation control.
* **EXCII access for the Onesait Editran /FF module**
> EXCII functionality is also implemented for access to all files in the Editran/FF module.
* **Onesait Editran /XML**
> Conversion of flat file to XML and vice versa for SEPA Standard 34.14.
* **HFS files**
> Files residing in the z/OS USS partition are sent and received.
>
> By including the file names in the sessions, a directory or a file name within a directory can be specified, and it can use the variables accepted by UNIX (POSIX portable file name character set).
>
> The full name must not exceed 44 bytes, such as Modified and Binary language (not translated).
* **Display the user who launches the request**
> Output in the P and G log the user who launches the request from the operation menus.
* **Binary file formatting**
> A field is added in profiles to adjust the record length of binary files on reception.
* **File 54 removal**
> Intermediate files ZTBGFE54 and ZTBFR54 are removed for conversion of compressed variable files.
* **New parameter to enable the session.**
> A new parameter is included to enable-disable the session.
## Phase 0
### Issues.
Modifications have been made:
* File queues. Error messages were being output and overwritten by the program name.
* Generic modification of Editran/P profiles. When a replacement of Connection Type was selected and change was selected without taking position into account, it did not do so for those that did not match in position. In the validation of the changes it did not take the generic selection of the lines into account.
* When downloading a file from an ASCII loaded with a length greater than 32760, file allocation failed. Modified so it ends in error due to unknown file characteristics.
* Exchange key management, it was downloaded incorrectly between two 5.0 versions if the sender loaded with remote G version 4.1
* Rejection by invalid calling endpoint did not work properly
* A GETMAIN was done without a FREEMAIN
* Generic modification of Editran/G profiles. It did not update the files properly when compression or translation was changed
* File queue management. When a load is requested from JCL-operator (not from CICS) and the session was a queue load, it did not validate the depth correctly
* In x25, if the fictitious LU is REL, sometimes it does not try the second one (in case there was no second PROXY line). It is modified so that it only happens if there is no second x25 line
* In cross-connections, it did not work properly in x25
* It calculated incorrectly the time to launch a timeout due to hourly window retry
* Errors in single-file download. Depending on the order and type of files, errors such as ZMA0098 ZTBGBG40 ERRONEOUS APPLICATION RECORD OF WRONG LENGTH DETECTED may occur. Binary files were not downloaded as VS with download file format 'E', single file 'S', and only one file was received. Record structure was lost (records longer than the original file were written) when downloading binary files with single file 'S', download file format 'F', and more than one file was received. In downloads, when several files with different characteristics arrive and the last two have the same ones (file type and length) and are fixed, the SACO creates it as fixed.
* Display the CICS errors that occur in batch
* When generating RSA keys in KEY MANAGEMENT, it always called the new EXCI program even though the environment had Modify
* When batch fails, it calls the user program. This returns zeros in rc, so the subsequent process does not refresh the previous failure
* The block size is increased for the space calculation of the auxiliary compression and conversion files of the send and receive converters. 27998 is used as the maximum block size instead of 6229. The files are also allocated with BLKSIZE zero. Converters are modified (to block the compressed file and file 54 up to 27998, and remove the BLOCKSIZE).
* Statistics. The history control record was incorrect when it reached 9999 records. Even if more records had been specified, at that number it wrapped around the file
* The number of bytes does not match the sender. Before it gave an error on reception and now it is detected on loading. In large files, which use multivolume during loading, it seems to load correctly, but there is a problem. The technical solution, if you do not have this modification, is to place the intermediate files on a specific SMS volume
* When the post-reception process fails in GC, if it remains in received state and the JCL is relaunched from batch operator (instead of from CICS), the subsystem search fails
* Usually, when remote ECP(8) arrives, if the send file is not prepared, A1P is launched with function 03. In this case, the modification consists of launching A1P with function 01 if ECP(8) and the calling endpoint is R and automatic disconnection is S.
* Be able to transmit more than 4 GB when file space adjustment is requested
* In the G log there are 4 positions for JOBID. It is increased to 5 because JOBID reaches higher ranges.
### Features
* **Incompatibility with Onesait Editran < 4.0 (phase 00 CICS-IMS)**
> Compatibility with version < 4.0 has been removed. The migration program consists of 2 JCLs. The first one produces a listing of incompatible sessions, so before running the second JCL, you can contact the entities with problems and modify them in their non-migrated profiles, since the remote entity will probably, although it appears as Editran < 4.0, have an Editran > 3.1 and they can bring their remote versions up to date.
* **Add new variable in download file name (phase 00 CICS-IMS)**
> A new variable is added to the download file name: "%E" (decade).
* **CICSPLEX-SYSPLEX (phase 00 CICS)**
> CICSPLEX functionality is implemented (included in production since 2010 in a pilot entity). The following actions have been carried out:
>
> * x25 terminals. Using TX is recommended; however, the functionality has been implemented so that a group of terminals (a line or a SUBADDR) is confined to a single CICS. In this way, activation-deactivation-INQUIRE of the terminals is performed only on the CICS in which they were defined. Graphical interface. The CICSPLEX SM, SCOPE and CONTEXT version is registered.
> * Listener. It allows starting several listeners in several CICSs on the same port (and different IP)
> * Control of which CICS a terminal is in, control of whether we are in CICSPLEX, and control of the CICSNAME and SISYD associated with a CICSPLEX
> * The JCLs that perform DEL/DEF of VSAM have been modified so that they are not reusable
> * MQ changes to be compatible with CICSPLEX, direct access to buffer files when they are EXCII
> * Treatment of INQUIRE-SET files
> * Modifications in listener and PLTS
> * Implementation of IP stack backup in IP, PROXY and TX connections. When retries exceed the limit for a connection type, everything is restarted again in another CICS, if possible
> * In START TRANSID with terminal, the SYSID is searched.
>
> EZACONFG configuration file, treat it as if there were no SYSPLEX, that is, open it if it is closed.
>
> Timeout manager. Starts timeouts with SYSID.
>
> Monitoring manager. Start the clients to perform loopback on the real CICSs where the listeners to which the loopbacks arrive are defined.
>
> Several ZTBZs (each in a different CICS) and only one working
* TSPOOL control
> Must be registered in CICS (PPT):
>
> Programs ZTBPOSPX, ZTBPOCPS (special compilation method with the CICSTS31.CPSM.SEYULOAD library; in CICSTS31.CPSM.SEYUPROC(EYUEITVL) there is a compilation proc.
>
> New Editran/MQ JCL
>
> ZTBCJG11, ZTBCJG22, ZTBCJP4E, ZTBCJP5E, ZTBCFG31, ZTBCPEXC
>
> Must be deregistered in CICS (PPT-MQ):
>
> Programs ZTBCG12
>
> New JCLs (EGDC.ZTBP.JCLS): ZTBCJG11, ZTBCJG22
* **Removal of Confirmed Exchanges functionality (phase 00 CICS-IMS).**
> That functionality is removed because it is not applicable in any entity. Therefore the ZTBI\*\*\*\* resources are removed (files, programs, TRANSID, JCL, etc.)
>
> Must be deregistered in CICS (PPT):
>
> Programs ZTBIO000, ZTBIO001, ZTBIO002, ZTBIO003
>
> MAPSET ZTBIM00, ZTBIM01.
>
> Must be deregistered in CICS (FCT):
>
> Files: ZTBI\*
* **Implementation of EXCII functionality in all Onesait Editran files (phase 00 CICS).**
> EXCII functionality and manager programs are implemented for all files (states, G log, statistics, alarms, FF log, key management, file queues, CRIPTOlib/DES, CRIPTOlib/RSA, etc.
>
> Must be registered in CICS (PPT):
>
> Programs ZTBPOI30, ZTBEOGPE
>
> Must be registered in CICS (PPT-RSA):
>
> Programs SCRKGEOO
>
> Must MODIFY the current FCT of all product files, ZTB\* files and FICHK\* files, so that they have the following characteristics:
>
> ADD(YES) DELETE(YES) READ(YES) UPDATE(YES)
>
> If you usually use an EXCII connection (local environment, JCLS notification parameter (M/E): E), you can change the SHR of all files, except matrix buffers, from 3,3 to 2,3 (not necessary)
>
> It is recommended to define the files as LOG NONE and NOREUSE, for SYSPLEX-CICSPLEX reasons.
>
> It is recommended to abandon matrix and specific buffers and use EXCII buffers, which provide better performance.
* **TCP and PROXY releases (phase 00 CICS-IMS).**
> Functionality is implemented to send and receive disconnects in TCP messages, so that the user can know the real reason for the socket drop (if both are seen as > 5.0). Until now, in all situations, one of the endpoints closed the socket. For example, if an entity has a defined schedule and they call it outside that schedule, the calling entity will know why the socket was closed.
>
> Must be deregistered in CICS (PPT):
>
> Programs ZTBPO202, ZTBPO203
* **Increase in the number of emails in alarms (phase 00 CICS-IMS).**
> Alarms are expanded to 3 emails, so that several users can be notified of the correct or incorrect operation of a transmission.
* **Resetkey (phase 00 CICS-IMS).**
> Functionality is implemented to delete exchanged 2.2 keys without needing to deregister and re-register the session. This deletes the exchanged keys and initializes the session as if it had been created again.
* **Download confirmation (phase 00 CICS-IMS).**
> Functionality is implemented to confirm remote downloads (not possible with specific buffers), so that the sender does not launch the post-send process until it knows that the receiver downloaded correctly (its post-reception procedure finished correctly). If the presentation session has several transmissions, only one post-process is launched (either send or receive), corresponding to the last transmitted one, so that statistics and states are updated in the CICS itself as the transmissions finish. It works as follows: if the sender specifies E (or X) and the receiver R (or X), when the send ends the sender does not launch the post-process. Instead, it starts a timeout to see how the remote download ends. If the timeout expires without the receiver having connected and indicated the result of the download, the sender connects and asks about it. If it is correct, it launches the post-send process; if it is not correct, it launches the post-reception process; if it has not finished, it launches another timeout until the retry limit is reached (in which case it throws an exception). Likewise, when the receiver finishes downloading the presentation, it connects to the sender to indicate the correct download (in which case the sender launches the post-send process) or the erroneous download (in which case the sender throws an exception). It could happen, for example, that the receiver has a remote calling endpoint, the sender has exhausted all retries and the receiver has not finished the post-reception process, in which case there would be no way to tell the sender that the post-reception process has finished. The sending operator must manually interrupt the sending presentation and process the post-send presentation (Editran/G operator options)
* **Character table negotiation in Editran/P (phase 00 CICS-IMS).**
> The ASCII-EBCDIC parameter is removed in Editran/P. If V > 50 and the receiving endpoint that calls us is ASCII, we indicate in the SAR that the control language is EBCDIC. In outgoing connections, we always indicate that the control language is EBCDIC. Therefore, only between two ASCII endpoints will they transmit with ASCII control language.
* **Management of TCP-PROXY-TX buffers (phase 00 CICS-IMS).**
> The user is given the possibility to configure, for both TCP-PX and TX, the TCP buffers used (sendbuffer and receivebuffer), both when the connection is incoming (implemented in the local environment) and when the connection is outgoing (implemented at the transmission session level. In outgoing connections, therefore, the user can adapt the buffers to each transmission. That functionality allows higher transmission speeds. Also review the MTU size in your IP stack and the local-environment send time.out milliseconds parameter (recommended 200 milliseconds).
* **Increase in transmission speed in TCP-PX-TX (phase 00 CICS).**
> The product has been redesigned so that processes are multiplexed, significantly increasing transmission speed:
>
> In outgoing sends, the core reads data from the sender buffer and writes it to a TS queue. The TCP process reads that TS queue at the same time and sends whatever is there to the network, so by working in parallel there are no dead transmission periods. Previously the core read until the end of each burst and at that moment the TCP process sent everything to the network.
>
> In incoming receptions, the TCP process reads data from the reception buffer and writes it to a TS queue. The core, at the same time, reads from that queue and writes the data to the receiver buffer, so by working in parallel the core is writing to the buffer while the burst is being received over the network. Previously the client-server child collected the entire burst and the core wrote it afterwards.
>
> Combine this functionality with the buffer size, the MTU, and the send time.out milliseconds parameter, and you will achieve higher transmission speeds.
---
# 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/cambios-onesait-editran-v5.1-respecto-a-onesait-editran-v5.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.