TerminalSession

Limitations

Currently, only single session is supported, so multiple sessions with the connected terminal are not possible. By default, the session is set as “A.”

Properties

CONNECTIONS

MISC

DisplayName: Displays the name of the activity. The activity name can be customized, which aids in troubleshooting.

SkipOnError: Specify the “Boolean” value as “True” or “False.”
True: Continue executing the workflow regardless of any errors thrown.
False: Halt the workflow if it encounters any errors.
None: If the option is left blank, the activity will, by default, behave as if “False” were chosen.

Version: It indicates the version of the feature being used.

OUTPUT

Result: It provides the ability to view the execution status of the activity. It returns values in “Boolean.”

True: Indicates that the activity has been executed successfully without any errors.
False: Indicates that the activity has been unsuccessful due to an unexpected error being thrown.

SessionStatus: It provides the result of the status of the session that has been connected. It returns values in “Boolean”.

True: Indicates that the session has been executed successfully without any errors.
False: Indicates that the session has been unsuccessful due to an unexpected error being thrown.

Configure Session

The Configure Connection window offers various configuration options that differ based on the selected provider for connecting to the terminal environment. 

Provider: This option allows you to select the connection type to be configured. It offers two types of connections:

1. IBMEHLLAPI
2. Direct Connection

IBMEHLLAPI Connection 

This connection type uses IBM’s HLLAPI to establish a session with a mainframe emulator, allowing the terminal activities to communicate with the IBM system and perform tasks like sending commands or retrieving data. This connection type supports any 3rd party terminal emulator software that implements the EHLL API

Utilize this provider connection when there is any 3rd party terminal emulator software that supports the EHLL API software. 

Emulator Exe path: This indicates to provide the path of the terminal exe file. It accepts only “.ws” extension file type. Click on the “Browse” option and manually choose the path where it has been situated. You can also provide the file path in “String” datatype. 

Session: This parameter indicates the session where the bot needs to perform the action. Currently this field will be disabled, and the default value will be provided as “A”.
Note: “A” represents the first session that has been launched against the connected terminal system.

Note: The terminal emulation software needs to be started and connected before attempting to automate with it. Utilize “Desktop Automation” activities to launch and configure the connection. 

Direct Connection