> 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/gestor-de-transmisiones/administrator/transmission-scheduler.md).
# Transmission scheduler
Planning cannot be done with EDIgt started.
With Administrator option 2, the screen appears that allows sessions to be managed.
The identifier parameters of the editran Session (Local Code, Remote Code and Application) must be specified, as well as the desired option (Create, Query, Delete or Modify). The meaning of the fields is as follows:
* LOCAL CODE: Identification number of the editran User Entity. With this code it will be recognized by all Entities interconnected with the application. (If left blank, it takes the general local environment)
* REMOTE CODE: Identification of the remote ediItran installation (for example, the entity's NIF number).
* APPLICATION: ediItran application code for the Session.
* CAR/EMI/INIC/REC: Request to perform, load and issue or initialize and receive.
* If a generic option is specified, all registered sessions will appear
Select with “S” the one you want to query and the parameters of that session appear.
Where we have the scheduled date data:
* Day: Table of the days of the week (in 3 characters) MON TUE WED THU FRI SAT SUN in which the scheduled job will be executed.
* Week: Table of the weeks of the month, 1 2 3 4 5, in which the scheduled job will be executed.
* Month: Table of the months of the year, 1 2 3 4 5 6 7 8 9 10 11 12, in which the scheduled job will be executed.
* Time (HHMM): The time at which the scheduled job will begin to execute.
* Exclude Days (ddmm): Table of 50 elements with the dates of days that, although scheduled, do not require execution. For example, regional holidays, etc. In this case, January 1, December 25 and May 1.
* Include Days (ddmm): Table of 50 elements with the dates of days that, although not scheduled, require execution. In this case April 3 and July 11.
---
# 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/gestor-de-transmisiones/administrator/transmission-scheduler.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)