UiPath’s Terminal Session connectivity with IBM Mainframe is intermittent

Help
, ,
4

Hi.
Sorry for very late answer here.
Truth be told, there are way too many possible reasons for intermittent connectivity issue.
We’ve been working on simplifying the situation in order to increase the chances for stability.

Via EHLL, you are dealing with 3 actors (Backend <-> Terminal Application <-> UiPath) out of which we can really control just one.

Since Terminal Activities 2.0.0, UiPath embeds (and has control over) its own terminal (integrating a well established commercial SDK).
In this paradigm, we only have 2 actors (Backend <-> UiPath) removing enough possible instability factors (and it was observed and demonstrated as such in our tests and real life projects)

So I highly recommend switching from EHLL API to the Direct Connection provider (Backend IP Address and port are needed but you will find those in IBMs terminal app configuration).

While doing this, other parameters you will need to care are: the encoding (has to be the IBM EBCDIC encoding corresponding to the language), Terminal ID (the default would work in most cases) and SSL/TLS flag. These are again items that should be available by examining the Session/Connection parameters in the existing Terminal Application (be it IBM Personal Communications or other application).

(Hope this will help in related searches as this post seems to come on top for intermittent connectivity issues).

1 Like