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.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 14.05.2025 o 16:01, Phil Smith III pisze:
Hmm. Still got an S522 overnight, so I guess that wasn't what you meant?
TWT looks to have the same 24-hour limit as JWT? This is a dev system, we don't
want users forced at all. Surely that's not unique, and doesn't require use of
an exit?!
-----Original Message-----
From: IBM Mainframe Discussion List<[email protected]> On Behalf Of Phil
Smith III
Sent: Tuesday, May 13, 2025 5:58 PM
To:[email protected]
Subject: Re: Disable user timeout via JWT?
I think I did #2:
//DYNISPFM EXEC PGM=IKJEFT01,DYNAMNBR=200,TIME=1440
// PARM='%DYNISPF'
That's in my logon PROC. Is that what you meant? Yes, I know very little about
this end of z/OS (or most other ends).
I did make the change from IBMUSER and then log off and back on to be sure I
wasn't locking myself out!
Is there a way to look at the time limit for a running job? I scrolled wayyyy
right in SDSF and didn't see it.
-----Original Message-----
From: IBM Mainframe Discussion List<[email protected]> On Behalf Of
Radoslaw Skorupka
Sent: Saturday, May 10, 2025 11:16 AM
To:[email protected]
Subject: Re: Disable user timeout via JWT?
W dniu 10.05.2025 o 16:33, Phil Smith III pisze:
Is there a way to keep idle users from getting forced off? JWT in SMFPRMxx is
documented as taking values 0001 to 2400. We have a handful of users on a
development system behind a VPN and don't want them forced off ever. Is there
an easy way to achieve this?
Few remarks:
1. Use TWT instead of JWT. TWT is quite new (younger than me ;-) ). It is for
TSO users.
2. Use TIME=1440 (or NOLIMIT for modern installations ;-) ) in the logon
procedure. It disables both JWT or TWT.
3. Don't forget about TCPIP settings. I can't remember the name, but network
folks like to drop inactive sessions. This is independent from JWT/TWT,
TIME=1440 and other TSO settings.
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
