Tying your metadata to your other information

Managing SAS® v9 applications means using information of different nature and origin. The applications in this context are both ETL processes and the creation of OLAP cubes and Information Maps to surface the information for the end user. Examples of types of information are the following. 1. Requirements for an application, technical architecture, technical draft, implementation issues, etc. This is mainly textual information, which can be in any form. 2. The metadata as it is being produced through the different clients: SAS® Management Console, the SAS® Data Integration Studio, SAS® OLAP Cube Studio, etc. This is all stored in the SAS Metadata architecture. 3. Status information and logging of the scheduled processes. Standard this information is partly available in the scheduler (like LSF) and optionally as log files. In this presentation a set of guidelines will be described together with some SAS macro code developed to be used in the job status options of DI Studio. Together with the right settings this will tie the information together. For example, this will make it possible to jump from the properties of a job in DI Studio to the documentation on the process, or to the log file of the last run of that job. And when browsing the metadata one will see among the attributes of a job also the return code and the date time stamp of the last run.