DFS2996E NOT ENOUGH DASD SPACE. ERROR REASON=X's99errorcode' [ SMS REASON=s99ersn ] BLOCKS=blocks BLKSIZE=blksize VOLUMES=volcount { UNIT=SYSALLDA | STORAGE CLASS=storageclassname } PART=partname DSN=dsname

Explanation

IMS tried to create the OSAM data set dsname for the HALDB partition partname as part of either:
  • Starting a HALDB OLR for the partition.
  • Loading the IMS catalog

The internally executed DYNALLOC macro instruction (SVC 99) that was used for this purpose reported that the data set could not be created because of DASD space or DASD volume constraints. The requested space was blocks blocks, each with a block size of blksize. There were volcount volumes requested.

If the text showing the group name (SYSALLDA) appears in the message text, the attempt was to create a non-SMS-managed data set because the corresponding input data set was not SMS-managed. If the text showing the storage class appears, then the attempt was to create an SMS-managed data set using storage class storageclassname because the corresponding input data set was SMS-managed and was created using that storage class.

If the reorganization was being started, these space allocation values were derived from the corresponding input data set.

For further information of this error, see the z/OS® MVS Programming: Authorized Assembler Services Guide (SA22-7608). The value s99errorcode is the hexadecimal value of the error reason code (field S99ERROR in the SVC 99 request block) that is provided when the DYNALLOC macro instruction (SVC 99) fails with return code 4. In the SMS case, s99ersn is the SMS reason code (field S99ERSN in the SVC 99 request block extension). The SMS reason code corresponds to the message number of an IGD message describing the error. For further information about the IGD message, see the z/OS MVS System Messages Vol 8 (IEF - IGD) (SA22-7638).

System action

If this error occurred in starting the reorganization, then the reorganization is not started, but the partition remains accessible with the original active set of data sets -- either the A-through-J and X or the M-through-V and Y data sets.

If this error occurred while loading the IMS catalog with the IMS Catalog Populate utility (DFS3PU00), the catalog is not loaded, message DFS4483E is written, and the utility ends with return code 12.

In any of these cases, if the data sets were to have been created automatically, one or more data sets might have been created before the error occurred.

Programmer response

Determine whether the requested space (blocks blocks of size blksize) is required for the output data set. In some cases, this space allocation request could include space acquired in a secondary allocation for the input data set and might not be required for the reorganized database. Then either:
  • Ensure that there is sufficient DASD space on the volumes referenced by the group name SYSALLDA (for the non-SMS-managed case) or referenced by the storage class storageclassname (for the SMS-managed case), possibly by scratching unneeded data sets. The primary allocation amount (blocks blocks of size blksize) must be available in a total of no more than five extents on a single volume. In the SMS-managed case, if the storage class definition includes the GUARANTEED SPACE attribute, then the primary allocation amount must be available and is allocated on each of the volumes (rather than on just the first volume).
  • Create and catalog this output data set yourself. In this case, you can reserve whatever amount of space you choose, and you can control the number of volumes. See Allocating OSAM data sets, for information about allocating OSAM data sets along with a technique for pre-allocating multi-volume data sets.

Then if the error was detected in processing the INITIATE OLREORG command, reissue the command for partition partname.

If this error occurred while running the DFS3PU00 utility to load the IMS catalog, rerun the utility.

Module

DFSORA20