A few centralizing comments.
- 64-bit:
There are known difficulties in dealing with x64 64-bit IBM Terminal Apps (be it Personal Communications or ACS) through EHLL API (in short, it’s a DLL bridge involved). The suggestions here would be, highest preference order first:
- Switch from IBM EHLL API to Direct Connection provider in Terminal Session. (please see this for a bit more details: UiPath’s Terminal Session connectivity with IBM Mainframe is intermittent - #4 by cornel )
- Failing at that for whatever reason, switch to 32-bit version of the IBM terminal app (should be covered by the same license as the 64 one)
- EHLL API things to try:
a) Try the “Run In Process” option in the EHLL API configuration. What this does, the terminal related activities will not be conducted through an external process anymore (no UiPath.Service.Host windows process).
This helps in certain high security environments which could interfere with the Inter-process Communication.
b) Try the different hll api dlls available. These are my known approaches:
But in the end, the main recommendation here would be to switch to Direct Connection ( UiPath’s Terminal Session connectivity with IBM Mainframe is intermittent - #4 by cornel )
ashokkarale
Anil_G
Yoichi
yangyq10
postwick
chandreshsinh.jadeja
aravindbalineni123
Parvathy
aya
PRASHANT_GABHANE