Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
An example of a hiperspace as a data-in-virtual object z/OS MVS Programming: Extended Addressability Guide SA23-1394-00 |
|
The program in this section creates a non-shared standard hiperspace for temporary storage of a table of 4K bytes that the program generates and uses. The program cannot save this table permanently. The following code creates a non-shared standard hiperspace and identifies it as a data-in-virtual
object.
When the hiperspace is a data-in-virtual object, your program does not need to know the origin of the hiperspace. All addresses refer to offsets within the hiperspace. Note that the example does not have the ORIGIN parameter on DSPSERV. After you finish making changes to the data in the address space
window, you can save the changes back to the hiperspace as follows:
The following macro refreshes the address space window. This means
that if you make changes in the window and want a fresh copy of the
object (that is, the copy that was saved last with the DIV SAVE macro),
you would issue the following:
When you finish using the hiperspace, use the DSPSERV macro to
delete the hiperspace.
|
Copyright IBM Corporation 1990, 2014
|