> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Paul D'Angelo > Sent: Wednesday, July 25, 2007 7:15 AM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: DSPSERV > > Gabor > > Wouldnt this design be much cleaner by starting a second address space > whose > sole purpose is to own the dataspace ? > Basically it would contain all the Data Space Code to initialize/create > and destroy the dataspace and a Console Routine to stop this Address > space. > > Granted not as elagant as an SRB scheduled to run in the MASTER Address > Space but alot cleaner. > > Paul D'Angelo
I agree that it may be cleaner to use an anchor space for the CADS. However, adding a CADS to the PASN-AL will add the same ALET to all active address spaces. There may be race conditions when the owning space terminates and another space adds its own unrelated CADS to the PASN-AL. The ALET may be reused. Also, the CADS should be allocated in a system key to prevent unauthorized programs from mucking with it. It may be cleaner to use an ordinary SCOPE=PRIVATE data space that is anchored only to the single PASN-AL of the owning address space and use space-switch PC routines to access the private data space. This will ensure that the only access to the data space is through trusted PC routines. It also ensures that when the owning address space terminates, any client code running will immediately lose their bind to the owning address space (probably a S0D5 or S0D6 abend upon redispatch). Jeffrey D. Smith Principal Product Architect Farsight Systems Corporation 700 KEN PRATT BLVD. #204-159 LONGMONT, CO 80501-6452 303-774-9381 direct 303-484-6170 FAX http://www.farsight-systems.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
