> 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-iseries-en/administracion-y-operacion/navigation-between-screens/main-menu/administrator/application-profile/add-application-profile.md).

# Add application profile

<figure><img src="https://2621858476-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F80nfuaOloGPZthms7LSJ%2Fuploads%2FBpbdOGA0CnF5W9W2hHWt%2Fimage.png?alt=media&amp;token=b305400e-486d-44f8-b35d-2c1a7e5f61c5" alt=""><figcaption></figcaption></figure>

* Description: Presentation application name.
* Load type: Offers the possibility of dynamic loading.
* A: Cumulative loading of application files into the "buffers" carried out in successive load requests.
* N: Only one load is allowed until the file is sent or initialized.
* Division criterion: Only in native mode 5.3.1 and in compatible 5.0, 5.1, 5.2, 5.2.1, 5.3, and if several transmission sessions are to be used for presentation. The following values can be specified:
* V: The application output information would be distributed equally among the different buffers, with a minimum of 400,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 send buffer.
* N: No division is performed.
* Output conversion table: Name of a table resident in the FGIGATCO file, which converts the characters to be sent from the application file into the characters indicated in that table (it does not change the language of the data, but adapts it to another table of the same language). If the application file language is EBCDIC, the FGIGATCO file will contain a table called Output-conversion-table + E. If it is ASCII, it will be called Output-conversion-table + A. If two files in different languages are to be sent, both tables will be applied.
* Translate on reception (A/E/N): Indicates whether we want to perform translation on reception and to which language. Translates to A (ASCII) or E (EBCDIC), provided that the language of the file data is compatible for translation, that is, the two possible combinations are: RECEIVED FILE DATA LANGUAGE 'A' and TRANSLATE ON RECEPTION 'E', RECEIVED FILE DATA LANGUAGE 'E' and TRANSLATE ON RECEPTION 'A'. It is not possible to translate two received files with different languages.
* Reception conversion table: Name of a table resident in the FGIGATCO file, which converts the characters received in the reception file into the characters indicated in that table (it does not change the language of the data, but adapts it to another table of the same language). If the language of the received application file is EBCDIC, the FGIGATCO file will contain a table called Reception-conversion-table + E. If it is ASCII, it will be called Reception-conversion-table + A. If two files in different languages are received, both tables will be applied.
* Delete buffer file: Deleting a buffer should be understood as CLRPFM of a file.
* After output: If S, the output buffer or buffers are deleted when the output presentation ends.
* After reception: If S, the reception buffer or buffers are deleted when the reception presentation ends.
* Request download acknowledgment (Y/N). This is to confirm whether a remote download is correct, so that the sender will not load if it does not know this data or the timeout has not expired. It is not possible to operate with sessions with specific buffers. Check them. Values
* 'Y' - The end that indicates this value, in its transmissions, expects the remote side to confirm the remote download.
* 'N'. Do not confirm downloads.
* Wait time (minutes).:
* 00-99 - Time the sender waits without being able to perform a new load if the remote side does not send the correct download result
* User programs: Called by editran at the end of the processes before/after output/reception and of exception.
* These programs will be provided by the user and will be called at the end of the presentation processes.
* The communications area passed to them contains all the information used by IGA (IGA and editran profiles).
* If you want to use any file, it must be included in the corresponding procedure

With Enter, the add will be performed. With PF3, you leave. The data values of a presentation application are passed to the presentation sessions of that entity, when they are created, as default values.

Modifying the profile of a presentation application is done in the same way as adding it, but the profile must already exist. The modified values are transferred to the matching fields in the presentation sessions of the same entity.

Query is the same as the previous functions.

When deleting an application profile, a screen identical to the one described appears. With Enter, the deletion is confirmed and with PF3 it is cancelled.


---

# 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-iseries-en/administracion-y-operacion/navigation-between-screens/main-menu/administrator/application-profile/add-application-profile.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.
