DSNP001I csect-name - data-set-name IS WITHIN n BYTES OF AVAILABLE SPACE. RC=reason-code CONNECTION-ID=connection-identifier, CORRELATION-ID=correlation-identifier, LUW-ID=logical-unit-of-work-id=token

Explanation

This message warns of an impending space shortage. The data space manager (DSM) extend function CSECT 'DSNPmmmm' detected the space shortage through the use of a 'hedge' quantity n. Reason code reason-code gives some information about why space could not be obtained.

There might also be some preceding DSM and VSAM messages that can help to determine why space cannot be obtained. The connection, correlation, and logical-unit-of-work IDs identify the user or application that encountered the problem. Correlation IDs beginning with '0nn', where nnis a number, identify 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 identifier 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. This makes it possible to scan a number of DSNP-prefixed messages and group activities involving a given user.

System action

If sufficient space is available for the current request, continue. Otherwise, message DSNP007I follows, and the current SQL request fails.

Operator response

DSM messages are directed to the database administrator (DBA) or system administrator. However, the DBA or system administrator can request that the operator issue an MVS™ WRITELOG operator command (for example, 'W A') to obtain MVS SYSLOG output. The SYSLOG sometimes contains media manager messages that might be helpful to the DBA or system administrator in determining why space could not be allocated.

System programmer response

Based on the reason code (RC) in the message, as well as information that might be available in access method services or VSAM messages preceding this one, try one of the following solutions:
  • 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 storage group-defined data sets and this data set is not at maximum extents, use the ALTER STOGROUP statement to add volumes to the storage group (up to 133 of them).
  • If the table space or index is backed by 'user-defined' data sets, and not at maximum extents for the data set, issue an ALTER ADDVOLUMES access method services command to provide additional volumes (up to 133 of them). Or, if the table space is nonpartitioned and the high allocated RBA is greater than or equal to 2GB (2,147,483,648) for the indicated data set, define the data set required for the next sequential piece. (Actually, in this case, there should be an indication in console messages or the reason code that the data set required for the next piece was not found.)
  • 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.
  • If all of the following conditions are true, the maximum number of extents is 7257:
    • The data set is SMS-managed
    • The Extent Constraint Removal option is set to YES in the associated SMS data class
  • If any of the conditions outlined in the previous bullet are not true, the maximum number of extents is:
    • 251 to 255 for non-striped data sets
    • 251 to 255 for each stripe for striped data sets

Problem determination

Examine the console messages, SYS1.LOGREC information, and SYSLOG to determine the reason for the condition. Try to resolve it by the methods described in the Operator Response section of this message. If you feel that this message indicates a problem in an IBM® program, you should provide the following sources of information about the problem:
  • Console sheet showing the message and related messages that might precede or follow it.
  • System log printout (obtained via MVS WRITELOG operator command) showing related VSAM/media manager messages that might appear there (usually needed only if you have a message or reason code that indicates a media manager services problem occurred).
  • Integrated catalog facility (ICF) catalog listing showing characteristics of the data set in question and of the ICF catalog itself.
  • VTOC listing of packs associated with the request, showing space available for data sets, catalogs, VTOC index, and the VTOC itself, as well as data set extent information.
  • Any associated dumps.
  • SYS1.LOGREC listing showing entries at or near the time of the problem (unless these appear in an associated dump).
  • Depending on the reason code, the results of certain SQL SELECT operations on Db2 catalog tables may be needed.