Database Package Sub-Object Checks (PDM)

PowerDesigner provides default model checks to verify the validity of database package cursors, exceptions, procedures, types, and variables.

Check	Description and Correction
Name/Code contains terms not in glossary	[if glossary enabled] Names and codes must contain only approved terms drawn from the glossary. Manual correction - Modify the name or code to contain only glossary terms. Automatic correction - None.
Name/Code contains synonyms of glossary terms	[if glossary enabled] Names and codes must not contain synonyms of glossary terms. Manual correction - Modify the name or code to contain only glossary terms. Automatic correction - Replaces synonyms with their associated glossary terms.
Name/Code uniqueness	Object names must be unique in the namespace. Manual correction - Modify the duplicate name or code. Automatic correction - Appends a number to the duplicate name or code.
Package `sub-object` definition empty	[cursors, procedures, types] These sub-objects must have a definition. Manual correction: Create the definition in the Definition tab of the sub-object's property sheet Automatic correction: None
Check for undefined return types	[cursors, procedures] These sub-objects must have a return data type. Manual correction: Select a return data type in the subobject's property sheet Automatic correction: None
Existence of parameter	[cursors, procedures] These sub-objects must contain parameters for input values. Manual correction: Create one or several parameters in the Parameters tab of the sub-object's property sheet Automatic correction: None
Undefined data type	[variables] Variables must have a data type. Manual correction: Select a data type in the variable property sheet Automatic correction: None