Skip to Content

EXONLY keyword

Use the EXONLY keyword to print all available reports.

You would most likely run the DBD Audit report when you want to verify that required elements have been defined or you are searching for inconsistencies in these definitions. By default, Database Integrity prints reports only for the DBDs for which it found an exception condition. If you are running the DBDAUDIT function to document your environment, you can use the EXONLY keyword to tell Database Integrity to report on all DBDs found in the DBD library, the ACB library, and the MODBLKS library, regardless of whether the DBD has an exception condition.

Related topic

Coding control statement keywords

Similarly, when comparing control blocks, you can use the EXONLY keyword to print or suppress the Compare report depending on whether differences were found between the two control blocks.

Attribute

Description

Uses

The EXONLY keyword is optional on the following statements:

  • COMPARE
  • DBDAUDIT

It is not valid on the other control statements.

Syntax

EXONLY(y/n)

Values

Code one of the following values:

YES or Y

Print only the exception conditions (DBDAUDIT). Print the Compare report only if differences are detected (COMPARE).

NO or N

Print all DBDs from all sources (DBDAUDIT). Always print the Compare report (COMPARE).

Default

EXONLY(YES)

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Database Integrity for IMS 5.2