# Launch mainframe

This is pre-built Action located under the Mainframe List Element Name. It instructs the Avo Assure Client to launch the mainframe by giving emulator path and emulator type in the Input Value.

{% hint style="info" %}
**Note:** When automating Mainframe this is first step that needs to be added to execute testcase.
{% endhint %}

### **Syntax**

**Input:** `<EmulatorPath>;<EmulatorType>`&#x20;

* **Emulator Path:** This Argument will accepts the Path of the Emulator (BlueZone, EXTRA, Rumba, PCOM, HOD).
* **Emulator Type:** This Argument accepts the type, it can be name of the Emulator for which this Action is working.

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

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F0xEpIpcCxWsisFwVGf5T%2Fimage.png?alt=media&#x26;token=8c0fe342-da62-41ae-904c-da773a637a78" 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%2FsCQ1fhjk9QHdhRrlr1Dx%2Fimage.png?alt=media&#x26;token=eee93b51-7c85-4dfe-aee0-bd3c32fad9de" alt=""><figcaption></figcaption></figure>

### **Scenario**

Consider a scenario where Mainframe Application needs to be automated. For this, the first and most crucial step is to launch the mainframe emulator and the **Launch mainframe** Action is executed with the correct emulator path and type.

&#x20;This step is essential as it opens the mainframe environment, which subsequent automation steps will interact with.

### **Input**

C:\Users\Desktop\new 2.zmd;BlueZone

### **Expected Result**

This Action needs to Launch the Mainframe application which Emulator path and the type is given.

### **Output**

The Launch Application Action Launches the BlueZone Emulator