FRD4411E 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 Database Recovery Facility found one of the following situations:
  • A data set of that same name exists; however, because of certain characteristics of this pre-existing data set, that data set could not be used for your intended purpose.
  • No data set by that name was found when one should have existed previously.
Situation 1:
In starting a HALDB online reorganization for the HALDB partition partname, IMS Database Recovery Facility found that the data set that was to be used as the output of the reorganization had one of the following limitations:
  • It was not of a type that could used for this purpose.
  • It had certain characteristics that did not match those of the corresponding input data set.
  • It did not exist.
Situation 2:
On the RSR tracking site, IMS Database Recovery Facility found that in tracking database changes for a HALDB online reorganization for the HALDB partition partname, the data set that was to be used as the shadow of an output data set had one of the following limitations:
  • It was not of a type that could used for this purpose.
  • It had certain characteristics that did not match those of the corresponding input data set.
  • It did not exist.
In any case, reasoncode is a reason code the specific problem. These reason codes, environments, and explanations are shown in the following table. The Environment column indicates whether the error is detected at the beginning of the reorganization itself, the tracking of the reorganization at the RSR tracking site, or both.
Table 1. Reason Codes, Environments, and Errors Detected for Message FRD4411I
Rsn Code Environs Errors Detected for Pre-Existing Data Set
1 Both The data set is not a DASD data set.
2 Both The data set is a VSAM data set, but the database is defined to use OSAM.
3 Both The data set is a PDS, PDSE, or a member of a PDS or PDSE.
4 Both The data set is not a VSAM ESDS, but the database is defined to use VSAM.
5 Both The VSAM data set does not have the REUSE attribute.
6 Reorg. The VSAM data set has a different record length than that of the corresponding input data set.
7 Reorg. The VSAM data set has a different control interval size than that of the corresponding input data set.
8 Reorg. The VSAM ESDS has a different control interval size than that of the corresponding input data set.
10 Reorg. 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.
18 Both One of these situations exist:
  • The data set is cataloged but it is not on the volume to which the catalog entry refers.
  • 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 Both 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 defined for this partition's data sets.
20 Both 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.

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 both cases, one or more of the output data sets might have already been created automatically.

User response

Situation 1:
Before restarting the partition at the RSR tracking site, perform one of the following tasks:
  • Delete the pre-existing output data set to allow IMS Database Recovery Facility to create it automatically. When IMS Database Recovery Facility creates the data set, the size and placement of the data set is determined automatically by IMS Database Recovery Facility, MVS, DFSMS/MVS, and also by parameters defined by the storage administrator. Therefore, do not let IMS Database Recovery Facility create the data set if you need precise control over the size and placement of the data set.
  • Create a data set that is acceptable for tracking the output of the reorganization. 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) meets the following criteria:
    • A DASD data set.
    • Not a VSAM data set.
    • Neither a PDS, PDSE, or a member of a PDS or PDSE.
    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:
    • A VSAM entry-sequenced data set (ESDS).
    • The REUSE attribute.
    • The same fixed-length record length as the tracked output data set at the active site (as shown in the X'2930' log record).
    • The same control interval size as the tracked output data set at the active site (as shown in the X'2930' log record) or that for a PHIDAM database the output data set for the primary index (the X or Y data set) at the RSR tracking site has the following characteristics:
      • A VSAM key-sequenced data set (KSDS).
      • The REUSE attribute.
      • The same fixed-length record length as the tracked output data set at the active site (as shown in the X'2930' log record).
      • The same key offset and key length as the tracked output data set at the active site (as shown in the X'2930' log record).
Then issue a INITIATE OLREORG command to start the HALDB online reorganization for partition partname.
Situation 2:
Before restarting the partition at the RSR tracking site, perform one of the following tasks:
  • Delete the pre-existing output data set at the tracking site to allow IMS Database Recovery Facility to create it automatically. When IMS Database Recovery Facility creates the data set, the size and placement of the data set is determined automatically by IMS Database Recovery Facility, MVS, DFSMS/MVS, and also by parameters defined by the storage administrator. Therefore, do not let IMS Database Recovery Facility create the data set if you need precise control over the size and placement of the data set.
  • Create a data set that is acceptable for tracking the output of the reorganization. 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) at the RSR tracking site meets the following criteria:
    • It is a DASD data set.
    • It is not a VSAM data set.
    • It is neither a PDS, PDSE, nor a member of a PDS or PDSE.
    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) at the RSR tracking site has the following characteristics:
    • A VSAM entry-sequenced data set (ESDS).
    • The REUSE attribute.
    • The same fixed-length record length as the tracked output data set at the active site (as shown in the X'2930' log record).
    • The same control interval size as the tracked output data set at the active site (as shown in the X'2930' log record) or that for a PHIDAM database the output data set for the primary index (the X or Y data set) at the RSR tracking site has the following characteristics:
      • A VSAM key-sequenced data set (KSDS).
      • The REUSE attribute.
      • The same fixed-length record length as the tracked output data set at the active site (as shown in the X'2930' log record).
      • The same key offset and key length as the tracked output data set at the active site (as shown in the X'2930' log record).
Then issue a /START DB command for partition partname in order for Online Forward Recovery to continue updating the partition.

Module

FRXIOCR0, FRXDDCR0