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

# Verify Text Exists

This is pre-built Action located under the **Mainframe List Element**. The functionality of this action in Avo Assure is used to verify whether a specific text value, provided in input, exists on the mainframe emulator screen, and save the result in dynamic variable.

### **Syntax**

**Input Value:** `<input value>`

| Argument                               | Description                                                    |
| -------------------------------------- | -------------------------------------------------------------- |
| <p>\<input value></p><p>(Required)</p> | Specify the text string to be verified on the mainframe screen |

**Output Value:**

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

**Example**

**Performs verification to check if the specified text exists on the emulator screen**

The **Verify Text Exists** action takes the value from the Input Value column (e.g., **CICS1**) and verifies whether the given text is present on the mainframe screen. The result of the verification is stored in the **{Verify}** variable as **True** ( if the text is found successfully ) or **False** ( if the text is not found)

<figure><img src="/files/zdTFCSDIkk9wdCfhveXq" 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 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.avoautomation.com/avo-assure/actions/mainframe/verify-text-exists-1.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.