> 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/login-to-mainframe-1.md).

# Login to Mainframe

This is a pre-built action located under the **Mainframe List Element**. The functionality of this action in Avo Assure is used to log in to the Mainframe Region using a provided Region, UserID, and Password.

### Syntax

**Input Value:** `<Region>;<UserID>;<Password>`

| Argument                            | Description                                                                                      |
| ----------------------------------- | ------------------------------------------------------------------------------------------------ |
| <p>\<Region></p><p>(Required)</p>   | Specify the logical partition or environment like a CICS region that manages specific workloads. |
| <p>\<UserID></p><p>(Required)</p>   | Specify the user ID assigned for mainframe login                                                 |
| <p>\<Password></p><p>(Required)</p> | Specify the password corresponding to the user ID.                                               |

**Output Value:**

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

**Example**

**Performs login operation on the mainframe emulator using provided credentials**

The **Login to Mainframe** action takes the value from the Input Value column (e.g., **CICS1;MATESG;SKL435**) and logs in to the specified region of the mainframe using the provided User ID and Password. Here, **CICS1** is the region name, **MATESG** is the user ID, and **SLK435** is the password.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F4DWo54nDu4soZUAmoXiC%2Fimage.png?alt=media&amp;token=02c77a7c-21b0-47ee-a250-9874de01b5ab" 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/login-to-mainframe-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.