Auto-answer.
I checked it.
Non-SNA (so called local connection aka ICC). => no issues related to
TCPIP settings.
Two sessions.
One with TIME=1440 in the EXEC card of the logon proc.
The second one with no TIME.
TSU jobclass has no 1440 (obviously it covers both sessions).
Result: Session with 1440 survived whole night, while the one without
was ended with x22 abend.
Note, the abend occured after TWT-defined time.
That's IMHO one of the simplest ways.
However there's still TCPIP setting to address.
Last, but not least: VPN connection can be dropped due to reasons
unrelated to mainframe at all.
One of the reasons could be inactivity.
There's also a solution even for that. It is called mouse jiggler.
Physically it is small USB dongle, which is recognized as a mouse, and
it marks mouse movements, all the time. It cost peanuts, ~$10. There's
also similar keyboard clicker.
Note: Even though such equipment is as (un)secure as a regular mouse, it
is not liked by companies because its main purpose is to simulate the
presence of users at the computer (user activity visible in Teams or
otherwise).
--
Radoslaw Skorupka
Lodz, Poland
W dniu 14.05.2025 o 19:29, Radoslaw Skorupka pisze:
Yes, I meant TIME=1440 in EXEC card, in the IKJACCNT (or any other
name) procedure in PROCLIB.
It's been many moons since I did it, but I could swear it works and it
is documented.
Unfortunately I don't know any way to find effective parameter by
examining such TSO session in SDSF.
So, the only way I know is to logon and wait.
I can't remember, however it seems to me the TSU jobclass TIME is not
relevant, however I could be wrong.
Last, but not least: TCPIP is important player here as it can drop
inactive session, which in turn gives same effect as forcibly closed
emulator window. However for testing purposes you can circumvent it by
using non-SNA (OSA-ICC) session. Such session does not depend on any
TCPIP setting, however it depends on JWT/TWT and TIME= settings.
Note: I observed that some applications preserve timeout set by TWT.
Example: regular p.3.4 screen - you're dropped after 2 hours (set by
TWT).
TSO OMVS screen or zSecure - your session will survive whole night. It
can be one of multiple ISPF screens (not OMVS, as it is different
animal, single screen).
BTW: I'm going to check 1440 trick.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
