> 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/operacion/onesait-editran-administrator/application.md). # Application The screen that allows applications to be managed is displayed: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:09:34 APPLICATION | ----------------------------------------------------------------------------- | | | | | | | | | A ---> ADD | | | | B ---> DELETE | | | | C ---> QUERY | | | | M ---> MODIFY | | | | | | OPTION : C | | APPLICATION...: | | | | | | | | | ----------------------------------------------------------------------------- ``` If you want to query, delete or modify, without specifying a code: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:11:22 APPLICATIONS | ----------------------------------------------------------------------------- | SELECTION CRITERIA: | | APPLICATION.: ****** | | S APPLICATION DESCRIPTION RECV.TRANSL. DEL EMIT DEL RECV | | - ---------- -------------------- -------------- --------- --------- | | AAAAAA TESTS N S S | | AA0001 N S S | | ABEURA ABEURA A S S | | ABEURC DES ABEURC APPLIES N S S | | ABEURP DESC ABEURP APPLIES E S S | | ABEUR2 DES ABEUR2 APPLIES N S S | | ABEUR3 PRU PRU PRU TESTS E S S | | ACUMUL ACCUMULATIVE LOAD N S S | | ACUMUV ACCUMULATIVE LOAD N S S | | AESRSA AESRSA A S S | | AE9987 DEBT RECEIPT N N N | | AE9994 DEBT EMISS. PRE/DE N N N | | AE9998 DEBT RECEIPT N N N | | | | EXIT, ADVANCE, SELECT | ----------------------------------------------------------------------------- ``` Selecting that screen or specifying a code on the previous one: ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN ADMINISTRATOR EDITRAN 5.3 | | 12:11:22 APPLICATION | ----------------------------------------------------------------------------- | USER:CICSSITD D-T:20260411-140011 | | | | APPLICATION CODE.....: AAAAAA DESCRIPTION : TESTS | | LOAD TYPE..................: N ((N)ORMAL, (A)CCUMULATIVE, (Q)UEUES) | | DIVISION CRITERION (V/S/N)......: N ((V)OLUME,(S)YNC.FILE,(N)ONE) | | LZW ADJUSTMENT PERCENTAGE (0-99)..: 50 EMISSION CONVERSION TABLE...: | | TRANSLATE ON RECEIPT (A/E/N)..: N RECEIPT CONVERSION TABLE.: | | PARAMETER.: | | DELETE BUFFER AFTER EMISSION.....: S DELETE BUFFER AFTER RECEIPT..: S | | REQUEST DOWNLOAD ACKNOWLEDGEMENT (S/N).: N WAITING TIME (MINUTES).: 00 | | | | | | USER PROGRAMS | | BEFORE EMISSION..........: BEFORE RECEIPT...........: | | AFTER EMISSION.......: AFTER RECEIPT........: | | EXCEPTION...............: RECEIPT EXIT..........: | | | | | | EXIT | ----------------------------------------------------------------------------- ``` * **USER**. Contains the last user who modified the record. It is common to all profile records. * **D-T:** Date and time of the last modification. * **DESCRIPTION**: Name of the presentation application. It is an informational parameter. * **LOAD TYPE**: > - ‘N’ normal > - ‘A’ accumulative (recommended value) > - ‘Q’ File queues. With type ‘Q’, editran points to the file pending transmission and loads/emits it when it can. With accumulative load type, reloading of the buffer with new application files is allowed, provided transmission has not begun. The requirements for the system to work in accumulative load are: > * It is assumed that load-sensitive profiles will not be modified between processes belonging to the same presentation. > * Loading is performed according to mode 2.1 or higher. That is: the CSB' file format is maintained with the ZTBGBG10 converter. > * The emission request will behave as before in all cases. That is: load and emit in the finalised state or not loaded, and emit in the loaded or emitting state. Therefore, if a session defined with accumulative load has already been loaded and emission is requested, no new data will be loaded for it. > * The load request in the not loaded, loaded, emitting or finalised state will trigger accumulative loading of the buffer. > * Once the presentation state control has been passed, in the emitting state the buffer control record is accessed and it is checked that it is really not emitting and that loading of more files can be performed. If so, it is marked as not available for editran/P so that emission does not start during the file loading process. When loading ends, the buffer is made available again. > * It can only be performed with a transmission session. > * The CICS buffer file cannot be specific, since it must be accessible from both CICS and batch simultaneously. * **DIVISION CRITERION**: Only if several transmission sessions are going to be used for the presentation session. The following values can be specified: > - V: The application information for emission 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: Split by file or by batch marked by synchronisation points, depending on the Converter. Successive complete files or batches would be assigned to each emission buffer. > - N: No splitting is performed. Recommended value for a single transmission session in the presentation. * **LZW ADJUSTMENT PERCENTAGE (00-99)**. Adjustment percentage of how compression will behave, to apply it when creating intermediate files. It can take values from 00 to 99, and indicates the percentage effectiveness of compression from when the application file is taken until it is passed to the buffer; for example, in a normal situation, 80 percent compression is usually given. This parameter is used for the following: > - If adjust file creation space = ‘S’ is available (local environment), the adjustment will be applied to the definition of the primary space of buffers, csbnedi and compressed files. For example, if 80 percent adjustment is set, the size of the above files will be: > * For compressed files, the size of the application file divided by 5. > * For buffer and csbnedi files, the sum of the sizes of the application files divided by 5. > - If adjust file creation space = ‘N’ is available, it will only be applied in ZTBGF54 to "increase its size to the currently calculated one". ZTBGF54 is currently calculated based on the PHS.PRIM. (REGS) field, so that if adjustment 80 is coded, in this case ZTBGF54 will be calculated as it is now, but by five. If the 3 circumstances listed below are met, the intermediate ZTBGF54 file is created (which is not compressed). > * That remote iga version > 4.0 > * That there is compression and/or encryption > * That one of the following 2 is met: > * Application files in R format and variables > * That there is translation and/or conversion. * **EMISSION CONVERSION TABLE**: Name of a table residing in the ZTBGBTCO file, which converts the characters to be sent from the application file to the characters indicated in that table (it does not change the language of the data, but rather adapts it to another table of the same language). If the application file language is EBCDIC, there will be a table in the ZTBGBTCO file called Emission-conversion table + (E/F). If it is ASCII, it will be called Emission-conversion table + (A/B). If two files in different languages are to be emitted, both tables will be applied. * **TRANSLATE ON RECEIPT (A/E/N)**: Indicates whether we want to perform translation on receipt and to which language. It translates to A (ASCII) or to E (EBCDIC), as long as the data language of the file is compatible for translation, that is, the 2 possible combinations are: RECEIVED FILE DATA LANGUAGE ‘A’ and TRANSLATE ON RECEIPT ‘E’, RECEIVED FILE DATA LANGUAGE ‘E’ and TRANSLATE ON RECEIPT ‘A’. Two files received in different languages cannot be translated on receipt. * **RECEIPT CONVERSION TABLE**: Name of a table residing in the ZTBGBTCO file, which converts the characters received in the receipt file to the characters indicated in that table (it does not change the language of the data, but rather adapts it to another table of the same language). If the language of the received application file is EBCDIC, there will be a table in the ZTBGBTCO file called Receipt-conversion table + (E/F). If it is ASCII, it will be called Receipt-conversion table + (A/B). If two files are received in different languages, both tables will be applied. * **PARAMETER**: Data required for the macro file process. * **DELETE BUFFER FILE**: Deleting a buffer should be understood as deleting data records. > - After emission: If S, the emission buffer(s) are deleted when the emission presentation finishes (recommended value). > - After receipt: If S, the receipt buffer(s) are deleted when the receipt presentation finishes (recommended value). * **REQUEST DOWNLOAD ACKNOWLEDGEMENT (S/N)**. This is to confirm whether a remote download is correct, so the sender will not load if it does not know this data or the timeout has not elapsed. It is not possible to operate with sessions with specific buffers. Verify them. Values > - ‘S’ - The endpoint that indicates this value, in its emissions, expects the remote side to confirm the remote download. > - ‘N’ - Do not confirm downloads. * **WAITING TIME (MINUTES).**: > 00-99 - Time the sender waits before being able to perform a new load if the remote side does not send the correct result of the download * **USER PROGRAMS**: Called by editran/G at the end of the pre/post processes for emission/receipt and exception. These programs are provided by the user and will be called at the end of the corresponding processes of the presentation and in each exception procedure. The communication area passed to them contains all the information used by editran/G (profiles of the local and remote entities, of the application and presentation session of editran/G, and profile of the editran/P sessions). If you want to use any file in them, it must be included in the corresponding procedure. ℹ️The values of the data of a presentation application are passed to the presentation sessions of that entity, when they are created, as default values. The deletion of a presentation application profile 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-cics-en/operacion/onesait-editran-administrator/application.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.