> 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/anexo-b.-procedimiento-de-excepcion.md).

# Appendix B. Exception procedure

Executed by the transmission module with an A7I message (when an incident occurs that prevents a complete transmission or reception). It must do the following:

* Notify the Installation Operator of the Incident with the corresponding comment.
* Depending on the Reference Code of the A7I message, the transmission or reception of the Session involved can be retried. There is a subset of Reference Codes for which the transmission should not be retried unless the error is repaired first. For the other Codes, retrying is possible, although it must be done a finite number of times, since it is always possible that due to an unexpected error a loop situation is reached. The non-retryable Codes are:

> - E010 and R010.
> - E020 if CALLING-END="X" or "R" of the Session involved.
> - R020 if CALLING-END="X" or "R" of the Session involved.
> - E022 and R022.
> - E023.
> - E024.
> - E100 and R100.
> - E110 and R110.
> - E140 and R140.
> - R144.
> - E200 and R200.
> - E230 and R230.

The Codes for which it is possible to retry a finite number of times are:

* E020 and R20 if CALLING-END="L" of the Session involved.
* E022 and R022 if CALLING-END="L" of the Session involved.
* E025 and R025.
* E030 and R030.
* E040 and R040.
* E060 and R060.
* E070.
* E090.
* E120 and R120.
* E130 and R130.
* E150 and R150.
* E210 and R210.
* E220 and R220.
* E230 and R230.

The transmission module sets BUFFER-STATUS to value "I" when it launches an A7I message (if an Exception Procedure exists) and the Reference Code of the A7I message is:

E010, R010, E021, R021, E023, E024, E100, R100, E110, R110, E200, R200, E210 and R210.

Therefore, when this circumstance occurs, it is convenient for the User Procedures or Application Interface to act accordingly if they want Editran to transmit again (set BUFFER-STATUS to "C").

All these codes are reflected in the following table:

## Table of A7I incident codes <a href="#toc21003036" id="toc21003036"></a>

A7I messages include the involved SESSION and a Reference Code for the Incident that caused the end of a transmission/reception. These Codes are shown below with their corresponding explanatory comment:

* E010

> Comment: Transmission ends due to an operator release request (E11).

* R010

> Comment: Reception ends due to an operator release request (E11).

* E020

> Comment: Transmission ends due to Incorrect Remote Receiver Buffer File. Previous is triggered. (SDR 3/D1). Transmission ends due to Local Transmission DB not being ready. Previous is not triggered.

* R020

> Comment: Reception ends due to Incorrect Remote Sender Buffer File. Previous is triggered. (SDP 3/D1).

* E021

> Comment: Transmission ends due to Incorrect Remote Receiver Buffer File. No Previous exists. (SDR 3/D2).

* R021

> Comment: Reception ends due to Incorrect Remote Sender Buffer File. No Previous exists. (SDP 3/D2).

* E022

> Comment: Transmission ends due to Incorrect Remote Receiver Buffer File. Previous in possible Execution. (SDR 3/D3).

* R022

> Comment: Reception ends due to Incorrect Remote Sender Buffer File. Previous in possible Execution. (SDP 3/D3).

* E024

> Comment: Transmission ends due to Incorrect Remote Receiver Buffer File. Total Number of Transmission Records less than Reception. (SDR 3/D5).

* R027

> Comment: Reception ends due to Incorrect Remote Sender Buffer File. Expected Total Number of Records is less than those received. (SDR 5/D9).

* E030

> Comment: Transmission ends due to a remote release request
>
> (SDR#3/SOL-LIB/SAB).

* R030

> Comment: Reception ends due to a remote release request
>
> (SDP#3/SOL-LIB/SAB).

* E040

> Comment: Transmission ends due to Excess Retries in Transmission Start (SCP).

* R040

> Comment: Reception ends due to Excess Retries in Reception Start (ECP).

* R060

> Comment: Reception ends due to Protocol Error in Synchronism Request (SBP).

* E070

> Comment: Transmission ends due to Excess Retries in Synchronism (SBP).

* E090

> Comment: Transmission ends due to Excess Retries in Transmission End (SEP).

* E100

> Comment: Transmission ends due to Session Association Error due to Incompatible Parameters (SAP/SAR).

* R100

> Comment: Reception ends due to Session Association Error due to Incompatible Parameters (SAP/SAR).

* E110

> Comment: Transmission ends due to Session Association Error due to Cryptography (SAP/SAR).

* R110

> Comment: Reception ends due to Session Association Error due to Cryptography (SAP/SAR).

* E120

> Comment: Transmission ends due to Excess Retries in Session Association (SAP).

* R120

> Comment: Reception ends due to Excess Retries in Session Association (SAP).

* E130

> Comment: Transmission ends due to Excess Retries in Connection (E00).

* R130

> Comment: Reception ends due to Excess Retries in Connection (E00).

* E140

> Comment: Impossibility of transmission due to Session Profiles (ECP).

* R140

> Comment: Impossibility of reception due to Session Profiles (ECR/SCP).

* E150

> Comment: Transmission impossible due to Unavailable Transmission Buffer File (ECP).

* R150

> Comment: Reception impossible due to Unavailable Reception Buffer File (ECR/SCP).

* R155

> Comment: Reception impossible due to Reception Buffer File with No Space.

* E200

> Comment: Transmission impossible due to Pre-Transmission Procedure Error (A1R).

* R200

> Comment: Reception impossible due to Pre-Reception Procedure Error (A2R).

* E210

> Comment: Transmission impossible due to Line Error.

* R210

> Comment: Reception impossible due to Line Error.

* E220

> Comment: Transmission impossible due to Compression and Cryptography Error.

* R220

> Comment: Reception impossible due to Compression and Cryptography Line Error.

* E230

> Comment: Transmission impossible outside schedule.

* R230

> Comment: Reception impossible outside schedule.


---

# 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/anexo-b.-procedimiento-de-excepcion.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.