The pause element can be obtained from any ASSBSTKN Sent from my iPhone
> On Oct 16, 2015, at 11:26 AM, Sam Siegel <s...@pscsi.net> wrote: > > It works like POST and WAIT. The task to be suspended must call the pause > service with a valid Pause Element. > >> On Fri, Oct 16, 2015 at 8:17 AM, michelbutz <michealb...@comcast.net> wrote: >> >> >> Yes 😊I'm using 2.1 >> >> Waiting for the likes of Pete Relson to chime in >> >> Thanks so much >> >> Sent from my iPhone >> >>>> On Oct 16, 2015, at 10:58 AM, John McKown <john.archie.mck...@gmail.com> >>> wrote: >>> >>> Well, the URL that I'm reading is >> https://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieaa800/chooch.htm?lang=en >>> >>> I do see what you're reading. It's under the "Pause, Release, Transfer" >>> column, row 4. Which says: "An authorized caller can pause and release >> any >>> task or SRB in the system." >>> >>> Please confirm that you want is program "A" to be able to pause "any task >>> or SRB" in the system (same or different address space) without any >> coding >>> in the target. Oh, you might want to say what release of z/OS you're >> using >>> too. >>> >>> I take it you interpret "An authorized caller can pause and release any >>> task or SRB in the system." as meaning "An authorized caller can use the >>> pause service to pause any _other_ task or SRB in the system". From >> reading >>> the other documentation ( >> https://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieaa200/ieavpse.htm?lang=en >>> "Call Pause to make the current task or SRB nondispatchable" ) >>> >>> I interpret this to mean that an authorized user can allocate a PE in >> such >>> a way as to allow that PE to be used by any task or SRB to suspend >> itself. >>> And that any _other_ task or SRB in the system can then use that same PE >> to >>> resume the paused task or SRB. >>> >>> I guess what I'm saying, at least until someone corrects me, is that the >>> sentence is either too ambiguous or just down right wrong. I don't see a >>> way for program "A" to cause some other "task of SRB" to be suspended (or >>> paused) without the target "task or SRB" doing something. IIRC, what you >>> want is something like CALLRTM (which abends any task or SRB in the >>> system), but which just "stops" it instead of abending it. >>> >>> I must now bow out to those more knowledgeable than I about the >> internals. >>> If this were _my_ need, my approach would be to schedule an SRB into the >>> address space which would schedule a CIRB which would do a SUSPEND >>> RB=PREVIOUS. Then something later would need to schedule an SRB into the >>> address space which would do a RESUME TCB=,RETURN=N to allow the >> suspended >>> work to continue. >>> >>> -- >>> >>> Schrodinger's backup: The condition of any backup is unknown until a >>> restore is attempted. >>> >>> Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will >> be. >>> >>> He's about as useful as a wax frying pan. >>> >>> 10 to the 12th power microphones = 1 Megaphone >>> >>> Maranatha! <>< >>> John McKown >>> >>> ---------------------------------------------------------------------- >>> 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 > > ---------------------------------------------------------------------- > 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
