Method and system for storing data in and retrieving data from a non-main storage virtual data space
CROSS REFERENCE TO RELATED APPLICATIONS 
     This application contains subject matter which is related to the subject matter of the following applications filed on Feb. 10, 1988 and assigned to the same assignee: &#34;Control Mechanism for Zero-Origin Data Spaces&#34;, by C. A. Scalzi, et al., U.S. Pat. No. 5,008,811, issued Apr. 16, 1991; &#34;Linkage Mechanism for Program Isolation&#34;, by R. I. Baum, et al., (Ser. No. 154,733 abandoned, continuation filed Jul. 19, 1991, Ser. No. 732,936 ); &#34;Home Space Facility&#34; by C. E. Clark, U.S. Pat. No. 4,943,913, issued Jul. 24, 1990; &#34;Access Register Translation Means for Address Generating Mechanism for Multiple Virtual Spaces&#34;, by R. I. Baum et al., U.S. Pat. No. 4,979,098, issued Dec. 18, 1990; &#34;Nonhierarchical Program Authorization Mechanism&#34;, by R. I. Baum et al., U.S. Pat. No. 5,023,773, issued Jun. 11, 1991; &#34;Domain Related Access Lists&#34;, by C. E. Clark, et al., U.S. Pat. No. 4,945,480 issued Jul. 31, 1990; and &#34;Method and System for Mapping Data in a Virtual Storage Data Processing System&#34;, by C. Eilert et al., filed on even date herewith and also assigned to the same assignee. These co-pending applications are incorporated by reference herein. 
     FIELD OF THE INVENTION 
     This invention relates to the field of systems control programming. More specifically, it relates to the structure and capabilities of virtual data spaces, and methods for performing I/O to certain virtual data spaces. 
     DESCRIPTION OF THE PRIOR ART 
     In a virtual storage data processing operating system, such as IBM&#39;s MVS, MVS/XA and MVS/ESA, a virtual address space is a control structure that provides an addressing range within which a set of programs operate. See, e.g., MVS/Extended Architecture Overview, form GC28-1348; IBM Enterprise Systems Architecture/370 Principles of Operation, form SA22-7200. A virtual address space may contain both programs and data, while a special form of address range, called a data space, may contain only data. The aforementioned &#34;Control Mechanism for Zero-Origin Data Spaces&#34; (Ser. No. 154,688) details the differences between data spaces and address spaces. One common feature of all such prior art address ranges is that data within any such address space or data space, at a particular point in time, might reside in real (or main) storage, or in non-main storage (expanded storage, auxiliary storage, external storage, etc.). When, for example, a program executing in an address space referenced a virtual address within that same address space, two possibilities existed: if the virtual address represented data that was already in real storage, processing continued; if the virtual address represented data not in real storage, program execution was suspended, the data was brought into real storage, and program execution resumed. 
     The prior art also recognizes mechanisms for an application referencing and manipulating data residing in an address space other than that in which the application is running, or residing in a data space. Examples of such mechanisms include those of U.S. Pat. No. 4,355,355 entitled &#34;Address Generating Mechanism for Multiple Virtual Spaces&#34; to J. R. Butwell, et al., and 4,521,846, entitled &#34;Mechanism for Accessing Multiple Virtual Address Spaces&#34; to C. A. Scalzi, et al., both also assigned to the assignee of the present invention as well as the Cross-Memory function of MVS System Programming Library: System Macros and Facilities, Volume 1, form GC28-1150. 
     In some cases, it may be desirable to write data into a data space as a &#34;temporary container&#34; for that data, subsequently bringing the data back into the address space. The sequence of steps previously necessary to accomplish this includes reading the data to be written into main storage in the event that the address space page is backed by auxiliary storage; reading the target page into main storage in the event that the target data space virtual page is backed by auxiliary storage; moving the data within main storage from the address space backing page to the data space backing page. It should be clear that if the intent is simply to temporarily store the data in the data space, without referencing it there, the two I/O operations, and attendant CPU cache space replacement, is wasteful. 
     Finally according to the prior art, moving data from an address space to auxiliary storage might be either &#34;synchronous&#34;--meaning control is returned to the application only after the I/O completes, or &#34;asynchronous&#34;--meaning control is returned immediately, but the application is responsible for insuring that the I/O completes before, for example, re-using an output buffer. 
     SUMMARY OF THE INVENTION 
     In accordance with the present invention, a non-main storage data (NMDS) space is introduced which may be advantageously used as a temporary receptacle for data which will not be referenced directly while in the NMDS, but will be moved to a conventional address space or data space before being referenced. This NMDS is similar to address spaces and main storage data spaces, except that its virtual storage pages may never be backed by main storage. 
     Taking advantage of the characteristics of this NMDS, methods for performing I/O are presented which improve performance by allowing the switching of auxiliary storage backing pages between the NMDS and an address space, when possible, thereby avoiding physical I/O operations in many cases. Also, mechanisms are provided for performing I/O which, in certain cases, permit initiating programs to continue execution after initiating the I/O, then being able to immediately reference the input or output buffers--the system&#39;s paging mechanisms are used for necessary synchronization, without any awareness on the part of the initiator. 
     It is therefore an object of this invention to provide a novel type of addressing range (a NMDS), usable for temporary data storage with improved performance characteristics. 
     It is a further object of this invention to provide efficient methods of bringing data into and out of a NMDS. 
     It is a further object of this invention to allow MVS/ESA applications to reference and modify data in separate address/data spaces without the requirement of executing in &#34;AR&#34; (Access Register) mode. 
     It is still a further object of this invention to provide methods to permit, in appropriate cases, applications to initiate I/O operations to NMDS&#39;s and immediately be able to reference the input or output buffer area, without waiting for the I/O to complete, by using the system&#39;s normal page fault mechanisms for necessary synchronization. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     FIG. 1 is a block diagram illustrating the logical difference between a main storage data space, and two forms of Non-Main Storage Data Spaces (NMDS&#39;s) of the present invention: &#34;Standard&#34;, and &#34;ESTOR&#34; (Expanded Storage) Only&#34;. 
     FIG. 2A is a block diagram illustrating the use of a System 370 instruction referencing operands in the address space of the instruction issuer. 
     FIG. 2B is a block diagram illustrating the use of a System 370 instruction referencing operands in a separate (main storage) data space. 
     FIG. 3 is a logical diagram illustrating the relationship between an ASTE and an STOKEN. 
     FIGS. 4A and 4B are a flow chart showing the steps involved in a request to write data from an address space to a NMDS of this invention. 
     FIGS. 5A and 5B are a flow chart showing the steps involved in a request to read data from a NMDS of this invention to an address space. 
     FIG. 6 the portions of a page table entry relevant to this invention. 
     FIG. 7 is a logical representation of the contents of virtual and physical storage during the writing of a page from an address space to a NMDS of this invention. 
     FIG. 8 a logical representation of the contents of virtual and physical storage during the reading of a page from a NMDS of this invention to an address space. 
     FIG. 9 is a block diagram illustrating the relationship between the virtual address of a page, and the virtual address of that page&#39;s page table entry. 
    
    
     DESCRIPTION OF THE PREFERRED EMBODIMENT 
     FIG. 1 presents a logical view of two embodiments of the non-main storage data space of the present invention: A &#34;standard&#34; non-main storage data space (Standard NMDS) 10, and an expanded storage only non-main storage data space (ESTOR NMDS) 11. (&#34;Expanded Storage&#34; has also been termed &#34;page storage&#34;--and method of accessing it are described in U.S. Pat. No. 4,476,524 to D. T. Brown, et al., issued Oct. 9, 1984, and assigned to the assignee of the present invention.) In FIG. 1, Data Space 13 is shown as being backed by main storage 15 (as well as by expanded storage and auxiliary storage--DASD). Since it is backed by main storage, any storage referencing instruction may reference data space 13 from primary address space 12. For contrast, logical views of the two types of NMDS of the present invention (Standard 10, and ESTOR only 11) are also shown. The most significant difference lies in the fact that virtual pages in the two NMDS&#39;s 10, 11 may never be &#34;backed&#34; by main storage, while both an address space 12 and a data space 13 may have virtual pages backed by main (real) storage 14, 15. In an ESTOR NMDS 11, virtual pages can be backed only by expanded storage 16, while a Standard NMDS 10 can have virtual pages backed by either expanded storage 17, or auxiliary storage 18. Because of the special character of NMDS&#39;s, reference to them is not by &#34;normal&#34; storage referencing instructions, but rather by special instructions (e.g., SREAD/SWRITE(19) for a standard NMDS  10, or CREAD/CWRITE (19A) for an ESTOR only NMDS). 
     A characteristic that flows naturally from the definition of a NMDS is that data residing in it may not be accessed by traditional (e.g., IBM System 370) storage referencing instructions which rely on the fact that the data represented by their operands is in real (main) storage. For example, FIG. 2A illustrates a &#34;CLC&#34; (compare logical character) instruction 201, in an MVS/XA system, comparing operand A 203 in the same virtual address space as the instruction at the virtual address indicated by 202, with operand B 205, also in the same virtual address space, at the virtual address indicated by 204. After conventional address translation and page fault processing (indicated at 206), the operands, still in virtual address space A, are physically located in main storage 207, 208, here they can be accessed for instruction execution. In order for a storage-referencing instruction to reference an operand residing in an address space or data space other than the address space containing the operand, the other address/data space must first be on an &#34;access list&#34; associated with the instruction--issuing application. The mechanism for using an access list in this manner is the subject of the aforementioned copending application &#34;Domain Related Access Lists&#34;, by C. E. Clark, et al. (Ser. No. 154,685). An application requesting to have an address/data space added to its access list must do so via a control program service. However, this control program service, before adding an address/data space to an application&#39;s access list, first checks to see whether the address/data space is a NMDS-type data space. The present invention makes use of the access list concept by associating with ASN (Address Space Number) second table entries (ASTE&#39;s) an indicator of whether a particular address/data space is a NMDS. If so, requests to add the NMDS to an access list by an application will be rejected by the system service. FIG. 3 illustrates this mechanism. 
     The creation of a data space/address space by an application results in the generation of an STOKEN (Space Token) 301 for subsequent references to the space. The STOKEN 301 logically points to the Data Space Descriptor 302, which is used to locate the ASTE 303, in turn containing the segment table descriptor 304 (locating the segment table 305, and Page Table 306). (Note that &#34;Page table&#34; may be read here to include the usual case where there are both Page tables and Extended Page tables. The distinction is not relevant to this invention.) If the creation was a NMDS, an indicator 307 in a data space descriptor flags the data space as a NMDS. Additional indicators flag it as an Expanded Storage Only (ESTOR) type NMDS 308, or a Standard (Expanded or Auxiliary Storage backing) type NMDS 309. For a main storage data space, such as that indicated by STOKEN 310, the NMDS indicator 312 in data space descriptor 311 is &#34;OFF&#34;. Thus, when a request is made to add the data space associated with STOKEN 310 to the requestors access list 313, the system service detects 312 that the data space is not a NMDS, and so adds an access list entry 314 to the access list, and returns an ALET (Access List Entry Token) 315 which the application subsequently uses to access data in the data space. If, on the other hand, the application indicates that the NMDS associated with STOKEN 301 be added to an access list, the system service detects 307 that it is an NMDS-type data space, and rejects the request. Without an ALET, the application is unable to directly reference data in the NMDS. 
     In FIG. 2B, representing an MVS/ESA system, a similar CLC (Compare Logical) instruction 201 is shown, but the operands 203A and 205A reside in different address/data spaces from address space A. Through the Access Register--based address translation process 206A of MVS/ESA these operands are paged into main storage 207A, 208A which backs the virtual storage in the address/data spaces. Since by definition a NMDS virtual page is never backed by main storage, a mechanism must be provided for moving data between a NMDS and a conventional address space for reference by standard instructions. The mechanism described here includes the SREAD/SWRITE (Cache Read/Cache Write) services (FIG. 1 at 19) for standard NMDS&#39;s, and the CREAD/CWRITE services 19A for ESTOR NMDS&#39;s. 
     SWRITE/CWRITE 
     FIGS. 4A and 4B show the steps involved in a request by an application to write data from an address space to a NMDS. FIG. 7 illustrates a specific example of such a &#34;write&#34;--which will help explain the steps. In requesting the write, the application specifies: The number of contiguous pages to be written 401 (in the example of FIG. 7, this is 2); the virtual address of the starting page J in the application&#39;s address space 402 to be written; the virtual address of the starting page K in the NMDS being written to 403; and the STOKEN of the NMDS being written to 404. 
     First, 405, the page table entry (PTE) Pj associated with virtual page J in the address space is located via the virtual address of page J 402 (explained below); the data space descriptor (DSD) associated with the NMDS is located via STOKEN 404; and PTE Pk associated with page K in the NMDS is located via STOKEN 404 and the virtual address of page K 403, as indicated below. 
     Next, 406, a test is made whether the PTE for page J &#34;points to&#34; real (main) storage, indicating that page J is backed by a page in real storage. This is determined by examining the PTE (FIG. 6). &#34;Invalid&#34; indicator 63, if &#34;OFF&#34;, shows that the associated page is backed by real storage (is &#34;valid&#34;)--which real address is indicated in field 61. In the example of FIG. 7, the first page 701 is backed by main (real) storage 703; the second page 702 is not--it is backed by auxiliary storage 704. 
     If the page was not backed by main storage (the case with page 2 702), then 407 a test is made whether PTE Pj points to expanded storage (i.e., whether page J is backed by expanded storage). (Note that, in FIG. 7, neither page 1 701 nor page 2 702 is backed by expanded storage.) This determination is again made by examining the PTE (Page Table Entry) (FIG. 6): If the invalid indicator 63 is &#34;ON&#34;, and the non-main storage indicator 64 and the expanded storage indicator 66 are &#34;ON&#34;, then the page is backed by an expanded storage frame, whose address is in field 62. If there is expanded storage backing, the non-main storage indicator 64 and the indicator of expanded storage backing for page J 66 in the PTE are turned &#34;OFF&#34; 408 (indicating that the virtual page j is &#34;null&#34;--or &#34;freshly acquired&#34;; conventionally, a subsequent direct reference to such a page produces a page of zeroes) and virtual page K in the NMDS is backed 409 by this expanded storage (simply by turning ON the non-main storage indicator 64 and the expanded storage backing indicator 66 in the PTE for NMDS page Pk, and placing the address of this expanded storage page in field 62). 
     If Pj did not point to expanded storage 407, then a test 410 is made whether Pj points to auxiliary storage (i.e., flags 63, 64 and 67 are all ON): If not, then it is a &#34;null&#34; page that is being &#34;written&#34;--which can be accomplished simply by making the target NMDS page k also &#34;null&#34; 415 (by turning OFF the non-main storage backing indicator 64 in the associated PTE Pk); if the test 410 showed that Pj is backed by auxiliary storage, (as is the case for page 2 702 in FIG. 7). Then another test 411 is made to determine if the NMDS is a standard type, as indicated by the DSD indicator 309. If so, then the auxiliary storage backing 704 is removed 412 from the address space page 705, and associated 413 with the NMDS page 706 (by turning OFF the non-main storage indicator 64 and the auxiliary storage backing indicator 67 in the PTE associated with the address space page 705, and turning ON flags 64 and 67 in the PTE associated with the NMDS page 706, and placing the location of the auxiliary storage slot now backing the NMDS page in field 62 of the NMDS PTE). If test 411 indicates that the NMDS is an Expanded Storage Only type (indicator 308), then the request is rejected. (The application would then normally reference the address space page to bring it back into main storage and then repeat the request.) 
     If the test 406 showed that the address space virtual storage page is backed by main storage (as is the case with page J 701 in FIG. 7--its backing located at 703), then a test 420 is made whether the associated NMDS page 707 should be backed by expanded storage (or by auxiliary storage). This determination depends on (a) the type (standard or ESO) of the NMDS as indicated in the data space descriptor control block (FIG. 3 at 308, 309), and (b) the current system load on expanded storage. (For ESO-type NMDS&#39;s, always back with expanded storage; for standard NMDS&#39;s, an algorithm might be selected, for example, that backs with auxiliary storage if expanded storage is &#34;heavily used&#34;, according to some local option. This is not critical to the present invention.) 
     If the NMDS page is to be backed by auxiliary storage (only possible for standard-type NMDS&#39;s; as is the case with page K 707 in FIG. 7), then 421 the backing for the address space page is removed 708 and the page is set &#34;null&#34; (by turning ON the &#34;invalid&#34; indicator 63 and the non-main storage backing indicator 64 OFF in address space page J&#39;s PTE) initiating 422 an I/O operation from main storage page J 703 to auxiliary storage (ultimately resulting in the writing of the page to location 709, FIG. 7); and backing 423 NMDS page K 707 with auxiliary page 709 (by turning ON the non-main storage indicator 64 and the auxiliary storage backing indicator 67 in the PTE associated with NMDS page K, and placing the location of the auxiliary page 709 in PTE field 62). Note that the address space virtual storage is immediately available for reuse, even if the I/O has not completed. This is the case because the address space virtual page has been marked as &#34;null&#34; (i.e., freshly acquired), meaning that a reference to it will result in a page of zeroes. 
     If the test 420 showed that the NMDS page should be backed by expanded storage, then 424 an expanded storage frame is obtained conventionally, page J is conventionally copied 425 from main to the newly obtained expanded storage frame, and 426 virtual page K is backed with this expanded storage page by placing the address of the expanded storage page into the appropriate field 62 of the PTE associated with NMDS page K, and turning on the non-main storage indicator 64 and the &#34;expanded storage backing&#34; indicator 66 in this PTE. The process described is repeated for each page in the write request. 
     SREAD/CREAD 
     FIGS. 5A and 5B show the steps involved in a request by an application to read data from a NMDS to an address space. FIG. 8 illustrates a specific example of such a &#34;read&#34;--which will help explain the steps. In requesting the read, the application specifies: The number of contiguous pages to be read 501 (in the example of FIG. 8, this is 2); the virtual address of the starting page K in the NMDS to be read 502; the virtual address 503 of the starting page J in the address space A to receive the data; the STOKEN 504 of the NMDS being read from. 
     First, 506, the page table entry (PTE) Pk associated with virtual page K in the NMDS is located via the virtual address of page K 502 and STOKEN 504 as explained subsequently; and PTE Pj associated with page J in the address space is located via the virtual address of page J 503; the data space descriptor associated with the NMDS is located via the STOKEN 504. 
     Next, a test 507 is made whether the PTE Pk for NMDS page K points to expanded storage (i.e., whether backing page K is on expanded storage). If so (as is the case for page 1 801 in FIG. 8), a main storage frame 802 is obtained conventionally 508; the page is copied 509 from expanded storage 801 to main storage 802; virtual page J 803 is indicated 510 as &#34;backed&#34; by main storage (by placing the address of the real storage page in field 61 of PTE Pj); and by &#34;validating&#34; 511 the virtual page J (by turning OFF the &#34;invalid&#34; indicator 63 in PTE Pj for address space page J). 
     If Pk did not point to expanded storage 507, a test 515 is made whether page J is backed by auxiliary storage. If not, a further test 520 is made to verify that this is not an &#34;ESO&#34; type NMDS. (If it were, the request would be rejected, since this would indicate that the data in the ESO NMDS has been cast out of the space and is no longer available. (An ESO NMDS is treated like a cache and the data in it is not guaranteed to always be retrievable as is the case with a standard type.)). Being a standard NMDS, the address space page J is indicated as &#34;freshly acquired&#34;--or &#34;null&#34;, by turning ON the &#34;invalid&#34; indicator 63 and turning OFF the non-main storage indicator 64 in PTE Pj. Processing is then complete--a subsequent reference to a virtual address in this page resulting conventionally in a page of zeroes. 
     If page K is backed by auxiliary storage (as is the case for page 2 804 in FIG. 8), then a real (main) storage frame is conventionally obtained 516; page J in the address space is &#34;invalidated&#34; 517 (by turning ON the &#34;invalid&#34; indicator 63 in the associated PTE Pj) (Any references to this page prior to re-validation will, conventionally, result in suspension of the referencer until the page is re-validated); virtual page J is indicated 518 as being &#34;backed&#34; by the obtained main storage frame (by placing the address of the frame in the address space page J&#39;s PTE field 61; and an I/O operation is initiated 519 to read the page backing NMDS page K 804 into the obtained main storage frame 805. (When this I/O is complete 530, address space page J 806 is indicated 531 as being &#34;valid&#34; (by turning OFF the &#34;invalid&#34; indicator 63 in the associated PTE), and all applications suspended on a reference to page J are conventionally made dispatchable 532). The process described is repeated for each page in the read request. 
     Mapping a Page Table Entry to a Virtual Page 
     For clarity, though not essentially part of the present invention, the following explains the relation between a virtual address and a page table entry: 
     A conventional 31 bit virtual storage address 901 has the capacity to address any byte in a range of 0 to 2 gigabytes--1 inclusive. For a virtual system based on 2048 segments of 1 megabyte each where each segment consists of 256 4 K byte pages, the virtual address can be partitioned into a segment number of 11 bits 902, a page number of 8 bits 903, and a displacement of 12 bits 904. 
     Each virtual page in the 2 gigabytes addressing space is represented by a page table entry (PTE). All PTEs for the 2 gigabytes space are each of the same length and are arranged contiguously in virtual storage in ascending order of the virtual storage they represent 905. Hence, the first 256 PTEs represent the pages in segment 0 and together form the page table for segment 0 906. The second set of 256 PTEs form the page table for segment 1 907, and so forth. Together all page tables form the page table array 905. 
     Now, to identify any virtual byte within a system consisting of multiple 2 gigabytes addressing spaces requires that a virtual storage address be accompanied by identification (space location) of the 2 gigabytes space to which the virtual storage address applies. This may be an address space ID (ASID) for a 2 gigabytes address space or a STOKEN for a 2 gigabytes data space. In either case, the space locator 908 leads to one or more control blocks, collectively called here a &#34;space block&#34; 909. The &#34;space block&#34; contains a pointer 910 to the array of page tables representing the 2 gigabytes addressing range of the space. 
     Now, given the address, consisting of a space locator and a virtual storage address, of any virtual page in the system, the PTE representing the page containing that byte can be located. The space locator 908 leads to the start of the page table array 905. The segment number 902 forms an index 911 to the page table within the array and the page number 903 forms an index 912 to the PTE within the page table. 
     Hence, knowing the address of a virtual page is equivalent to knowing the address of its page table entry and vice versa. 
     While the invention has been shown and described with reference to a particular embodiment, it should be appreciated by those persons skilled in the art that changes and modifications may be made without departing from the spirit of the invention or the scope of the appended claims.