DFS2991E UNACCEPTABLE DATA SET, REASON CODE reasoncode. PART=partname DSN=dsname

Explanation

In determining whether to create the data set dsname for the HALDB partition partname, IMS found either:
  • A data set of that same name. However, because of certain characteristics of this preexisting data set, the data set was not used for the intended purpose.
  • No data set of that name exists when there must be a data set preexisting.
Case 1:
When a HALDB online reorganization is starting for the HALDB partition partname, IMS determined the following conditions about the data set that was to be used as the output of the reorganization.
  • Whether the data set was of a type that can be used for the applicable data set.
  • Whether the data set has certain characteristics that do not match with those in the corresponding input data set.
  • Whether the data set exists.
Case 2:
When the IMS catalog is loading, the IMS Catalog Populate utility found that for the HALDB partition partname the data set that was to be used either:
  • Was not of a type that can be used for the applicable data set.
  • Has certain characteristics that do not match the requirements of the DBD of the IMS catalog.

In all of the preceding cases, reasoncode is a reason code for the specific problem.

The following table shows the definitions of the possible reason codes. In the table, the Environment column indicates whether the error is detected at the beginning of one or more of the following activities:
  • HALDB online reorganization
  • HALDB online reorganization with the ALTER option
  • The loading of an IMS catalog
Table 1. Reason codes, environments, and errors detected for message DFS2991I
Reason code Environment Errors detected for preexisting data set
1 Any The data set is not a DASD data set.
2 Any Either VSAM is incorrectly defined for an OSAM database, or the required LINEAR parameter is missing for the VSAM linear data set that is being used for the OSAM database.
3 Any The data set is a PDS, PDSE, or a member of a PDS or PDSE.
4 Tracking, Reorganization The data set is not a VSAM ESDS, but the database is defined to use VSAM.
5 Any The VSAM data set does not have the REUSE attribute.
6 Reorganization The VSAM data set has a different record length than that of the corresponding input data set.
7 Reorganization The VSAM data set has a different control interval size than that of the corresponding input data set.
8 Reorganization The VSAM ESDS has a different control interval size than that of the corresponding input data set.
9 Reorganization The data set is not a VSAM KSDS. The primary index data set of a PHIDAM database must be a VSAM KSDS.
10 Reorganization The primary index data set of a PHIDAM database (the KSDS), is defined with a different key offset or key length than that of the corresponding input data set.
11 Tracking The VSAM data set has a different record length than that of the tracked output data set at the active site.
12 Tracking The VSAM data set has a different control interval size than that of the tracked output data set at the active site.
13 Tracking The primary index data set of a PHIDAM database (the KSDS), is defined with a different key offset or key length than that of the tracked output data set at the active site.
15 Loading IMS catalog The VSAM KSDS has a different record length than what is required by the DBD that defines the IMS catalog.
17 Loading IMS catalog The VSAM KSDS is defined with a different key offset or key length than what is required by the DBD that defines the catalog.
18 Any Either:
  • The data set is cataloged but it is not on the volume to which the catalog entry refers.
or
  • The data set was allocated with a DD statement that had a VOLUME parameter, but the data set was not on the referenced volume.
19 Any The data set was allocated with a DD statement, but the data set name in the DSNAME parameter does not follow the data set naming convention that is defined for the data sets of this partition.
20 Tracking, Reorganization The output data set does not exist, but the corresponding input data set resides on multiple volumes and is not an SMS-managed data set.
22 Any An unexpected condition that involves the HSM-migrated data set occurred after it was recalled. This condition is likely caused by an internal error.
23 Reorganization with the ALTER option The VSAM data set has a different control interval size than what is specified for the data set in the ALTER BLOCK SIZE field of the partition record in the RECON data set.
24 Reorganization with the ALTER option The data set has a block or control interval size that is not large enough to hold the largest database segment that can be stored in this data set.

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

In any of these cases, one or more of the output data sets might be already created automatically.

Programmer response

Case 1:
Before you restart the HALDB online reorganization, do one of the following:
  • Delete the preexisting output data set, thus allowing IMS to create it automatically. When IMS creates the data set, the size and placement of the data set is determined automatically by IMS, MVS, and DFSMS/MVS, and also by parameters defined by your storage administrator. However, if you need precise control over the size and placement of the data set, you can create the data set manually and not let IMS create the data set automatically. Ensure that the preexisting data set matches the requirements of the output data set.
  • Create a data set that is acceptable as the output of the reorganization, which can be an OSAM Physical Sequential data set or VSAM Linear data set.

    Ensure that for an OSAM defined database the output data set for the database segments (one of the A-through-J or the M-through-V data sets) is a DASD data set.

    Ensure that for a VSAM defined database the output data set for the database segments (one of the A-through-J or the M-through-V data sets) has the following characteristics:
    • VSAM entry-sequenced data set (ESDS)
    • The REUSE attribute
    • A fixed-length record length identical to that of the input data set
    • A control interval size that is identical to that of the input data set
    Ensure that for a PHIDAM database the output data set for the primary index (the X or Y data set) has the following characteristics:
    • A VSAM key-sequenced data set (KSDS)
    • The same key offset, key length, and record length as the corresponding input data set
    • The REUSE attribute

Subsequently, reissue the INITIATE OLREORG command to start the HALDB online reorganization for partition partname.

Case 2:
Before you rerun the IMS Catalog Populate utility to load the IMS catalog, do one of the following:
  • Delete the preexisting output data set, thus allowing IMS to create it automatically. When IMS creates the data set, the size and placement of the data set is determined automatically by IMS, MVS, and DFSMS/MVS, by parameters in the DFSDFxxx member that activates the catalog, and also by parameters defined by your storage administrator. However, if you need precise control over the size and placement of the data set, you can create the data set manually and not let the IMS Catalog Populate utility create the data set automatically.
  • Create a data set that is acceptable as the output of the reorganization, which can be an OSAM Physical Sequential data set or VSAM Linear data set.

    Ensure that for an OSAM defined database the output data set for the database segments (one of the A-through-J or the M-through-V data sets) is a DASD data set.

    Ensure that for VSAM data set for the primary index, ILE data set, and secondary index has the following characteristics:
    • VSAM key-sequenced data set (KSDS).
    • The REUSE attribute
    • A fixed-length record length identical to that of the input data set
    • A control interval size that is identical to that of the input data set

Subsequently, rerun the IMS Catalog Populate utility to load the catalog.

Module

DFSORA00