Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Standard hiperspace z/OS MVS Programming: Extended Addressability Guide SA23-1394-00 |
|
Standard hiperspace is available to all programs. The data in a standard hiperspace is predictable; that is, your program can write data out to a standard hiperspace and count on retrieving it. The best way to describe how your program can scroll through a standard hiperspace is through an example. Figure 1 shows a hiperspace that has four scroll areas, A, B, C, and D. After the program issues an HSPSERV SREAD for hiperspace area A, it can make changes to the data in the buffer area in its address space. HSPSERV SWRITE then saves those changes. In a similar manner, the program can read, make changes, and save the data in areas B, C, and D. When the program reads area A again, it finds the same data that it wrote to the area in the previous HSPSERV SWRITE to that area. Figure 1. Example of scrolling through a standard hiperspace
A standard hiperspace gives your program an area where it can:
After you finish using the hiperspace, you can:
Standard hiperspaces can be non-shared and shared, depending on how you code the SHARE parameter
on DSPSERV.
You can extend the use of hiperspaces by supplying an ALET on the HSPSERV macro. To learn the differences between non-shared and shared standard hiperspaces and how you can extend their use, see Accessing hiperspaces. If your application wants to save a permanent copy of the data from a standard hiperspace, consider using the services of data-in-virtual. See Using data-in-virtual with standard hiperspaces. |
Copyright IBM Corporation 1990, 2014
|