I confess to not knowing the gizzard level details, but I suspect that TIME is not a 'real' TSO command in the way that D T (I'm told) is not a real console command. The gizzard wizards on the list can evaluate this opinion.
In any case, aside from some odd reports of inconsistency, it would appear that 'P userid' pretty much relegates a user to the trash heap once out of ISPF, which was the original goal of the shop I mentioned earlier. . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Gord Tomlin <gt.ibm.li...@actionsoftware.com> To: IBM-MAIN@LISTSERV.UA.EDU, Date: 12/05/2012 03:58 PM Subject: Re: Historical question regarding the stop command Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> Apparently it depends on the command used. TIME does not cause this behavior: [STOP command issued here] READY READY time IKJ56650I TIME-06:54:36 PM. CPU-00:00:02 SERVICE-34255 SESSION-04:12:58 DECEMBER 5,2012 READY alloc f(foo) da(*) IKJ56620I MVS STOP command encountered. TSO/E session is terminated. IKJ56470I [redacted] LOGGED OFF TSO AT 18:55:52 ON DECEMBER 5, 2012 IKJ56400A ENTER LOGON OR LOGOFF- -- Regards, Gord Tomlin Action Software International (a division of Mazda Computer Corporation) Tel: (905) 470-7113, Fax: (905) 470-6507 On 2012-12-05 17:23, Robert A. Rosenberg wrote: > At 14:49 -0500 on 12/05/2012, Gord Tomlin wrote about Re: Historical > question regarding the stop command: > >> I had never heard of the ability to issue a STOP command for a TSO >> session, so I tried it with one of my TSO sessions (which was in READY >> mode), and nothing happened. It would appear that as of z/OS 1.13 this >> ability no longer exists. > > The STOP takes effect when the session goes into READY mode. If you are > already in READY mode I would expect that there is a need to first have > a command run that when it completes will go back into READY mode. Try > the test again and issue some command and see what happens. I am NOT > saying that it no longer works under 1.13 but only that you did not test > it correctly. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
