DFS0843I dbname MAXIMUM NUMBER OF BYTES REACHED, DDNAME=ddname

Explanation

The data set group of an HDAM, HIDAM, PHDAM, or PHIDAM database has reached its maximum capacity.

For non-HALDB databases, the maximum size of a data set is:
  • If the data set is VSAM, 4 GB.
  • If the data set is OSAM, 4 GB for a data set with an odd-length block size and 8 GB for a data set with an even-length block size.

4,294,967,295 bytes (4 GB) is the largest absolute number for a fullword. A non-HALDB OSAM database with an even block size doubles the possible storage within a fullword to 8,589,834,591 bytes (8 GB).

For HALDB database partitions, the maximum size of a data set is:
  • If the data set is VSAM, 4 GB.
  • If the data set is OSAM, 4 GB or 8 GB.

System action

An attempt to obtain space is made by examining bitmaps. The search starts at the end of the data set and works up to the start. If this is unsuccessful, message DFS0844I is issued and the transaction terminates with pseudoabend 0844.

Programmer response

Reorganize the database to consolidate and reclaim space. If this does not work, consider taking one of the following actions:
  • For a HALDB database, split the partition into two or more partitions.
  • For a HALDB database that uses VSAM data sets or 4-GB OSAM data sets, consider using 8-GB OSAM data sets.

    To use 8-GB OSAM data sets, the HALDB database must be registered to DBRC as supporting 8-GB OSAM data sets. HALDB databases that use 8-GB OSAM data sets cannot be reorganized with the HALDB Online Reorganization (OLR) function

  • For a non-HALDB database, convert the database to HALDB.
  • For a non-HALDB database that uses VSAM data sets, change the database to use OSAM data sets with an even block size.
  • Use multiple data set groups.

Module

DFSGGSP0