DSNP031I csect-name - CURRENT SPACE HAS nn EXTENTS FOR data-set-name. THE MAXIMUM EXTENTS IS mm. CONNECTION-ID=connection-identifier, CORRELATION-ID=-correlation-identifier, LUW-ID=logical-unit-of-work-id=token

Explanation

This message indicates that data set data-set-name has almost reached the maximum number of extents. The maximum number is indicated by mm. You cannot add more volumes if the current volume runs out of space.

The connection, correlation, and logical-unit-of-work IDs identify the user or application that encountered the problem. Correlation IDs beginning with 0nn (where nn is a number) identifies system agents.

A LUW-ID of an asterisk (*) indicates that the thread does not have a LUW-ID. If the LUW-ID is not an asterisk (*), the value is a logical-unit-of-work-id that is assigned to the thread followed by an equals sign (=) and a token value, which can be used in place of logical-unit-of-work-id in any Db2 command that accepts logical-unit-of-work-id as input.

Messages that have the same connection ID, correlation ID, and LUW-ID relate to the same user. Including all three pieces of information makes it possible to scan a number of DSNP-prefixed messages and group activities involving a given user.

System action

Db2 continues. If the table space or index space is not able to extend when needed, Message DSNP001I is issued and the current SQL request fails.

Operator response

For more information, issue an MVS WRITELOG operator command (for example, 'W A') to obtain MVS SYSLOG output. The SYSLOG sometimes contains VSAM or media manager messages that might be helpful in determining why space could not be allocated.

System programmer response

Based on the information that might be available in the access method services or VSAM messages preceding this one, try one of the following actions:
  • If you do not anticipate further extension of this table space or index, ignore the message.
  • If the table space or index is Db2-managed and has not yet reached the maximum number of extents, obtain an access method services LISTCAT for the named data set's to see how the extensions are distributed. Your options then include:
    • If there are multiple small extents, you can use the SQL statement ALTER TABLESPACE SECQTY to alter to a larger secondary space allocation quantity.
    • Otherwise, use the ALTER STOGROUP statement to add volumes to the storage group (up to 133 of them).
  • If the table space or index is user-managed and has not yet reached the maximum number of extents, issue the access method services command ALTER ADDVOLUMES to provide additional volumes (up to 59 of them).
  • If the data set is at the maximum number of extents, recover or reorganize the table space or index after taking one of the following actions:
    • Enlarge the primary or secondary space allocation quantity of the table space or index.
    • Convert the data set to SMS-managed with the Extent Constraint Removal option set to YES in the SMS data class. If you do this, the maximum number of extents is 7257.

      After the option is changed, the data set must be closed and re-opened to reflect this change. To reopen the data set, you can use the -STOP DATABASE and –START DATABASE commands, or run the REORG utility on the object.

Problem determination

Obtain an access method services LISTCAT for the named data set's VOLUME list for the extent space distribution.

See the Problem Determination section of message DSNP001I for more information.

Severity

0 (informational)