Main Icons for Metadata Objects in the Inventory Tree and Folders
Tree
|
|
|
|
|
Metadata for a Status
Handling action. SAS provides a number of actions, such as Skip
the Record and Send Email, that
can be performed when certain conditions are met during the execution
of a job. You cannot add or update actions.
|
|
|
Metadata for an XML
file containing ordered rules, conditional events, and analytical
models that can be deployed for execution to produce a decision.
|
|
|
Metadata for a Status
Handling conditions. SAS provides a number of conditions, such as Successful and Error
in Process, that can be tested for when jobs are executed.
You cannot add or update conditions.
|
|
|
Metadata for the default
Status Handling conditional action sets (conditions and actions).
You cannot add or update conditional action sets.
|
|
|
Metadata for a SAS cube,
a logical set of data that is organized and structured in a hierarchical,
multidimensional arrangement. A cube supports online analytical processing
(OLAP).
|
|
|
Metadata for an Enterprise
Decision Management flow, which used to structure the input data in
an Enterprise Decision Management transformation into output data.
|
|
|
Metadata for a job flow
used for scheduling. Job flows are maintained in SAS Management Console.
You cannot use SAS Data Integration Studio to add or update a deployed
flow.
|
|
|
Metadata for a file
that contains the code of a job that was deployed for scheduling.
The icon for the original job has a blue triangle overlay, which indicates
that the job has been deployed for scheduling.
|
|
|
Metadata for a dimension
that is used by multiple cubes.
|
|
|
Metadata for a document.
Many metadata objects have a Description attribute, which is limited
to 200 characters. A document can be used to supplement the Description.
Documents can contain graphics as well as text.
|
|
|
Metadata for an external
file. An external file is a file that is created and maintained by
a host operating system or by another vendor's software application.
A comma-delimited file is one example.
|
|
|
Metadata for a transformation
that is created with the Transformation Generator wizard.
The wizard helps you specify SAS code for the transformation.
|
|
|
Metadata for an Information
Map that is based on a SAS cube. Information Maps are created and
maintained in SAS Information Map Studio, and they can be used in
end-user applications. You cannot use SAS Data Integration Studio
to add or update an information map, but information maps are shown
in impact analysis.
|
Information map (Relational)
|
|
Metadata for an Information
Map that is based on one or more tables.
|
|
|
Metadata for a SAS Data
Integration Studio job. A job is collection of SAS tasks that create
output.
|
|
|
Metadata for a read-only
job that creates a SAS cube.
|
|
|
Metadata for a library.
In SAS software, a library is a collection of one or more files that
are recognized by SAS and that are referenced and stored as a unit.
|
|
|
Metadata for a message
queue. A message queue is a place where one program can send messages
to be retrieved by another program.
|
|
|
Metadata for the output
of a Mining Results transformation.
|
|
|
Metadata for a note.
Many metadata objects have a Description attribute, which is limited
to 200 characters. A note can be used to supplement the Description.
Notes can contain text only.
|
|
|
Metadata for an OLAP
schema. In general, do not add or update OLAP Schemas in SAS Data
Integration Studio.
|
|
|
Metadata for prompts.
In general, do not add or update prompts in SAS Data Integration Studio.
|
|
|
Metadata for prompt
groups. In general, do not add or update prompt groups in SAS Data
Integration Studio.
|
|
|
Metadata for saved searches
that you can initiate from the Tools menu
and save for future use.
|
|
|
Metadata for a stored
process that was generated from a SAS Data Integration Studio job.
Enables users to execute SAS Data Integration Studio jobs from applications
such as SAS Enterprise Guide or a web service client.
|
|
|
|
|
|
Metadata for generated
web services.
|