Skip to main content
Community site session details
Power Automate - Power Automate Desktop
Answered

Terminal Emulation session with IBM Personal Communcations of AS/400

Like (0) ShareShare
ReportReport
Posted on 22 Mar 2021 10:14:20 by 20

Hey,

 

Trying to setup a Terminal Session, and seemingly struggling to do so..

 

Using the "Open Terminal Session" from PAD, and HLLAPI as provider, and HLLAPI DLL PATH to: mypath/ehlapi32.dll

I set the session name to "A", and I am receiving the following error:

Robin.Core.ActionException: Error during Communcation emulator ---> Robin.Shared.Runtime.TerminalEmulationActionException: Exception of type 'Robin.Shared.Runtime.TerminalEmulationActionException' was thrown.

   at Robin.BridgeToHLLAPI.HLLAPIActionsImpl.<>c__DisplayClass16_0.<Open>b__0()

   --- End of inner exception stack trace ---

   at Robin.Modules.TerminalEmulation.Actions.OpenTerminalSession.Execute(ActionContext context)

   at Robin.Runtime.Engine.ActionRunner.RunAction(String action, Dictionary`2 inputArguments, Dictionary`2 outputArguments, IActionStatement statement)

Chriskhansen_0-1616407944682.png

 

Any ideas? Thanks in advance!

 

  • Verified answer
    ZS440 Profile Picture
    262 on 22 Mar 2021 at 12:27:43
    Re: Terminal Emulation session with IBM Personal Communcations of AS/400

    Hi @Chriskhansen 

    You need to start PCOM from the workstation profile (*.WS) first.
    Make sure that PCSWS.EXE is present in the running process.
    In this state, the Open terminal sesseion action will allow the PAD to access the PCOM.
    If you are using the default installation
    HLLAPI DLL path : C:\Program Files\ibm\Personal Communications\EHLAPI32.dll
    Session name :A

     

    try it.

  • Verified answer
    Chriskhansen Profile Picture
    20 on 28 Mar 2021 at 19:58:37
    Re: Terminal Emulation session with IBM Personal Communcations of AS/400

    Turns out - if I open the session from a .ws file, and make sure to NOT do anything at all (not even login), I can connect to this Session by granting the matching session name. So the solution is to open from the .ws and not do anything at all, and then connect using the name you have been granted. Seems a bit scuffed, but it works.

Helpful resources

Quick Links

Announcing our 2025 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for…

Paul Stork – Community Spotlight

We are honored to recognize Paul Stork as our July 2025 Community…

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 497 Super User 2025 Season 2

#2
David_MA Profile Picture

David_MA 436 Super User 2025 Season 2

#3
Riyaz_riz11 Profile Picture

Riyaz_riz11 244 Super User 2025 Season 2

Loading complete