> May I assume that "telling" includes providing z/OS with the address of the
> ECB(s)?
Asking, actually, LOL.
*------------------------------------------------------------------*
* OBTAIN ADDRESS OF THE CIB *
* From z/OS V1R10.0 MVS Authorized Assembler Services Guide p. 2-4
*------------------------------------------------------------------*
*
* Now see if have a CIB
EXTRACT COMADDR,FIELDS=COMM,MF=(E,EXTRACTL)
L R8,COMADDR GET ADDRESS OF THE AREA
USING COM,R8 USE R8 AS BASE ADDRESS OF COMM AREA
*
* Pick up ECB address out of the COM
L R0,COMECBPT
ST R0,ECBLISTC Store in ECB list
*
* Use QEDIT to set MODIFY count to one
QEDIT ORIGIN=COMCIBPT,CIBCTR=1
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Wednesday, December 05, 2012 9:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Historical question regarding the stop command
On Wed, 5 Dec 2012 08:03:16 -0800, Charles Mills wrote:
>> How does STOP work?
>
>From a programmer's point of view, it sets a flag and posts an ECB.
>
>> Is MODIFY similar?
>
>Yes, both are quite similar in how they work. Modify is a flag plus the
>text of the command. AFAIR Stop is just a flag, but I might well be
>wrong and I am too lazy to look it up right now.
>
Same ECB or different ECB? Or does the flag indicate whether the operation was
STOP, MODIFY, or ... (What else?)
>z/OS "knows" whether a program has gone through the motions of telling
>z/OS it was prepared to accept console commands. ...
>
May I assume that "telling" includes providing z/OS with the address of the
ECB(s)?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
