Issue with handling System Exception for Terminal activities

[Nizri_Daniel]

Hello Team,

Using reframework, if hit system exception, i would like for the process to restart the terminal session from the beginning, so to also close the current terminal session. I try to use just an empty terminal session, to close the connection immediately, but it doesn’t works and the terminal session would still be there, so then it would open another terminal session during the actual login.

In the tooltips its mentioned that the close connection will be ignored if the output connection is filled, but mine is definitely empty, but what i dont understand is why there is a variable that is not created by me available to be select in the terminal session sequence called “terminalSession”. Is this the reason why the terminal refuse to close? Is there a way to delete that variable?

[ashokkarale]

@Nizri_Daniel,

Follow this solution.

Mainframe Terminal Session - Already logged in issue

@shyamala_shyamu, After Kill process try this. Thanks, Ashok

Thanks,
Ashok

[ppr (Peter Preuss)]

@Nizri_Daniel

I try to use just an empty terminal session, to close the connection immediately, but it doesn’t works

it depend on a serveral details. But when session A was involved in flow is active, alive, not properly closed it can happen when:

@Nizri_Daniel

use just an empty terminal session, to close the connection immediately

that a session B is started and closed. But Session A is not touched by this actions