> 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/launch-mainframe-1.md). # Launch mainframe This is pre-built Action located under the **Mainframe List Element**. The functionality of this action in Avo Assure is to launch a Mainframe emulator using the provided emulator path and type. {% hint style="info" %} **Note:** * When automating Mainframe this is first step that needs to be added to execute testcase. * Avo Assure 3270 uses **Model 4** by default. If the Mainframe session is configured with a different terminal model or the model number is manually changed in the emulator, provide the corresponding model number in the **Launch Mainframe** configuration. * Provide the **emulator type/path** in the **Launch Mainframe** configuration along with the **model number**. {% endhint %} ### **Syntax** **Input Value:** `;` | Argument | Description | | --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | |

\

(Required)

| Specify the Full file path of the Mainframe emulator | |

\

(Required)

|

Specify the name of the emulator being launched.

Supported Emulators: (BlueZone, EXTRA, Rumba, PCOM, HOD)

| **Output Value:** | Argument | Description | | ------------------------------------------------------------ | --------------------------------------------------------------- | | \(Optional);\ (Optional) | This dynamic variable holds the result as **True** or **False** | **Example** **Launches the mainframe emulator using the specified path and emulator type** The **Launch Mainframe** action takes the value from the Input Value column (e.g., **C:\Users\rakshanda.ambershett\OneDrive - SLK Software Pvt Ltd\Desktop\MainFrame.zmd;Bluezone**) and launches the mainframe emulator application with the provided path and type.
--- # 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/launch-mainframe-1.md?ask=&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.