Recovering from out-of-disk-space or extent limit problems

When a volume on which a data set is stored has insufficient space, or when the data set reaches its maximum size or its maximum number of VSAM extents, you can recover from this situation.

Symptoms

The symptoms vary based on the specific situation. The following messages and codes might be issued:

  • DSNP007I
  • DSNP001I
  • -904 SQL return code (SQLSTATE '57011')

Environment

For a demand request failure during restart, the object that is supported by the data set (an index space or a table space) is stopped with deferred restart pending. Otherwise, the state of the object remains unchanged.

Diagnosing the problem

Read the following descriptions of possible problems, and determine which problem you are experiencing.

  • Extend request failures: When an insert or update requires additional space, but the space is not available in the current table space or index space, Db2 issues the following message:
    DSNP007I - DSNPmmmm - EXTEND FAILED FOR
               data-set-name. RC=rrrrrrrr
               CONNECTION-ID=xxxxxxxx,
               CORRELATION-ID=yyyyyyyyyyyy
               LUWID-ID=logical-unit-of-work-id=token
  • Look-ahead warning: A look-ahead warning occurs when enough space is available for a few inserts or updates, but the index space or table space is almost full. On an insert or update at the end of a page set, Db2 determines whether the data set has enough available space. Db2 uses the following values in this space calculation:
    • The primary space quantity from the integrated catalog facility (ICF) catalog
    • The secondary space quantity from the ICF catalog
    • The allocation unit size
    If enough space does not exist, Db2 tries to extend the data set. If the extend request fails, Db2 issues the following message:
    DSNP001I - DSNPmmmm - data-set-name IS WITHIN
               nK BYTES OF AVAILABLE SPACE.
               RC=rrrrrrrr
               CONNECTION-ID=xxxxxxxx,
               CORRELATION-ID=yyyyyyyyyyyy
               LUWID-ID=logical-unit-of-work-id=token 

Resolving the problem

What you need to do depends on your particular circumstances.

  • In most cases, if the data set has not reached its maximum size, you can enlarge it. For the maximum sizes of data sets, see Limits in Db2 for z/OS.
  • If the data set has reached its maximum size, you need to follow the appropriate procedure, depending on the situation you face.