> 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/set-text-1.md).

# Set Text

This is pre-built Action located under the **Mainframe List Element**. The functionality of this action in Avo Assure is used to set a text value at a specified row and column location on the mainframe emulator screen.

### Syntax

**Input Value:** `<Row Number>;<Column Number>;<input text>`

{% hint style="warning" %}
**Note:** *Row number: It refers to X coordinate value from emulator screen.*

*Column number: It refers to Y coordinate value from emulator screen.*

*Input text: The user gives text to set at specified position.*
{% endhint %}

| Argument                                 | Description                                                                      |
| ---------------------------------------- | -------------------------------------------------------------------------------- |
| <p>\<Row Number></p><p>(Required)</p>    | Specify the X-coordinate on the emulator screen where the text should be entered |
| <p>\<Column Number></p><p>(Required)</p> | Specify the Y-coordinate on the emulator screen where the text should be entered |
| <p>\<input text></p><p>(Required)</p>    | Specify the text to be set at the specified screen location                      |

**Output Value:**

| Argument                                                     | Description                                                     |
| ------------------------------------------------------------ | --------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable> (Optional) | This dynamic variable holds the result as **True** or **False** |

{% hint style="warning" %}
***Note:** Supported Emulators are Bluezone, EXTRA, Rumba, PCOMM, and HOD.*
{% endhint %}

**Example**

**Enters text at the specified row and column on the emulator screen**

The **Set Text** action takes the value from the Input Value column (e.g., **24;017;CICS1**) and sets the provided input text at the given position on the emulator screen. Here, **24** refers to the row number (X-coordinate), **017** refers to the column number (Y-coordinate), and **CICS1** is the text to be entered.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FbfZ9Up2c77rIktfonmil%2Fimage.png?alt=media&amp;token=d927fb31-09ee-481c-b6d3-fb7df909a8eb" 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/set-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.