Thank you for replying. Also am I to understand that if I have program A creating a scope=common dataspace that program must not exit and maintain itself possibly waiting on an ecb to be posted so that it can then go to EOJ?
-----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Glen Garrison Sent: Wednesday, March 12, 2025 10:18 AM To: [email protected] Subject: [EXT] Re: Dataspaces Please Note: This email is from an [EXTERNAL] sender. Do not click on links or attachments unless you expect them from the sender and know the content is safe. Please contact the Service Desk if you have any concerns regarding this message. >From z/OS extended addressability guide..... Relationship between the data space and its owner Your program can create a data space, but it cannot own the data space. If the unit of work that represents the program is a TCB, that TCB is the owner of the data space, unless the program assigns ownership to another TCB. If the unit of work is an SRB, the program must assign ownership to a TCB. Because of this assignment of ownership, the owner of the data space and the creator of the data space are not always the same TCB. The data space virtual area is available to programs that run under the TCB that owns the data space and is available, in some cases, to other programs. When a TCB terminates, the system deletes any data spaces that the TCB owns. The system swaps a data space in and out as it swaps in and out the address space that dispatched the owning TCB. Thus, data spaces shared by programs that run in other address spaces must be owned by TCBs in non-swappable address spaces. A data space can remain active even after the creating TCB terminates. When the program creates a data space, it can assign ownership of the data space to a TCB that will outlast the creating TCB. In this case, the termination of the creating TCB does not affect the data space. Because access lists and data spaces belong to units of work, keep in mind the relationship between the program and the unit of work under which it runs. For simplicity, however, this chapter describes access lists and data spaces as if they belong to programs. For example, "a program's DU-AL" means "the DU-AL that belongs to the TCB under which a program is running". ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Ward, Mike S <[email protected]> Sent: Wednesday, March 12, 2025 11:08 AM To: [email protected] <[email protected]> Subject: [EXTERNAL] Dataspaces I have a question. If a program creates a dataspace, and the program ends or abends. Does the dataspace go away or is it still there? ======================================= This email, and any files transmitted with it, is confidential and intended solely for the use of the individual or entity to which it is addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete this e-mail from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ======================================= This email, and any files transmitted with it, is confidential and intended solely for the use of the individual or entity to which it is addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete this e-mail from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
