Let me see If I understand this. Lets Say I Attach a Task (TCB) - the program (RB) associated with that TCB runs and ends. The TCB is not detached.
At some undertimed time latter an SRB is scheduled into this address space. The SRB Issues TCTL with/to the TCB. So Do I understand that the program (RB) will be re-executed Again ? Is my understanding correct. Paul D'Angelo ---------- Original Message ---------- From: David Stokes <sto...@interchip.de> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: AW: Curosity Question About TCTL Date: Sat, 23 Feb 2013 17:48:23 +0000 The TCTL or RESUME kicks off the TCB code without it having to wait for the usual scheduling, as long as it is dispatchable. What the TCB code does then is up to it. >>When the resumed routine finishes executing under the TCB should it re-enter >>the WAIT state again ? No, but it presumably will at some point or terminate. -----Ursprüngliche Nachricht----- Von: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] Im Auftrag von esst...@juno.com Gesendet: Freitag, 22. Februar 2013 17:31 An: ASSEMBLER-LIST@LISTSERV.UGA.EDU Betreff: Curosity Question About TCTL I was reading about Scheduling SRBs using IEAMSCHD and discovered the TCTL macro. The TCTL (transfer control) macro allows an SRB routine to exit from its processing and to pass control to a task with minimal system overhead. When an SRB specifies RESUME RETURN=N, control transfers to the resumed TCB. Control then passes to the top RB on the TCB/RB chain, but only if the system determines that the RB is dispatchable. Again this is a curosity question and I have nop real reason to use TCTL. Am I to understand that the TCB needs to be in a WAIT state ? When the resumed routine finishes executing under the TCB should it re-enter the WAIT state again ? Its not clear to me how this facility should work. Can Some one explain the mechanics behind using TCTL and the target Task Control Block. Paul D'Angelo ---------------
