Can run on: Windows

The Terminal Automation plugin depends on Windows-only host access components, so these steps require an agent running on Windows.

Terminal Automation: Start

Terminal Automation: Start step establishes connection to a terminal. This is an input step, use this as the first step in the workflow.

Example:

With Host set to 10.60.0.32, the following three properties open a 5250 session on port 23:

Property = port, Value = 23

Property = sessionType, Value = 2

Property = sessionName, Value = A

sessionType 2 means 5250. If you leave sessionType out, 3270 is used.

Field Name	Description
Step Name	Name of the step. This name must be unique in a single workflow.
Connection:
Host	Provide the host name or IP address of the terminal host itself, for example the IBM i / AS400 server. This field is mandatory.

Input tab:

Field Name	Description
Input Fields:
Property	Provide the property names for the session. This is a string value. If you type a property name but leave its Value blank, the property is skipped without any warning. Check for empty Value cells if a session does not behave as expected. Notes: In case you do not explicitly specify 'sessionType' property, it is set to terminal TN3270 by default. Reference URL to get property names: https://www.ibm.com/support/knowledgecenter/SSS9FA_13.0.0/com.ibm.hod.doc/doc/beans/com/ibm/eNetwork/beans/HOD/Session.html
value	Provide an appropriate value for the property. Note: Reference Link to get Property values : https://www.ibm.com/support/knowledgecenter/cs/SSS9FA_12.0.0/com.ibm.hod.doc/doc/hacl/com/ibm/eNetwork/ECL/ECLSession.html#SESSION_TYPE_5250_STR

For example, if you choose property


sessionType	enum*	ECLSession.SESSION_TYPE_3270_STR

SESSION_TYPE- Type of session to establish the value can be one of the following: