<snip> the extended addressability guide and it shows a DU-AL only for SRB and TCB, not for individual RBs. </snip>
I don't know what to clarify. A work unit (Task or SRB), AKA dispatchable unit, has an access list (that is the DU-AL). That is an architectural construct. When an IRB is given control the system switches the DU-AL to an empty one. The work unit still has a DU-AL. So, yes, due to IRBs the work unit could be thought of as having multiple access lists, only one of which is active at a time. <snip> In the Auth Assembler guide, it is stated that IRBs (created by CIRB) get control with an empty DU-AL : “Upon entry, the exit routine runs with an empty dispatchable unit access list (DU-AL). To establish addressability to a data space created by the mainline routine, the exit routine can use the ALESERV macro with the ADD parameter, and specify the STOKEN of the data space.” </snip> All fully true. <snip> ALESERV AL=WORKUNIT does not allow the ALET to be used for an IRB under the same TCB. Thus WORKUNIT means something else. </snip> I view that conclusion as incorrect. Workunit means workunit, the task. Within the processing for that work unit, there are restrictions/exceptions. Having restrictions/exceptions should not be much of a surprise. 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
