SAS/Warehouse Administrator Metadata API- P59: The operating system and SAS version that are associated with a given host are now available through the WHHOST property. For example, you can write a SAS/Warehouse Administrator add-in that reads the host metadata that is associated with a given data store and then uses these values to generate code that is appropriate for the operating system and SAS version. | 287 Glossary application program interface API interpreter specifies a program that translates the metadata type that is requested by a client to the corresponding metadata object in a repository. business metadata represents text that describes the content or purpose of an application element. For example the business metadata for a SAS table might describe the purpose of the table and contact information for the person who is responsible for the accuracy of the information in the table. component indicates a set of related metadata types. Each component has an ID such as WHOUSE and a name such as SAS Warehouse Administrator that often matches the name of the application whose metadata is modeled by the component. WHOUSE is the component that is used for SAS Warehouse Administrator. contact records indicates a metadata record that specifies the owner or administrator who is responsible for a given warehouse element. An owner is a person who formulates policy and makes decisions about an object. An administrator is a person who implements decisions that are formulated by the owner in accordance with established policy. You can include contact records in the metadata for groups data stores processes jobs and other objects in the current environment. They are part of the global metadata for a warehouse environment. Although contact records are not required for code generation you might find them essential for project management. They enable you to identify and perhaps programmatically contact the people who are responsible for a given warehouse element. data file represents a metadata record that specifies a SAS file that is an input to an ODD. If you are defining an ODD whose Load Step is a DATA step view or an SQL view but not a Pass-Through view you must define its inputs in the Process Editor. Even if your ODD does not meet the conditions above you might still want to specify a process flow for this job for documentation purposes. You can define a data file that
