> 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-cics-en/utilities-and-codes/general-information-about-onesait-editran-and-interfaces/communication-between-editran-and-interfaces.md).

# Communication between editran and interfaces

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

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

In the editran installation, the JCL ZTBPJBAT and the CLIST ZTBG are supplied, with which A5Ps of types 1 to 4 can be sent to a given transmission session, whose meaning is as follows:

* Type 1: Send load order and send start.
* Type 2: Receive initialization order and receive start.
* Type 3: Post-send process order.
* Type 4: Receive unload order.

These orders cause editran to launch the pre/post send/receive processes, from which editran will be informed of their successful or unsuccessful completion by means of the messages AnR (+) or AnR (‑), where n is from 1 to 4 and corresponds to the A5P types seen above. Specifically:

* A1R (+): Instructs editran to begin sending.
* A2R (+): Instructs editran to begin receiving.
* EDP: Interrupt sending.
* EDR: Interrupt receiving.

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

In the cases that interest us, it cannot really be said that messages are being sent from editran to another region where a process is running, but rather that Jobs are launched invoking pre/post send/receive procedures with the contribution of 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 causes the procedure corresponding to its type to be launched, as we saw earlier. However, the procedures are also launched in other circumstances:

* The pre-send procedure is launched when a send request is received from the local operator or from remote editran and the send buffer is:
  * Empty.
  * Not fully sent, but with all records confirmed by the receiver and a rejection of the send is received from it.
* The pre-receive procedure is launched when the receive buffer is in situations equivalent to those just seen for the send buffer.
* The post-send procedure is launched when it ends.
* The post-receive procedure is launched when it ends.
* Editran will also launch the pre-send or pre-receive procedures when the corresponding buffer is closed.
* Editran launches an exception procedure when an incident or an interruption of the transmission occurs.

<br>


---

# 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-cics-en/utilities-and-codes/general-information-about-onesait-editran-and-interfaces/communication-between-editran-and-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.