Restrictions and considerations for the DBD/PSB/ACB Compare utility

Certain restrictions and considerations apply when you use the DBD/PSB/ACB Compare utility.

The DBD/PSB/ACB Compare utility compares the DBD/PSB fields even if they are not used for some IMS™ versions and releases.

The DBD/PSB/ACB Compare utility supports only the ACBs generated by IMS of the same version and release when generating block-level compare reports.

When the DBD/PSB/ACB Compare utility compares DBD-type ACBs for a DEDB to generate a source-level compare report, the utility also uses the PSB-type ACB that references the DBD to obtain the DBD VERSION= parameter value. If a problem occurs when reading the PSB-type ACB, the DBD VERSION= parameter value is not compared.

When the DBD/PSB/ACB Compare utility compares a PSB that was generated by IMS Version 2 Release 2, the name of the PCB is not compared even if the name is defined.

When you compare ACBs by using a source-level compare report, the following restrictions apply. These restrictions are the same as the restrictions for the DBD/PSB/ACB Reversal utility.

Because the DBD/PSB/ACB Compare utility cannot obtain segment name information and database name information of the SOURCE parameter for virtually paired logical relationship, the program does not compare these names.
Because the DBD/PSB/ACB Compare utility cannot obtain information about the INDICES parameter of the SENSEG statement, the program does not compare the fields of the parameter.
Because the DBD/PSB/ACB Compare utility cannot obtain label information of the DATASET statement, the program does not compare the label fields.

When you compare ACBs with DBDs, the following restrictions apply:

The DBD/PSB/ACB Compare utility compares only parameters that exist in ACB libraries. When the utility compares DBD-type ACBs with DBDs, it ignores the parameters that exist only in DBD libraries. For information about parameters that are not contained in ACB libraries, see Restrictions on the generated control statements.
If the index target segment type that the XDFLD statement specifies is assumed to be the index source segment, the program does not compare the SEGMENT parameter.

The NODIFF option, which generates compare reports even when no difference is found, is supported only for source-level compare reports.

For the restrictions that apply to the generated control statements, see Restrictions on the generated control statements.