Fujitsu_HostTalk

Fujitsu_HostTalk_Emulator

Pega Robot Studio allows you to control an ICL emulator, such as the Fujitsu HostTalk emulator. This project item is displayed as one of the Text adapters. To use this emulator, be sure to set these properties:

Property	Description
DllName	Enter the path to the iclhll32.dll file.
EmulatorType	Specifies the type of emulator. The default is VT7561. Change this to VT320 to test the VT320 emulator.
Path	Enter the path to the executable you want to use to launch the emulator. Note that the VT320 emulator has a different path than the VT7561 emulator.
SessionPath	Enter the path to the file that contains the session information. This file must be created by the emulator when configuring the session. It must be saved in a location that the Pega user has privileges to access.
RefreshTimeout	Specifies how often a refresh occurs in milliseconds. The default is 5000. To speed up processing, you can set it to a lower value, such as 100.
ScreenDefinition	Do not change the default value, which specifies a 25x80 screen since the emulator has one more than the standard 24 rows.

Keep in mind these differences between the Fujitsu HostTalk adapter and the standard WinHllapi adapter.

The adapter uses a polling mechanism since it does not support asynchronous notifications. This is the equivalent of setting the UseExtendedFunctions property to False on a standard WinHllapi adapter.
The text adapter starts the process when it starts. It does not support connecting to a running instance. This is required by the ICLHllapi interface. The iclhllpi32 DLL launches the process and passes the session name as a parameter. This could fail for several reasons, such as the path might not exist, the session file might not exist, the user does not have permission to access the session file, and so on.
Typical WinHllapi adapters are used with a Windows adapter to start the emulator process. This is not necessary with this adapter. If a Windows adapter is required, you must set it to MonitorAll and start it before the text adapter. If the emulator is already running, starting the text adapter will launch a new window in the same process instead of starting a new process.
The emulator does not have a session ID associated with the session file. There is a session ID that is dynamically associated with the session when it starts. The system maintains this ID internally and requires no interaction.
Multiple adapters controlling multiple sessions is supported. The system launches an instance of WinHllapiHost for each adapter even though only one emulator process will run (see above). If you shut down the last adapter, you will shut down the process. The only exception is if the emulator was running prior to staring the first adapter.