> 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/interfaz-generica-de-aplicacion/generalidades-sobre-onesait-editran-e-interfaces/comunicacion-entre-onesait-editran-e-interfaces.md).

# Communication between Onesait Editran and interfaces

## From an interface to Onesait Editran

Generally speaking, it could be said that this is the sending of messages from batch programs to the CICS where Editran is running.

The application installation includes the JCL, ZTBPJBAT for CICS, which can be used to send A5P messages of types 1 to 4, 8 and A to a specific transmission session, the meaning of which is as follows:

* Type 1: Transmission load order and start of transmission.
* Type 2: Reception initialization order and start of reception.
* Type 3: Post-transmission processing order.
* Type 4: Reception unload order.
* Type 8: Transmission load order.
* Type A: Reception initialization order.

A5P messages (P = 1 to 4) can also be routed, via distribution lists, to several transmission sessions.

These orders cause Editran/P to launch the pre/post transmission/reception processes, from which Editran/P will be informed of their successful or unsuccessful completion by means of the AnR(+) or AnR(−) messages, where n is 1 to 4, 8 and A and corresponding to the A5P types seen above. Specifically:

* A1R(+): Orders Editran/P to start transmission.
* A8R: Notifies Editran/P of the transmission load.
* A2R(+): Orders Editran/P to start reception.
* AAR: Notifies Editran/P of reception initialization.

Since the release of Editran/G, Editran/P is allowed to receive the following messages from the interfaces:

* EDP: Interrupt transmission.
* EDR: Interrupt reception.

## From Onesait Editran to an interface <a href="#toc149819061" id="toc149819061"></a>

In the cases that concern us, it is not really a matter of sending messages from Editran to another region where a process is running, but rather of launching jobs invoking pre/post transmission/reception or exception procedures, with certain values passed as parameters.

These procedures will be launched only if they are specified in the profile of the corresponding transmission session. In this case, an A5P always determines that the procedure corresponding to its type be launched, as we saw earlier. However, the procedures are also launched in other circumstances:

* The pre-transmission procedure is launched when a transmission request is received from the local operator or from remote Editran and the transmission buffer is:
  * Empty.
  * Not fully transmitted, but with all records acknowledged by the receiver and a rejection of the transmission is received from it.
  * Marked as "Interrupted"
* The pre-reception procedure is launched when the reception buffer is in situations equivalent to those just seen for the transmission buffer.
* The post-transmission procedure is launched when it ends.
* The post-reception procedure is launched when it ends.

Editran will also launch the pre-transmission or pre-reception procedures when the corresponding buffer is closed to CICS. However, they will not be launched if it is marked as "Unavailable", in which case it is understood that there may be a previous procedure running.

The Editran transmission module will be able to launch a transmission exception or interruption procedure, A7I with a reference code, depending on which the Editran presentation module will or will not change the status of the transmission session to "Interrupted".


---

# 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/interfaz-generica-de-aplicacion/generalidades-sobre-onesait-editran-e-interfaces/comunicacion-entre-onesait-editran-e-interfaces.md?ask=<question>&goal=<endgoal>
```

`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.