> 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/editran-sepa/descripcion-de-la-funcionalidad/casos-de-uso-de-los-conversores.md). # Use cases for the converters Basically, there are 3 use cases for calling the converters: * In pre-issue procedures (A1P). In this case, it is proposed to use the converter in a step prior to A1P, so that with a single new procedure (ZTBGP1X), a solution can be provided for all submission sessions that require XML files to be issued. In addition, this makes the use of this converter transparent to the user with respect to its previous loading (flat-file) operation * Post-receipt procedures (A4P). In this case, it is proposed to use the converter in a step after the A4P step and the LFE step, so that with a single new procedure (ZTBGP4X), a solution can be provided for all submission sessions that require XML files to be received and want to convert them to FLAT FILES. In addition, this makes the use of this converter transparent to the user with respect to its previous download (flat-file) operation * JCL. In this case, a specific JCL, ZTBGJXML, can be used to convert any file from the entity to XML or to a flat file. In short, the converters from flat file to XML and from XML to flat file have been developed: * So that they can be used for files transmitted by the application. In this case, the most common approach will be to use 2 new standard product procedures: one before issue (ZTBGP1X) and one after receipt (ZTBGP4X). * So that they can be used to process, in this way, any other file in the installation. In this case, the most common approach will be to use a supplied JCL, ZTBGJXML --- # 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/editran-sepa/descripcion-de-la-funcionalidad/casos-de-uso-de-los-conversores.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.