> 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/sepa/functional-description/input-output-data-for-the-converters.md).
# Input/output data for the converters
* Output data
In all cases, a list of output files generated by the P1PRESEPA process will be created.
This list is generated for each load and is not deleted; a new one is added.
It is not deleted, so that it can be used to check the files that are going to be sent.
This list of output files is the one in step A1P
Therefore, it will be included as input data to the converter; the converter generates a list of files, which will be the one that reaches A1P.
* Input data
To call the converters, the following are used:
#### Data passed to the converter via PARM
A PERFSEPA profile file has been created, which contains the necessary data to pass to the converters
It is accessed with the EDISEPA command
On one hand, there is the Local Environment, which is defined once and contains:
* Source. source code of the entity.
* SEPA server IP address
* Port
* Timeout
To define sessions that will be used to obtain the reception download parameters.
* Source. source code of the entity.
* Destination. destination code
* Application. Code of some application/example program.
Conversion table: If no value is provided, it assumes the one in :Conf/Configuracion.proporties in the #ALFABETO section
* For the EMISSION case,
We read the environment profiles to obtain the Java server address; this is done once, after the previous P1PRESEPA process passes the session parameters and the name of the file list. This process calls PBIGA110SP, which is the equivalent process to PBIGA110, but specific to SEPA.
* For the RECEPTION case,
The P4POSEPA process will be set as the post-reception program in the editran/P transmission session.
The P4POSSEPA process passes “SEPA” to the post-reception process, in addition to the session parameters, with the C4GENERI program being the one that reads the received files and the names of the adapted files from the SEPA profiles in order to pass them to the CLI4SEPA converter.
These names must match the Physical File Name of the Reception Application File that is set in the editran/g profile
If transform = F, it matches the name of the received file
If transform = X, it matches the name of the adapted file.
---
# 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/sepa/functional-description/input-output-data-for-the-converters.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)