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.
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
On 2012-12-05 09:03, McKown, John wrote:
To my remembrance, START, STOP, and MODIFY we all original commands in OS/360 (I can be
wrong, I don't go back that far). They do not do asynchronous functions like
"kill" does. They basically post an ECB. It is up to the program to
periodically query this ECB (see the QEDIT macro). That's why entering a STOP command
doesn't always STOP a broken STC. You can even STOP a batch job step. If the program is
proper set up, it will process the STOP request and terminate. I don't know about today's
environment, but in the past, if you did this and the program didn't remove the STOP
request from the queue but terminated instead, then the initiator would see the STOP and
it would shut down. This was many years ago, so it may not do this anymore.
BTW, did you know that a TSO user's address space will honor a STOP command? But ISPF
doesn't. So, in the old days, an operator could "P tsoid" and the user's TSO
session would terminate when they next went to the READY prompt, usually at the end of a
command. Since, to TSO, ISPF is basically a never-ending command, the P doesn't have much
effect any more.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
