Peter END_ECB is the address, it is DSECTed off R7 So is TASK_ADDR, END_ECB and SYS_ECB they are unique to the 4 subtasks as for the reason code as you so helpfully suggested yesterday the registers I got in my dump were from IGC062 i know with what I provided it would be close to impossible to figure out my issue however for starters I posted my code to see if my understanding of end of task processing was erroneous
Thanks > On Oct 31, 2018, at 8:13 AM, Peter Relson <rel...@us.ibm.com> wrote: > > Please provide all the relevant information in a post like this. The > IBM-Main community is very helpful but should not be wasting time trying > to guess about things that could easily have been supplied. This would > include the 23E reason code, the ATTACH (and how you saved the result) and > the data definitions that are referenced. > > If END_ECB is the ECB, then your POST is wrong. If END_ECB is the address > of the ECB, then your POST is OK. > > Having something like "_ADDR" in variable names when the content is an > address of something can be very helpful to code readers trying to > understand your intent. > > Zeroing the high byte of TCB_ADDR is unnecessary if you had set TCB_ADDR > by storing the output register 1 from the ATTACH. > > It seems unlikely that all 4 tasks can successfully use the same > completion ECB (if indeed SYSECB is "the same" as opposed to something > unique per task), and the same is true for END_ECB. > > Peter Relson > z/OS Core Technology Design > > > ---------------------------------------------------------------------- > 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