On 23 May 2014 10:47, Ed Jaffe <[email protected]> wrote: > On 5/23/2014 5:04 AM, Peter Relson wrote:
>> Of course I agree that it is much easier when the TCB key matches the >> execution key. This can be done for subtasks which is why ATTACH supports >> attaching a task but not making it dispatchable initially (DISP=NO), >> giving the attacher the opportunity to change the key before it is >> (approximately) "too late" and then indicate ATTACH DISP=RESET. But the >> PPT is the only mechanism for the jobstep program task. > > Never knew specifically where DISP=NO came from. Thanks for sharing. We've > leveraged that very useful feature for many different purposes, for example > to have the attaching task construct a name/token, usable by code running in > the subtask, whose name contains the four-byte subtask TCB address. Cute. The main reason I've used DISP=NO is to have the opportunity to update TCBSENV with an appropriate ACEE before letting it run. How much more elegant is this DISP=NO mechanism than some specific scheme to change the key on ATTACH... Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
