<snip> There doesn't seem to be any documentation on what this parm means. </snip> Sure there is, as Michael Stein pointed out. And "owner" is the same for getmain, storage obtain, IARV64, IARCP64.
<snip>Seems like I would have to do a SSAR to point to the secondary asid and I am guessing the storage would reside in that asid and reference it with AR value of 1 ? </snip> In all of the obtaining storage cases, owner applies to common storage obtains (as the documentation indicates), and SECONDARY applies to the current secondary ASN when the request is made. Since common storage is never freed by the system upon some work unit's (or address space's) termination, owner does not relate to when the storage might automatically be freed. For these obtaining storage cases, for the most part, owner refers to how the storage is tracked by the system so that in a diagnostic situation you might be able to ascertain who is responsible for obtaining a particular area or who is responsible for using up "so much" common storage. Look up the DIAGxx parmlib member TRAP statement with the CSA and/or SQA options (although that does not apply to the high virtual that IARST64 deals with). Look up IPCS subcommand VERBEXIT VSMDATA OWNCOMM (similarly, I think not for high virtual). The most common usage might be in a space-switch PC target where you want to get common storage that is to be tagged as owned by the PC issuer (which usually is identified by your current secondary ASN). If ever considering SSAR, you need to factor in the authorization requirements, the non-swappability requirements with respect to the target space, and the possibility of needing to use SSAIR instead. 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
