My understanding is that a "data space" is a z/OS construction, the hardware has no such concept. There's no reason a "dataspace" couldn't execute instructions as far as the hardware is concerned. Just connect the DAT tables as the primary and fire away. Of course, you'd be programming on the bare metal, with absolutely no OS support; implying the next interrupt would blow you away. And more-or-less by definition, it wouldn't be a dataspace any more. All-in-all a far-fetched and not particularly interesting idea. I presume IBM would like to deprecate and retire dataspaces completely, although the eternal backward-compatibility may prevent that for 100 years or more.
On Tue, Mar 28, 2017 at 12:38 PM, Binyamin Dissen < [email protected]> wrote: > On Tue, 28 Mar 2017 08:32:49 -0700 Ed Jaffe <[email protected]> > wrote: > > :>On 3/28/2017 8:23 AM, Tom Marchant wrote: > > :>> I could be wrong, but I don't think that the hardware cares about > :>> data spaces. A data space is an address space that contains no > :>> operating system information, including Nucleus, LPA, CSA, and SQA. > > :>The hardware does not perform ALET-qualified instruction fetch. > > Isn't an ALET a mapping to a STO? > > Can't it be placed in CR1? > > -- > Binyamin Dissen <[email protected]> > http://www.dissensoftware.com > > Director, Dissen Software, Bar & Grill - Israel > > > Should you use the mailblocks package and expect a response from me, > you should preauthorize the dissensoftware.com domain. > > I very rarely bother responding to challenge/response systems, > especially those from irresponsible companies. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
