> 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/interfaces-de-programas-de-aplicacion/colas-de-ficheros.md). # File queues To view the graphical interface, see the manual: [Administration and operation](/documentacion-editran/copy-of-privado-editran-v5.3-cics/operacion.md) for CICS or [Administration and operation ](/documentacion-editran/ibm-editran-v5.3-ims/operacion.md)for IMS. The file queue functionality consists of applications notifying which files they want to send or load, and they do not concern themselves with whether the application can do so at that moment or not. There is a file (ZTBPGFQF) whose contents are one profile for each involved presentation session and the files pending or in progress of transmission. To work with this option, it is necessary: * Define in the presentation session the parameter LOAD-TYPE = ‘Q’ (option 1.4 of the main menu) * Define the presentation session in the file queue profile (option 2.4.2). If the session is not defined, it is created automatically when the API is called from the applications (without schedule, load+send, depth 1 and active). * Call the API from the applications, indicating the function (save-delete), the presentation session, the name of the file to load-send, and its characteristics (format, language, translation, and compression). The API can also be called with a JCL. The application saves in a storage queue - file ZTBGFQF in CICS, and DB ZTBGDQFD/I in IMS-: * The profile of the presentations, with their parameters: start time-end time, whether to load or load and send, whether to keep it active or stop it, whether to send 1 single file or all available ones, or a specified number, etc. * Each of the files indicated by the API from the applications and the state it is in (pending processing = pending, in process = sending). The operating scheme is as follows: * There is a manager that starts every xx minutes (according to the local Editran environment parameter), which checks whether there are pending files (to load or send). If so, and the session is in a compatible state and meets the time limits and is active and in the presentation session has load-type='Q', a pre-send is launched (the one indicated in the presentation session, with the JCL cards of the first transmission of the presentation in CICS, and in the presentation session itself in IMS). * When the pre-send is launched, if the presentation session has queue-based load mode in its profile, ‘Q’: * It checks that the Editran/G status is compatible for loading (not loaded, finished, initialized). If not, it ends the process. * It checks that there are no files in the storage queue in the “sending” state. If there are, it ends the process. If this situation comes from an exception, a send-state modification procedure must be launched. * It puts the file(s) to be loaded into the “sending” state * It loads them into the buffer * It requests Editran/P to load and/or send according to the file queue profile. * When the post-send is launched, if the presentation session has load-type = ‘Q’ in its profile, it deletes the files in the “sending” state from the storage queue. * When the send-state modification is launched, if the presentation session has load-type = ‘Q’ in its profile, it changes the files that are in the “sending” state to the “pending” state, provided that it does not duplicate the file name with another saved as “pending”; in that case, it deletes the one that was in the “sending” state. --- # 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/interfaces-de-programas-de-aplicacion/colas-de-ficheros.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.