>I know dataspaces have to be attached. To paraphrase, it's what we know but that isn't true that causes problems. Data spaces are unrelated to 64-bit storage (private or common).
>I need to allocate 64bit storage that's not attached to a >TCB, much like sp 231 IS ... >See the OWNER keyword on the IARST64 macro I disagree. There is no real need to see anything if you want "like SP231". Common storage is never "attached to a TCB", whether it's SP 231, 241, 239, 245 (etc) or above-2G storage. The OWNER keyword on IARST64, as on GETMAIN/STORAGE, is for tracking purposes, not for cleaning-up-on-termination purposes (which is usually what we think of for the "owner" of private storage). If you're talking about private storage above-2G then we would be talking about "much like sp255 is". Somewhat strangely (to me, anyway) there is no such concept for IARV64. The default is "current task" and anything else requires specification of a valid TCB Token via the TTOKEN parameter. So the closest that you can come to "no task ownershp" is to use the TCB Token of the ASXBFTCB task (that's the RCT task). I don't recall if the system actually guarantees that all SRBs have terminated before the RCT task goes through the final stages of end-of-task at the end of an address space (the point at which storage would be unallocated by the system), but if it's not reality it's probably close enough to reality that this works OK. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
