I'm not arguing--I don't know, obviously--but that contradicts folks who said 
that TIME= on the EXEC statement in the logon PROC would work. You're saying no?

But meanwhile, the PARMLIB member has
JWT(2400)              /* 522 AFTER 24 HOURS  */
so I'd expect it to be, like, 24 hours. And remember that
$TJOBCLASS(TSU),TIME=
shows
RESPONSE=S0W1
 $HASP837 JOBCLASS(TSU)
 $HASP837 JOBCLASS(TSU)       AUTH=(ALL),BLP=NO,COMMAND=EXECUTE,
 $HASP837                     CONDPURG=NO,DSENQSHR=ALLOW,
 $HASP837                     IEFUJP=YES,IEFUSO=YES,
 $HASP837                     JESCANCEL=ALLOWED,JESLOG=(NOSPIN),
 $HASP837                     LOG=YES,MSGLEVEL=(1,1),MSGCLASS=K,
 $HASP837                     OUTDISP=(PURGE,HOLD),OUTPUT=YES,
 $HASP837                     PERFORM=000,PROMO_RATE=0,
 $HASP837                     PROCLIB=00,QAFF=(ANY),REGION=0000K,
 $HASP837                     SWA=ABOVE,TIME=(001440,00),
 $HASP837                     TYPE26=YES,TYPE6=YES,
 $HASP837                     RESOURCE(TG)=(LIMIT=DEFAULT,
 $HASP837                     ACTION=DEFAULT),
 $HASP837                     RESOURCE(JOE)=(LIMIT=DEFAULT,
 $HASP837                     ACTION=DEFAULT),DESC=

So I'm feeling like it's not SMF?

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Seymour J Metz
Sent: Sunday, May 18, 2025 9:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Disable user timeout via JWT?

There's nothing special about 24 hours; the wait-time limit is set by SMF. You 
can change it in JES parameters, but not in JCL.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר



________________________________________
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of 
Phil Smith III <li...@akphs.com>
Sent: Sunday, May 18, 2025 9:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU <IBM-MAIN@LISTSERV.UA.EDU>
Subject: Re: Disable user timeout via JWT?


External Message: Use Caution


I can try that, but it isn't even going 24 hours, so something else must be 
triggering, no?

Does this tell anyone anything:
IEA631I  OPERATOR PHS      NOW INACTIVE, SYSTEM=S0W1    , LU=TCP00025
IEF450I PHS DYNISPFM DYNISPFM - ABEND=S522 U0000 REASON=00000000  728
        TIME=16.47.23
$HASP395 PHS      ENDED - ABEND=S522

Doc (https://www.ibm.com/docs/en/zos/2.5.0?topic=messages-iea631i) says:
An extended MCS (EMCS) console has been deactivated.

This suggests to me that my connection is 'special' but I don't know what EMCS 
means, and some searching hasn't helped. If this turns out to be key, I'll feel 
stoopid for not having pasted it earlier!

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Seymour J Metz
Sent: Saturday, May 17, 2025 6:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Disable user timeout via JWT?

TIME=UNLIMITED?

----------------------------------------------------------------------
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