> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/mainframe/get-text-1.md).

# Get text

This is pre-built Action located under the **Mainframe List Element**. The functionality of this action in Avo Assure is used to retrieve a specific text string from the mainframe emulator screen, using coordinates and a length, and store the retrieved value in an dynamic variable.

### **Syntax**

**Input Value:** `<Row Number>;<Column Number>;<length>`

| Argument                                 | Description                                                              |
| ---------------------------------------- | ------------------------------------------------------------------------ |
| <p>\<Row Number></p><p>(Required)</p>    | Specify the X-coordinate from which to start reading the text            |
| <p>\<Column Number></p><p>(Required)</p> | Specify the Y-coordinate from which to start reading the text            |
| <p>\<input text></p><p>(Required)</p>    | Specify the number of characters to retrieve from the specified position |

**Output Value:**

| Argument                                    | Description                                                     |
| ------------------------------------------- | --------------------------------------------------------------- |
| <p>\<Dynamic Variable></p><p>(Required)</p> | This dynamic variable holds the retrieved text                  |
| <p>\<Dynamic Variable></p><p>(Optional)</p> | This dynamic variable holds the result as **True** or **False** |

**Example**

**Fetches text from the specified coordinates on the emulator screen**

The **Get Text** action takes the value from the Input Value column (e.g., **24;017;5**) and retrieves the text starting from the given position on the emulator screen. Here, **24** is the row number (X-coordinate), **017** is the column number (Y-coordinate), and **5** is the number of characters to fetch from that position. The result of the fetch operation is stored in the **{Get Text}** variable as (**Welco**)

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FtNvp1KFsoCuve4UTH2Ay%2Fimage.png?alt=media&amp;token=1895260f-f9b1-4691-8f53-5e9ccc93230f" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/actions/mainframe/get-text-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.