Where is that?

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Mark Jacobs
Sent: Wednesday, May 14, 2025 12:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: EXTERNAL Email: Re: Disable user timeout via JWT?

You should be able to set TIME=(1440) on the JES2 JOBCLASS(TSU) statement to 
prevent TSO users from timing out. 

Mark Jacobs

Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com


On Wednesday, May 14th, 2025 at 12:41 PM, Jerry Whitteridge 
<jerry.whitteri...@albertsons.com> wrote:

> I've always coded the TIME=1440 on the jobcard not the steep.
> 
> Jerry Whitteridge
> Sr Manager Managed Services
> Tech Operations & Innovation
> jerry.whitteri...@albertsons.com
> 480 578 7889
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf 
> Of Phil Smith III
> 
> Sent: Wednesday, May 14, 2025 7:02 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: EXTERNAL Email: Re: Disable user timeout via JWT?
> 
> 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 IBM-MAIN@LISTSERV.UA.EDU On Behalf 
> Of Phil Smith III
> 
> Sent: Tuesday, May 13, 2025 5:58 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 IBM-MAIN@LISTSERV.UA.EDU On Behalf 
> Of Radoslaw Skorupka
> 
> Sent: Saturday, May 10, 2025 11:16 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN 
> ________________________________
> Warning: All e-mail sent to this address will be received by the corporate 
> e-mail system, and is subject to archival and review by someone other than 
> the recipient. This e-mail may contain proprietary information and is 
> intended only for the use of the intended recipient(s). If the reader of this 
> message is not the intended recipient(s), you are notified that you have 
> received this message in error and that any review, dissemination, 
> distribution or copying of this message is strictly prohibited. If you have 
> received this message in error, please notify the sender immediately.
> ________________________________
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to