DFS2998E [ DATA SET CREATION ERROR. | UNALLOCATION FAILURE. ] RETURN=returncode [ { INFO. REASON=X's99infocode' | 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
As indicated by the message text, the internally executed DYNALLOC macro instruction (SVC 99) reported one of these two problems:
  1. The data set could not be created.
  2. The data set that was just created successfully could not be unallocated from the IMS job.

The requested space was blocks blocks, each with a block size of blksize. There were volcount volumes requested.

When the text showing the group name (SYSALLDA) appears in the message text, the attempt was to create a non-SMS-managed data set. If the text showing the storage class appears, then the attempt was to create an SMS-managed data set using storage class storageclassname.

If this error occurred during a HALDB online reorganization, the choice of creating an SMS-managed or non-SMS-managed data set is based on the corresponding input data set.

If this error occurred during the loading of an IMS catalog by the IMS Catalog Populate utility (DFS3PU00), then the choice of creating an SMS-managed or non-SMS-managed data set is based on the presence or absence of the STORCLAS parameter in the DFSDFxxx member that activated the IMS catalog.

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

In the message text:
returncode
Is the decimal value of the register 15 return code provided by the DYNALLOC macro instruction (SVC 99).
s99infocode
Is the hexadecimal value of the information reason code (field S99INFO in the SVC 99 request block).
s99errorcode
Is the hexadecimal value of the error reason code (field S99ERROR in the SVC 99 request block).
s99ersn
Is, for the SMS case, 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.

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 IMS catalog is not loaded, message DFS4483E is written, and the DFS3PU00 utility ends with return code 12.

In any of these cases, other data sets might have been created before the error occurred.

Programmer response

Determine the meaning of returncode, s99info, s99errorcode, and s99ersn, as applicable. Follow any recommended actions to correct the error.

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

If this error occurred while loading the IMS catalog with the DFS3PU00 utility, rerun the utility.

Module

DFSORA20