> 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.md).

# Login to Mainframe

This is pre-built Action located under the Mainframe List Element. It instructs the Avo Assure Client to login to the Mainframe Region using userID and password.

### Syntax

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

{% hint style="info" %}
***Note:** In mainframe systems, a **Region** refers to a logical partition or environment, like a CICS region, that manages specific resources or transaction workloads.*\
\&#xNAN;***UserID** and **password** are provided by the administration.*
{% endhint %}

**Output:** `<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)`

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FjNC8ajmpXSMGF2hv69VM%2Fimage.png?alt=media&amp;token=6fbdb606-3a16-4f6d-8ff2-34fd0617a626" alt=""><figcaption></figcaption></figure>

### Usecase/Example

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FoFhH1VylCREioTn5Vpag%2Fimage.png?alt=media&amp;token=22f52c5f-af07-48a7-b0cd-93fad0cde768" alt=""><figcaption></figcaption></figure>

### Scenario: Automating Mainframe Login with Credentials

Consider a scenario where automating a mainframe application involves logging in to the system. With the **Log in to mainframe** action, logging in with credentials becomes a straightforward process.

### **Input**

CICS1;MATESG;SKL259

### **Expected Result**

This Action needs to log in with Credential to the mainframe application.

### **Output**

The **Log in to mainframe** action performed successfully.


---

# 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.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.
