Thanks. Here's the top-most SMFPRMxx:
INTVAL(01)             /* SET SMF INTERVAL AT 1 MIN FOR AUTO TESTS */
SYNCVAL(01)            /* SYNC SMF AT 1 MIN FOR AUTO TESTS */
DDCONS(NO)             /* SAVE CPU TIME */
ACTIVE                 /*ACTIVE SMF RECORDING*/
DSNAME(SYS1.&SYSNAME..MAN1,SYS1.&SYSNAME..MAN2)
NOPROMPT               /*DO NOT PROMPT OPERATOR FOR OPTIONS*/
REC(PERM)              /*TYPE 17 PERM RECORDS ONLY*/
MEMLIMIT(3G)           /* MEMLIMIT(1280M) CHG W 2.2 *?
MAXDORM(3000)          /* WRITE AN IDLE BUFFER AFTER 30 MIN*/
STATUS(SMF,SYNC)       /* CREATE SMF STATUS TYPE 23 IN SYNC     */
JWT(2400)              /* 522 AFTER 24 HOURS  */
SID(&SYSNAME(1:4))     /* SYSTEM ID                   */
LISTDSN                /* LIST DATA SET STATUS AT IPL*/
LASTDS(MSG)            /* SEND A MESSAGE WHEN OUT OF BUFFERS */
NOBUFFS(MSG)                /*DEFAULT TO MESSAGE          */
SYS(NOTYPE(14:19,62:69,99),EXITS(IEFU83,IEFU84,IEFU85,IEFACTRT,
     ENFEXT37,IEFUJV,IEFUSI,IEFUJP,IEFUSO,IEFUJI,IEFUTL,IEFU29,IEFUAV),
     INTERVAL(SMF,SYNC),DETAIL)

SUBSYS(STC,TYPE(37,229))
SUBSYS(STC,INTERVAL(000100))
SUBSYS(STC,EXITS(IEFU29,IEFU83,IEFU84,IEFU85,IEFUJP,IEFUSO))

So yes to IEFUTL.

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

OK, let's step back and look over things, start to finish.

What's being measured is continuous wait time while the application (whatever 
is on the EXEC= statement) is in control. The common case for TSO is the time 
that the TSO application program spends waiting for the user to press ENTER.

In SMFPRMxx, there are three parameters that control the wait time before the 
system calls IEFUTL: JWT, TWT, and SWT. JWT is the default wait time in hours 
and minutes; TWT and SWT supply the same values for TSO sessions and STCs, 
respectively, and default to JWT if not specified.

The documentation for SMFPRMxx says that if TIME=1440 is coded on the JOB or 
EXEC JCL statement, or if it is defaulted by the JES class attribute of 
TIME=1440, IEFUTL is not invoked for that job. It also says that the wait time 
interval is checked every 90 seconds, so the actual call to IEFUTL might be 
delayed up to that long.

The documentation for IEFUTL says that if it is not invoked (because it's been 
disabled or is not specified in the SMFPRMxx EXITS= parameter), the system 
proceeds to issue the S322 or S522 ABEND. There's no mention of
TIME=1440 turning that off in that discussion.

So there are a few parameters that can affect it: SMFPRMxx [JTS]WT, TIME= on 
the EXEC statement, JES2's class TIME= defaults, and IEFUTL itself.

Do you even have an IEFUTL? Is it specified in SMFPRMxx's EXITS= statement?

On Sun, May 18, 2025 at 8:24 AM Phil Smith III <li...@akphs.com> wrote:

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


--
Jay Maynard

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