Defining a HATS rich client Application Command Action detail

If you want to define an action that starts a specific HATS rich client application, the format of the command is determined by whether your HATS rich client application is designed to support single sign-on or not.

Complete one of the following steps:
If your application does not support automated sign-on, the format of the command is just the URL of the HATS application. For example: HATSRCP=appname where appname is the name of the HATS rich client application. Or, if the application has parameters, the command might be similar to the following example: HATSPCP=appname hatsgv_userid hatsgv_password
If your application does support automated sign-on, specify the name of the variables for the user ID and password that are to be added to the HATS command. For HATS, the global variables are specified in the following format on the HATS command: HATSPCP=appname hatsgv_userid hatsgv_password In addition to the user ID and password parameters, you can also specify additional parameters to be passed to HATS. In this example, the HATS Web application is invoked and the user ID and password are passed. Additionally, three other parameters (hatsgv_var1, hatsgv_var2, and hatsgv_var3) are passed, along with their corresponding values. More than three parameters can be passed.
```
HATSRCP=HCmvs211Parms hatsgv_userid hatsgv_password hatsgv_var1=value1 hatsgv_var2=value2 hatsgv_var3=value3
```
If your application does support automated signon, Developer for z/OS® substitutes your user ID and password, if you specify the name of the variables for the user ID and password that are to be added to the HATS command. For HATS, the global variables are specified in the following format on the HATS command:
```
http://hostname/appname/?parameter1=one hatsgv_userid hatsgv_password 
```
There must be a space between the HATSRCP=appname and hatsgv_userid and between hatsgv_userid and hatsgv_password. The name of the global variables for user ID and password are not important (except that HATS does require the hatsgv_ prefix to know that a specified parameter is a global variable). What is important is that hastgv_userid is interpreted as the user ID and hatsgv_password will be interpreted as the password.
In addition to the user ID and password parameters, you can also specify additional parameters to be passed to HATS. In this example, the HATS web application is started and the user ID and password are passed. Additionally, three other parameters (hatsgv_var1, hatsgv_var2, and hatsgv_var3) are passed, along with their corresponding values. More than three parameters can be passed.
```
http://hostURL/myapp?tabs1=structures hatsgv_userid hatsgv_password var1=value1 var2=value2 var3=value3
```
The following URL results from this example:
```
http://hostURL/myapp?tabs1=structures&hatsgv_userid=userid&hatsgv_password=password&var1=value1&var2=value2&var3=value3
```
For the web interface, the URL specified in the command can be with or without parameters in the URL itself. Host Connection Emulator correctly detects the presence or absence of parameters and adjusts accordingly. For example, without any parameters the following URL is generated:
```
http://hostURL/myapp hatsgv_userid hatsgv_password var1=value1 var2=value2 var3=value3
```
With parameters, the following URL is generated:
```
http://hostURL/myapp?tabs1=structures&oneparm=good hatsgv_userid hatsgv_password var1=value1 var2=value2 var3=value3
```