On Sat, Dec 8, 2012 at 11:06 AM, Scott Ford <[email protected]> wrote:
> Steven,
>
> I am correct in assuming that the dataspace must be created by a running STC 
> or JOB, and when shutsdown the dataspace Is deleted ?

Scott - Take a look at chapter 6 in the Extended Addressable guide
(SA22-7614).  It provides very clear answers to this question and many
others along the same lines.

With SCOPE=COMMON you will need to take special precautions to ensure
that the DATASPACE is not deleted while the possibility exists that
other address spaces can access its data.

Sam

>
> Scott ford
> www.identityforge.com
>
> Tell me and I'll forget; show me and I may remember; involve me and I'll 
> understand. - Chinese Proverb
>
>
> On Dec 8, 2012, at 12:53 PM, "Steven St.Jean" <[email protected]> wrote:
>
>> Donald,
>>
>> That's right.  Any address space with the token can access the data space.
>>
>> Something like this:
>>
>> *************************************************************
>> *    Create the Dataspace                                   *
>> *************************************************************
>>     DSPSERV CREATE,                                         +
>>           NAME=dspname,                                     +
>>           SCOPE=COMMON,                                     +
>>           KEY=8*16,                                         +
>>           STOKEN=stoken,       Where to put the STOKEN      +
>>           BLOCKS=(max,init),   Size of dspc (max,init)      +
>>           ORIGIN=origin
>>     LTR   R15,R15
>>     BNZ   fail
>> *
>> *************************************************************
>> *    Obtain an ALET for the Dataspace
>> *************************************************************
>>     ALESERV ADD,ALET=alet,                                  +
>>           STOKEN=stoken,                                    +
>>           CHKEAX=NO,                                        +
>>           AL=PASN,                                          +
>>           ACCESS=PUBLIC
>>     LTR   R15,R15
>>     BNZ   fail
>>     ...
>>     ...
>> STOKEN     DS XL8         STOKEN of dataspace
>> DSPNAME    DS CL8         Name of dataspace
>> ALET       DS AL4         ALET of dataspace
>> MAX        DC F'4096'     Max size in 4Kb blocks
>> INIT       DC F'2048'     Max size in 4Kb blocks
>> ORIGIN     DS AL4         Address of first byte of dataspace
>> ************************************************************
>>
>> Hope this helps.
>>
>> Best,
>>
>> Steven St.Jean
>> http://sdsusa.com
>>
>>
>>> -----Original Message-----
>>> From: IBM Mainframe Discussion List [mailto:[email protected]] On
>>> Behalf Of Donald Likens
>>> Sent: Friday, December 07, 2012 3:50 PM
>>> To: [email protected]
>>> Subject: Common Data Space Basics
>>>
>>> I've studied the manuals but before I start coding to use a Common Data
>>> Space I want to confirm that for a common data space access is by the
>>> PASN-AL and the ALESERV creates a PASN-AL for all the address spaces.
>>>
>>> So all I have to do is issue the DSPSERV CREATE,TYPE=BASIC,SCOPE=COMMON
>>> and ALESERV ADD,AL=PASN once and pass the ALET to all address spaces that
>>> access this dataspace. Correct?
>>>
>>> Is there additional overhead accessing data spaces as opposed to accessing
>>> primary storage? (I expect not) If an address space is created after the
>>> ALESERV macro is executed, can the new address space access the data
>>> space?
>>>
>>> ----------------------------------------------------------------------
>>> 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
>
> ----------------------------------------------------------------------
> 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

Reply via email to