Do you mean that TCAS issued a WTOR? Because that's the only way I can imagine TSO having had such a problem.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jesse 1 Robinson [jesse1.robin...@sce.com] Sent: Monday, July 27, 2020 6:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Keeping TSO users our of CICS This is not a 'RACF problem'. The problem lies with product that manages logins using RACF. Whipper snappers believe it or not, once upon a time TSO itself had this problem. The task gets a wait from RACF, but that task is running in the mainline of the top guy. The proper way to handle this is to put logon in a subtask, which can wait forever allowing TSO or CICS or TPX or whatever to keep business running in the meantime. I'm not a CICS guy, but it shocks me that such a mature product would behave this way. Short of a CICS fix, the shop needs to change its practices. The idea of assigning SPECIAL to a help desk jockey is pretty outré. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Tony Harminc Sent: Monday, July 27, 2020 3:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Keeping TSO users our of CICS CAUTION EXTERNAL EMAIL On Mon, 27 Jul 2020 at 18:03, ITschak Mugzach <imugz...@gmail.com> wrote: > It happens because racf is a single task. This is why other users > can't login until the wtor is replied. > I very much doubt this. It may be that this part of *CICS* is a single task for all its users, but RACF itself pretty much runs as a subroutine of the caller of RACROUTE. So it is up to CICS to not get caught up in this wait. Tony H. ---------------------------------------------------------------------- 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
