An object language contains specifications for a particular language. It provides PowerDesigner with the syntax and guidelines for implementing stereotypes, data types, scripts and constants for an object language.
Each OOM is by default attached to an object language. When you create a new OOM, you must choose an object language. You can create a new object language or use the languages delivered with PowerDesigner.
The definition of an object language is available from its property sheet. You can select and configure parameters used when defining objects or generating from an OOM.
For more information on object languages, see "Resource File Reference" in the Resource Files and the Public Metamodel chapter of the Customizing and Extending PowerDesigner manual.
In an OOM, you can use the List of Object languages to display the properties of object languages, and to compare, or merge object languages.
For more information on using the list of object languages, see "Working with PowerDesigner Resource Files" in the Resource Files and the Public Metamodel chapter of the Customizing and Extending PowerDesigner manual.
Some resource files are delivered with "Not Certified" in their names. Sybase will perform all possible validation checks, however Sybase does not maintain specific environments to fully certify these resource files. Sybase will support the definition by accepting bug reports and will provide fixes as per standard policy, with the exception that there will be no final environmental validation of the fix. Users are invited to assist Sybase by testing fixes of the definition provided by Sybase and report any continuing inconsistencies.