DSNP030I csect-name THE CURRENT EXTENT REACHES THE LAST VOLUME FOR data-set-name. CONNECTION-ID=xxxxxxxx, CORRELATION-ID=yyyyyyyyyyyy, LUW-ID=logical-unit-of-work-id=token

Explanation

This message indicates that the last volume to which the data set data-set-name can extend has been reached. 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, identify system agents.

A LUW-ID of '*' indicates that the thread does not have a LUW-ID. If the LUW-ID is not an '*', the value is a logical-unit-of-work-id that is assigned to the thread followed by an '=' 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. This makes it possible to scan a number of DSNP-prefixed messages and group activities involving a given user.

System action

If sufficient space in current volume is available for the current request, Db2 continues. Otherwise, message DSNP007I 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

Depending on what information is available in the access method services or VSAM messages preceding this one, try one of the following:
  • If you do not anticipate further extension of this table space or index, ignore the message.
  • If the table space or index is backed by SMS-managed data sets, use LISTCAT to choose another SMS storage group that has more space available and recover or reorganize the table space or index into the new SMS storage group.
  • If the table space or index is Db2-managed but is not SMS-managed, rearrange the Db2 storage group volume list by shifting volumes with free space or by adding new volumes. Use the SQL statements ALTER STOGROUP ADD VOLUMES and ALTER STOGROUP REMOVE VOLUMES and then recover or reorganize the table space or index.
  • If the table space or index is user-managed and not SMS-managed, delete and redefine the data set with more space and then recover or reorganize the table space or index.

Problem determination

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

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

Severity

0 (informational)