FRD4416E 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
- Starting a HALDB OLR for the partition.
- Tracking these changes at the RSR tracking site.
If the text showing the group name (SYSALLDA) appears in the message text, IMS Database Recovery Facility attempted 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 an attempt was made 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 those of the corresponding input data set. On the RSR tracking site, these space allocation values were derived from those of the tracked output data set at the active site where the reorganization occurred.
For further information of this error, see the z/OS® MVS Programming: Authorized Assembler Services Guide. 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 on the IGD message, see the z/OS MVS System Messages, Vol 8.
System action
If this error occurred while 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 at the RSR tracking site, then the shadow partition is taken offline.
In either case, one or more of the output data sets might have already been created automatically.
User response
- Ensure that there is sufficient DASD space on the volumes referenced by the group name SYSALLDA (for non-SMS-managed) or referenced by the storage class storageclassname (for SMS-managed), possibly by scratching unneeded data sets. Note that 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. For SMS-managed data sets, if the storage class definition includes the GUARANTEED SPACE attribute, then the primary allocation amount must be available and will be 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 the IMS Administration Guide: Database Manager for information on allocating OSAM data sets and for a technique for pre-allocating multi-volume data sets.
INITIATE
OLREORG
command, reissue the command for partition partname.If
the error was detected at the RSR tracking site, issue a START
DB
command for the partition in order for Online Forward
Recovery to continue updating the partition.
Module
FRXIOCD0, FRXDDCD0