Of course I had to try it for the first time in years. 1. Logon to TSO as SKIP01 at z/OS R13. 2. Issue P SKIP01 from a console. 3. Hit <enter> a few times, just get Ready. I.e. 'nothing happens'. 4. Then...
pdf IKJ56620I MVS STOP command encountered. TSO/E session is terminated. IKJ56470I SKIP01 LOGGED OFF TSO AT 13:51:50 ON DECEMBER 5, 2012 IKJ56400A ENTER LOGON OR LOGOFF- I think the key is that user is terminated at the next actual command. . . 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: Tony Harminc <t...@harminc.net> To: IBM-MAIN@LISTSERV.UA.EDU, Date: 12/05/2012 12:29 PM Subject: Re: Historical question regarding the stop command Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On 5 December 2012 14:49, Gord Tomlin <gt.ibm.li...@actionsoftware.com> wrote: > 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. I noticed that it had been removed a few years ago, but I'm not sure when it happened. It may well have been early in TSO/E. It is certainly there in the TSO in MVS 3.8. There is check of the STOP/MODIFY ECB in the main loop that issues the READY message. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
