It's not about users staying connected. Rather, it's the other kinds of waits that happen in a running system. True, they're not likely to happen in a dev environment these days, but if a job hangs for too long waiting on a resource that will never come available in a production environment, that would be an issue. In a production environment, that's usually set to 30 minutes or so.
On Sun, May 18, 2025 at 6:56 PM Phil Smith III <[email protected]> wrote: > Because? I've stated repeatedly that it's a dev system and I'm currently > the only user, but I'm baffled as to why anyone is hyper about users > staying connected. Bits are cheap these days. > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf > Of Steve Beaver > Sent: Sunday, May 18, 2025 7:50 PM > To: [email protected] > Subject: Re: Disable user timeout via JWT? > > I hope the 2400 is on a sandbox > > > > Sent from my iPhone > > No one said I could type with one thumb > > > On May 18, 2025, at 18:23, Phil Smith III <[email protected]> wrote: > > > > Ok, I think we might be on it now: > > D PARMLIB > > gets > > RESPONSE=S0W1 > > IEE251I 17.21.37 PARMLIB DISPLAY 231 > > PARMLIB DATA SETS SPECIFIED > > AT IPL > > ENTRY FLAGS VOLUME DATA SET > > 1 S A3CFG1 USER.Z31A.PARMLIB > > 2 S A3CFG1 FEU.Z31A.PARMLIB > > 3 S A3SYS1 ADCD.Z31A.PARMLIB > > 4 S A3RES1 SYS1.PARMLIB > > 5 S VUSER2 VENDOR.PARMLIB > > 6 S VUSER1 SVTSC.PARMLIB > > 7 S VUSER1 LVL0.PARMLIB > > > > And in > > ADCD.Z31A.PARMLIB(SMFPRM00) > > and > > USER.Z31A.PARMLIB(SMFPRM00) > > I found > > JWT(0400) > > as Jay Maynard predicted! > > > > I changed both to JWT(2400). Short of reIPLing, is there a way to make > this active? Since it's just me, I *can* reIPL, but I'd sorta rather > not--there are a bunch of things that have to be started manually, so if > there's a command it'd be easier. > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <[email protected]> On > > Behalf Of Roger Lowe > > Sent: Sunday, May 18, 2025 7:15 PM > > To: [email protected] > > Subject: Re: Disable user timeout via JWT? > > > > To find out PARMLIB concatenation order, you can issue - > > > > D PARMLIB command OR > > SDSF and then option PARM and then on the command line type SRCH > > SMFPRMxx (once you know what SMFPRMxx you are using by issuing the D > > SMF,O or D IPLINFO,SMF command) > > > > As for the IEFUTL exit and whether it is in use, you can issue - > > > > D PROG,EXIT command > > > > Roger > > > > > >> On Sun, 18 May 2025 15:55:42 -0400, Phil Smith III <[email protected]> > wrote: > >> > >> I mean "the one that's last in the list as far as I know". I'm not sure > how to check that hierarchy, though. There are four PARMLIBs, two of which > have SMFPRMxx members: LVL0.PARMLIB and VENDOR.PARMLIB (this is a former > IBM Dallas system). But I just checked and all the members have JWT(2400). > So I guess this means it's the exit? How do I tell where the exit is loaded > from? If you're thinking "This is scary that he knows so little" let me > agree 100%, but at the moment I'm the only one who can spell "z/OS" here. > Plus, as noted, it's a dev system, so there's nothing "real" on it anyway > (even our source code doesn't live there). > >> > >> D SMF,O: > >> RESPONSE=S0W1 > >> IEE967I 13.49.45 SMF PARAMETERS 222 > >> MEMBER = SMFPRM00 > >> NOWIC -- DEFAULT > >> NOHFTSINTVL -- DEFAULT > >> NOARECSIGN -- DEFAULT > >> NORECSIGN -- DEFAULT > >> SMFDLEXIT(USER3(IRRADU86)) -- DEFAULT > >> SMFDLEXIT(USER2(IRRADU00)) -- DEFAULT > >> SMFDPEXIT(USER3(IRRADU86)) -- DEFAULT > >> SMFDPEXIT(USER2(IRRADU00)) -- DEFAULT > >> EMPTYEXCPSEC(NOSUPPRESS) -- DEFAULT > >> NOPERMFIX -- DEFAULT > >> NOSMF30COUNT -- DEFAULT > >> MULCFUNC -- DEFAULT > >> DSPSIZMAX(2048M) -- DEFAULT > >> BUFUSEWARN(25) -- DEFAULT > >> BUFSIZMAX(0128M) -- DEFAULT > >> MEMLIMIT(00002G) -- DEFAULT > >> DDCONS(YES) -- DEFAULT > >> LASTDS(MSG) -- DEFAULT > >> NOBUFFS(MSG) -- DEFAULT > >> MAXEVENTINTRECS(00) -- DEFAULT > >> SYNCVAL(00) -- DEFAULT > >> INTVAL(30) -- DEFAULT > >> DUMPABND(RETRY) -- DEFAULT > >> SUBSYS(STC,NOTYPE(14:19,62:69,99)) -- SYS > >> SUBSYS(STC,NOINTERVAL) -- SYS > >> SUBSYS(STC,NODETAIL) -- SYS > >> SUBSYS(STC,EXITS(IEFUSO)) -- PARMLIB > >> SUBSYS(STC,EXITS(IEFUJP)) -- PARMLIB > >> SUBSYS(STC,EXITS(IEFU84)) -- PARMLIB > >> SUBSYS(STC,EXITS(IEFU83)) -- PARMLIB > >> SUBSYS(STC,EXITS(IEFU29)) -- PARMLIB > >> SYS(NODETAIL) -- PARMLIB > >> SYS(NOINTERVAL) -- PARMLIB > >> SYS(EXITS(IEFU29)) -- PARMLIB > >> SYS(EXITS(IEFUJI)) -- PARMLIB > >> SYS(EXITS(IEFUSI)) -- PARMLIB > >> SYS(EXITS(IEFACTRT)) -- PARMLIB > >> SYS(EXITS(IEFU84)) -- PARMLIB > >> SYS(EXITS(IEFU83)) -- PARMLIB > >> SYS(NOTYPE(14:19,62:69,99)) -- PARMLIB > >> AUTHSETSMF -- PARMLIB > >> LISTDSN -- PARMLIB > >> SID(S0W1) -- PARMLIB > >> JWT(0400) -- PARMLIB > >> STATUS(010000) -- PARMLIB > >> MAXDORM(3000) -- PARMLIB > >> REC(PERM) -- PARMLIB > >> NOPROMPT -- PARMLIB > >> DSNAME(SYS1.S0W1.MAN2) -- PARMLIB > >> DSNAME(SYS1.S0W1.MAN1) -- PARMLIB > >> ACTIVE -- PARMLIB > >> > >> -----Original Message----- > >> From: IBM Mainframe Discussion List <[email protected]> On > >> Behalf Of Jeremy Nicoll > >> Sent: Sunday, May 18, 2025 11:23 AM > >> To: [email protected] > >> Subject: Re: Disable user timeout via JWT? > >> > >>> On Sun, 18 May 2025, at 15:50, Phil Smith III wrote: > >>> Thanks. Here's the top-most SMFPRMxx: > >> > >> When you say "topmost", what do you mean? > >> > >> Are you looking at the one specified by the appropriate (as used at the > last IPL) IEASYSxx? > >> > >> Does the site override any of this by operator (or automation- > >> issued) command? > >> > >> If you're able to issue (or have someone else issue) an operator > >> command, does the > >> > >> D SMF,O > >> > >> command (which I think lists options in effect) show anything useful? > >> > >> If there is an IEFUTL exit in use, what does its (site-supplied?) code > actually do? > >> > >> -- > >> Jeremy Nicoll - my opinions are my own. > >> > >> --------------------------------------------------------------------- > >> - For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected] with the message: INFO > >> IBM-MAIN > >> > >> --------------------------------------------------------------------- > >> - For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected] with the message: INFO > >> IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Jay Maynard ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
