> 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-ims-en/operacion/primerospasos/control-de-actividad-de-onesait-editran/colas-de-ficheros.md). # File queues This screen is accessed with option 4 of the Activity Control menu or with option 2.4 of the main menu. ``` ------------------------------------------------------------------------------ | 21/06/26 ACTIVITY CONTROL EDITRAN | | 14:12:32 FILE QUEUES 5.3 | ------------------------------------------------------------------------------ | | | | | | | | | | | | | 1 FILE MANAGER | | | | 2 SESSION MANAGER | | | | | | | | | | OPTION ---> | | | | | | | | | | | ------------------------------------------------------------------------------ ``` The File Queues facility allows users to include application files so that they can be transmitted later automatically. When files are emitted they are deleted from the system. Files are incorporated into the system through an API invoked by the application. For a description of the API see the manual ([Application Program Interfaces](https://open-2v.gitbook.com/url/preview/site_GWwaR/ibm-editran-v5.3-comun-z-os/~/revisions/8s8vLdGheE7QlujbwpPo/interfaces-de-programas-de-aplicacion/colas-de-ficheros)). A periodic mechanism triggers the loading of the files in Editran. Through this screen we can manage the resources that control the process. With option 1 the application files are queried and deleted. With option 2 the sessions that use this facility are managed. ## **1-File manager** This screen is accessed with option 1 of the File Queues menu, option 2.4.1 of the main menu. ``` ------------------------------------------------------------------------------ | 21/06/26 FILE QUEUES EDITRAN | | 14:57:38 FILE MANAGER 5.3 | ------------------------------------------------------------------------------ | | | | | | | | | | | B DELETE | | | | C QUERY | | | | | | | | OPTION : C | | LOCAL CODE : | | REMOTE CODE : | | APPLICATION : | | | | | | | | | ------------------------------------------------------------------------------ ``` From here the names of application files pending to be emitted are managed. Enter the desired option and the codes for the local entity, remote entity, and the presentation application for a specific session and a generic one for all of them, and the following screen will appear: ``` 21/06/26 FILE QUEUES EDITRAN 14:59:42 FILE INQUIRY 5.3 S PRESENTATION SESSION FILE STAT - -------------------------- -------------------------------------------- ----- 000099980 000000010 TELECA KI.EIDA.F53 PENDING 000099980 000000010 TELECA KI.EIDA.F51 PENDING 000099980 000000010 TELECA KI.EIDA.F54 PENDING 000099980 000099930 CARGQF KI.EIDA.F05 EMITTING 000099980 000099930 CARGQF KI.EIDA.F06 EMITTING 000099980 000099930 CARGQF KI.EIDA.F07 PENDING 000099980 000099930 CARGQF KI.EIDA.F08 PENDING 000099980 000099930 CARGQF KI.EIDA.F09 PENDING 000099980 000099930 CARGQF KI.EIDA.F10 PENDING 000099980 000099930 CARGQF KI.EIDA.F11 PENDING 000099980 000099930 CARGQF KI.EIDA.F12 PENDING 000099980 000099930 CARGQF KI.EIDA.F13 PENDING 000099980 000099930 CARGQF KI.EIDA.F14 PENDING 000099980 000099930 CARGQF KI.EIDA.F15 PENDING 000099980 000099930 CARGQF KI.EIDA.F16 PENDING 000099980 000099930 CARGQF KI.EIDA.F17 PENDING 000099980 000099930 CARGQF KI.EIDA.F18 PENDING ``` Select the corresponding file with an ‘S’. The following screen will appear. With PF3 you exit the option, and with ENTER the removal is executed if you selected that option. ``` ------------------------------------------------------------------------------ | 21/06/26 FILE QUEUES EDITRAN | | 15:00:33 FILE INQUIRY 5.3 | ------------------------------------------------------------------------------ | PRESENTATION SESSION: 0 0009998 0 0 0000001 0 TELECA | | | | NAME : KI.EIDA.F53 | | | | RECORDING DATE : 05/09/2011 - 13:51:01 | | LOAD DATE : 16/06/2008 - 09:35:49 | | STATUS : PENDING LOAD | | LOAD FORMAT : RECORD | | ALPHABET : EBCDIC | | TRANSLATION : NO | | COMPRESSION : YES | | | | | | | | | | | | | | | | | ------------------------------------------------------------------------------ ``` * **PRESENTATION SESSION**: It is the presentation session that will carry out the transmission. * **NAME**: It is the name of the file to be emitted. * **RECORDING DATE**: It is the date and time when it was included in the queue system. * **LOAD DATE**: It is the date and time when it was loaded by the presentation module. It will appear blank if the file is pending load. * **STATUS**: The file will initially be PENDING LOAD. When it is loaded by the application it will change to EMITTING. When the transmission ends it will disappear from the queue. * **LOAD FORMAT**: Indicates the way it will be loaded, in RECORD format or in BINARY format. * **ALPHABET**: It is the alphabet in which the file data are stored, ASCII, EBCDIC or binary. * **TRANSLATION**: The file will be translated to ASCII, to EBCDIC or will not be translated during loading. * **COMPRESSION**: The file will or will not be compressed during loading. ## **2-Session manager** This screen is accessed with option 2 of the File Queues menu, option 2.4.2 of the main menu. ``` ------------------------------------------------------------------------------ | 21/06/26 FILE QUEUES EDITRAN | | 15:03:26 SESSION MANAGER 5.3 | ------------------------------------------------------------------------------ | | | | | A ADD | | | | B DELETE | | | | C QUERY | | | | M MODIFICATION | | | | | | OPTION : C | | LOCAL CODE : 0 0009998 0 | | REMOTE CODE : | | APPLICATION : | | | | | | | | | ------------------------------------------------------------------------------ ``` From here the sessions of the queue system are managed. These sessions control the way files will be loaded. The session will be registered manually through this screen or automatically when the first file of the application is included. To be able to register the queue session, there must be a presentation session in Editran with the same local code, remote code and application. The presentation session must also include in the application parameter “CARGA (N)ORM,(A)CUM,(Q)COL.:” the value 'Q' to indicate that the load type is via file queues (fourth session screen of option 1.4 of the menu). Deleting the session does not delete the associated files. Enter the desired option and the codes for the local, remote and presentation application entities for a specific session, and generic ones for all of them; the following screen will appear. ``` 21/06/26 FILE QUEUES EDITRAN 14:12:10 SESSION MODIFICATION 5.3 S PRESENTATION SESSION START TIME END TIME DEPTH LOAD/EMIT ACTIVE - -------------------------- -------- -------- ------- ---------- ------- 000099980 000000010 TEST 07:00 17:00 123456 EMITTING ACTIVE 000099980 000000010 TELECA 07:00 17:30 ALL EMITTING INACTIVE 000099980 000000010 000001 07:30 20:00 1 EMITTING ACTIVE 000099980 000000010 000003 08:00 07:00 1 EMITTING ACTIVE 000099980 000000010 000051 08:00 18:00 000002 EMITTING ACTIVE 000099980 000000010 000052 07:00 18:00 ALL EMITTING ACTIVE 000099980 000000010 000053 07:00 18:00 ALL EMITTING ACTIVE 000099980 000000010 000054 00:00 23:59 ALL EMITTING ACTIVE 000099980 000000010 000055 10:00 18:00 000321 LOADING ACTIVE 000099980 000000010 000056 07:00 07:00 ALL EMITTING ACTIVE 000099980 000000010 000057 10:00 10:00 ALL EMITTING ACTIVE 000099980 000000010 000058 00:00 00:00 ALL EMITTING ACTIVE 000099980 000000010 000059 09:00 09:00 ALL EMITTING ACTIVE 000099980 000000010 000060 09:00 18:00 1 EMITTING ACTIVE 000099980 000000010 455051 1 LOADING INACTIVE 000099980 000000010 465244 ALL LOADING INACTIVE 000099980 000000010 465398 ALL LOADING INACTIVE ``` Select the corresponding session with an ‘S’. The following screen will appear. With PF3 it is canceled, and with ENTER the desired option is executed. ``` ------------------------------------------------------------------------------ | 21/06/26 FILE QUEUES EDITRAN | | 14:13:18 SESSION MODIFICATION 5.3 | ------------------------------------------------------------------------------ | PRESENTATION SESSION: 0 0009998 0 - 0 0000001 0 - TEST | | | | START TIME : 07 : 00 (hh:mm) | | END TIME : 17 : 00 (hh:mm) | | DEPTH : V (1/Several/All) NUMBER OF FILES: 123456 | | LOAD OR EMIT: E (L/E) | | ACTIVE SESSION : A (A/I) | | | | | | | | | | | | | | | | | | | | | | | | | ------------------------------------------------------------------------------ ``` * **PRESENTATION SESSION**: It is the presentation session that will carry out the transmission. * **START TIME, END TIME**: A schedule can be specified for the automatic loading of files. The periodic trigger mechanism will only start loading files within this interval. This does not prevent the loading from being started outside this schedule at the request of the presentation module operator, the application, or the remote entity. * **DEPTH**: Indicates whether all files found for the session, a specific number, or only 1, will be processed. * **NUMBER OF FILES**: Indicates the number of files that will be processed if “V” was indicated in “*Depth*”. * **LOAD OR EMIT**: The file will be loaded by the presentation module, to be transmitted later, or loaded and emitted. * **ACTIVE SESSION (INACTIVE)**: Allows file loading to be stopped temporarily. With the session inactive, the periodic trigger mechanism is disabled and the presentation module's loading process is prevented. With the session inactive, the application is allowed to include files in the queue. --- # 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-ims-en/operacion/primerospasos/control-de-actividad-de-onesait-editran/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.