Can an installation limit the use of data spaces?

The use of data spaces consumes system resources such as expanded and auxiliary storage. Programmers responsible for tuning and maintaining MVS™ can set limits on the amount of virtual storage that programs in each address space can use for data spaces. They can limit:
  • The size of a single data space. (The default is 956K bytes, or 239 blocks.)
  • The amount of storage available per address space for all data spaces with a storage key of 8 - F. (The default is 2²⁴ - 1 megabytes, or 16777215 megabytes.)
  • The combined number of data spaces with storage key 8 - F that can exist per address space at one time. (The default is (2**32)-1 data spaces.)

You should know the limits your installation establishes and the return codes that you can check to learn why the DSPSERV macro might not create the data space you requested.

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Who owns a data space?

Although programs create data spaces, they do not own them. When a program creates the space, the...

How does a program move data into a data space?

One way to move data into a data space  is through buffers in the program's address space....

How does a program obtain a data space?

Data spaces and hiperspaces are created through the same system service: the DSPSERV macro. On...

What can a program do with a data space?

Programs can use data spaces and hiperspaces to: Obtain more virtual storage than a single...

How does a program manage the storage in a data space?

Managing storage in data spaces differs from managing storage in address spaces. Keep the...