> 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-ims-en/operacion/primerospasos/administrador-de-onesait-editran/aplicacion.md). # Application This screen is accessed with option 3 of the administrator menu, with 1.3 of the general menu, and by executing or cancelling the invoked function. ``` ------------------------------------------------------------------------------ | 21/06/26 ADMINISTRATOR EDITRAN | | 11:18:09 APPLICATION 5.3 | ------------------------------------------------------------------------------ | | | | | | | A ADD | | | | B DELETE | | | | C QUERY | | | | M MODIFICATION | | | | | | | | OPTION : M | | APPLICATION CODE : TEST | | | | | | | | | ------------------------------------------------------------------------------ ``` Enter the desired option and the code of the presentation application. ``` 21/06/26 11:20:47 APPLICATION MODIFICATION EDITRAN 5.3 ------------------------------------------------------------------------------ APPLICATION-CODE.: TEST DESCRIPTION.: DATA IN APPLICATION LOAD TYPE (N/A/Q): N DIVISION CRITERION (V/S/N)..: S LZW ADJUSTMENT PERCENT (0-99)......: 00 TRANSMISSION CONVERSION TABLE...: TRANSFER ON RECEPTION (A/E/N)..: N RECEPTION CONVERSION TABLE.: PARAMETER.: APPLICATION DATA IN TEST APPLICATION DELETE BUFFER AFTER TRANSMISSION.....: S DELETE BUFFER AFTER RECEPTION..: S REQUEST DOWNLOAD ACKNOWLEDGMENT (S/N).: N WAIT TIME (MINUTES).: 00 START TIME (HHMMSS): 000000 END TIME (HHMMSS): 000000 ``` * **APPLICATION CODE**: Presentation application code. Consists of 6 alphanumeric characters * **DESCRIPTION**: Name of the presentation application. It is an informational parameter. * **LOAD TYPE**: 'N' normal, 'A' cumulative and 'Q' by file queues. With cumulative load type, the buffer can be reloaded with new application files, provided transmission has not started. The requirements for the system to work in cumulative load type are: * It is assumed that the profiles sensitive to the load will not be modified between processes belonging to the same presentation. * The transmission request will behave as before in all cases. That is: load and transmission in finished state or not loaded, and transmission in loaded or transmitting state. Therefore, if a session defined with cumulative load has already been loaded and transmission is requested, no new data will be loaded for it. * The load request in not loaded, loaded, transmitting or finished state will trigger cumulative loading of the buffer. * Once the presentation state control has been passed, in transmitting state the buffer control record is accessed and it is checked that it is really not transmitting and that more files can be loaded. If so, it is marked as unavailable for Editran so that transmission does not begin during the file loading process. When loading is finished, the buffer is made available again. * It can only be done with a transmission session. * **DIVISION CRITERION (V/S/N)**: Only if several transmission sessions are going to be used for the presentation. The following values can be specified: * V: The transmission application information would be distributed equally among the different buffers, with a minimum of 600,000 bytes per buffer. This means that some of the transmission sessions defined in the presentation might not be used. * S: Distribution by file or by batch marked by synchronization points, depending on the Converter. Successive complete files or batches would be assigned to each transmission buffer. * N: No division is performed. Recommended value for a single transmission session in the presentation. * **LZW ADJUSTMENT PERCENT (0-99):** Adjustment percentage of how compression will behave, to apply it to the creation of intermediate files. It can take values from 00 to 99, and indicates the compression effectiveness percentage from when the application file is taken until it is passed to the buffer; for example, in a normal situation an 80 percent compression is usually given. This parameter is used for the following: * If ADJUST FILE CREATION SPACE.= 'S' (local environment), the adjustment will be applied to the primary space definition of the auxiliary load files. For example, if 80 percent adjustment is available, the file size will be adjusted to 20 percent. * If ADJUST FILE CREATION SPACE.= 'N', it will only be applied in the creation of the ZTBGFE54 file to "increase its size". For example, if 80 percent adjustment is available, the size will be calculated by dividing the primary record space by 0.20. This file is used in the case that 3 circumstances are met: * That remote-IGA version > 5.0 and < 5.3 * That there is compression and/or encryption * That one of the following 2 is met: * Application files in R format and variable * That there is translation and/or conversion. * **TRANSMISSION CONVERSION TABLE**: Name of a table resident in the ZTBGBTCO file, which converts the characters to be sent from the application file into the characters indicated in that table (it does not change the alphabet of the data, but adapts it to another table of the same alphabet). If the application file alphabet is EBCDIC, there will be a table in the ZTBGBTCO file called Transmission-conversion-table + E. If it is ASCII it will be called Transmission-conversion-table + A. If you want to transmit 2 files with different alphabets, both tables will be applied. * **TRANSFER ON RECEPTION (A/E/N)**: A (ASCII), E (EBCDIC) and N (Do not translate). Indicates whether we want to perform translation on reception and to which alphabet. It will only be translated if the file comes in an alphabet opposite to that of the translation. If the file has no alphabet, it will not be translated. * **RECEPTION CONVERSION TABLE**: Name of a table resident in the ZTBGBTCO file, which converts the characters received in the reception file into the characters indicated in that table (it does not change the alphabet of the data, but adapts it to another table of the same alphabet). If the alphabet of the received application file is EBCDIC, there will be a table in the ZTBGBTCO file called Reception-conversion-table + E. If it is ASCII it will be called Reception-conversion-table + A. If 2 files with different alphabets are received, both tables will be applied. See manual [Generic Application Interface](/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/interfaz-generica-de-aplicacion.md). (Appendix F) * **PARAMETER**: Data needed for Macrofile process. Manual [Generic Application Interface](/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/interfaz-generica-de-aplicacion.md). (Appendix C) * **DELETE BUFFER FILE**:. * After transmission: If S, the transmission buffer or buffers are deleted when the transmission presentation ends (recommended value) * After reception: If S, the reception buffer or buffers are deleted when the reception presentation ends (recommended value). * **REQUEST DOWNLOAD ACKNOWLEDGMENT (S/N)**: Allows the sender of the files to request that the remote Editran confirm the download of those files * **WAIT TIME (MINUTES)**: It is the time that the sending Editran will wait for the download acknowledgment to arrive and during which a new send will not be allowed * **START TIME and END TIME**: Time window for establishing a connection or starting a transmission or reception. When both fields are 0, it indicates that there is no time window, and the above operations can be performed whenever desired. This value applies to local connection, transmission or reception requests and to remote connection requests. ℹ️With ENTER, the add operation will be performed. With PF3 you exit. The values of the data of a presentation application are passed to the presentation sessions of that entity, when they are added, as default values. The other options can be performed on a specific application, in which case it will appear the same as in the add operation, but with the fields protected. If it is done generically, the following screen will appear and you will select with an 'S': ``` 21/06/26 11:21:36 APPLICATION MODIFICATION EDITRAN 5.3 ------------------------------------------------------------------------------ S APPLICATION DESCRIPTION REC.TRAN DEL EMI DEL REC - ---------- -------------------- -------- --------- --------- PRB044 TESTS N S S PRB045 TESTS N S S PRB046 TESTS N S S PRB047 TESTS S S S PRB048 TESTS N S S PRB049 TESTS N S S PRB050 TESTS N S S PRB051 TESTS S S S PRB052 TESTS S S S PRB053 TESTS N S S PRB054 TESTS N S S PRB055 TESTS S S S PRB056 TESTS N S S PRB057 TESTS S S S PRB058 TESTS N S S PRB059 TESTS N S S PRB060 TESTS N S S ``` The removal of the profile of a presentation application will only be carried out if there are no presentation sessions associated with that application. --- # 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-ims-en/operacion/primerospasos/administrador-de-onesait-editran/aplicacion.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.