Conversion Utilities › Preconversion Data Validation Utility - CAL2DCVP › Issues Identified

Issues Identified

The Preconversion Data Validation utility identifies the following r11.3 data issues that can cause problems during the conversion process:

• Invalid dates and times

  Some columns in the CA Datacom/AD tables are defined as a data type that must contain a valid date, time, or both. If the r11.3 data contains invalid dates, times, or both, an error occurs during the import process. The row containing the invalid data is not included in the CA Datacom/AD database.

• Constraint violations

  Foreign keys constrain some columns in the CA Datacom/AD tables. That is, a constrained column in one table must match a key in another table for a successful import. Constraint violations cause errors during the import process and prevent rows from being included in the CA Datacom database. The following types of constraint issues are identified:

  • r11.3 record fields that correspond to a 'mini-table' foreign key but do not contain valid data.

    Note: During the installation process, constant data is imported into mini-tables. Mini-tables contain codes for use as foreign keys by other tables that are created from your CA 7 r11.3 database.

  • IDS data set and network names that do not have a matching data set/network name in the SASDS data set.
  • Jobs that have VRM resources defined but do not exist in the SASJOB data set.
  • Job directories and members that are out-of-sync with XP or agent definitions.
  • Unresolvable DSNBRs

    If the Conversion utility cannot determine the data set name associated with a DSNBR, the entry containing the unresolvable DSNBR is not included in the EXPORT file. That DSNBR is not included in the CA Datacom/AD database.

• Duplicates
  • Duplicate VRM Resource Count Resource Name Definitions

    Previous releases let a job have the same resource count resource name defined multiple times for the same schedule ID or for both zero and non-zero schedule IDs when the numeric component (/nnnn) was different.

    Note: Previous releases erroneously considered the numeric component of a resource count resource name (/nnnn) as part of the resource name. In Version 12.0, the numeric component is no longer part of the resource name.

    This release does not permit duplicate resource definitions. Duplicates are not included in the CA Datacom/AD database.

  • Duplicate DSNBR/SCHID Requirement Definitions

    In a previous release, CA 7 erroneously let you define multiple requirements with the same DSNBR/SCHID for a single job. This release does not permit duplicate requirement definitions. Duplicates are not included in the CA Datacom/AD database.

  • Duplicate unsatisfied requirements

    In previous releases, CA 7 let you add multiple temporary requirements for the same job or user requirement to a job in the request queue using the ADDRQ command. This release does not permit a job to have duplicate requirements. Duplicates are not included in the CA Datacom/AD database.

    Note: For more information, see the ADDRQ command in the Release Notes.