- Access Control Domain
- The
Access Control Domain (ACD) is a security definition that serves as
the foundation for all levels of Optim™ Security.
Each Optim Directory for which Optim Security is initialized contains
an ACD named (Default) that cannot be deleted. Depending upon
the needs of your facility, you may create additional ACDs or use
only the (Default) ACD. Each ACD includes a list of roles.
Each role represents a logical grouping of user and group accounts
in your network.
- Access Control List
- The
Access Control List (ACL) is an Optim object
that serves as the basis for Object Security. ACL parameters govern
the ability of a role to perform actions (such as read, update, or
delete) on both the object and the ACL for the object. Each ACD, File
Access Definition, and secured Optim object
has a unique ACL.
- Access Definition
- An Access Definition identifies the Start Table,
related tables, relationships, and selection criteria that define
the data you want to Archive, Extract, Edit, or Compare. You can save
and reuse Access Definitions, which are stored in the Optim Directory.
- Access Definition Name
- An Access Definition name has two parts: identifier.name
- identifier
- (1 to 8 characters)
- name
- (1 to 12 characters)
- Age Function
- The Age Function is used in a Column Map to age
a source column value before inserting that value at a destination.
The Age Function is formatted as: AGE(parameters)
For details on using the Age Function in a Column Map,
refer to Data Privacy Functions in Column Maps.
- Archive
- Archive enhances database performance by
facilitating the removal of infrequently referenced data. This tool
allows you to identify and archive sets of relationally intact data
before removing selected data from your database. Archived data is
indexed and stored. Using Archive, you can browse, search,
or restore selected subsets of archived data.
- Archive Action
- Archive Actions are supplemental SQL statements
stored in the Table Specifications of an Access Definition that are
to be executed at a selected phase of an Archive, Delete, or Restore
Process.
For example, you might use this feature
to audit deleted rows by executing an appropriate SQL statement before
the start of an Archive Delete Process, or after the deletion of each
row.
- Archive Directory
- A database table in the Optim Directory. When an Archive File is created,
an entry is created in the Archive Directory that is used to identify
and locate the Archive File and any associated indexes.
- Archive Directory Maintenance
- A utility that creates, updates, or deletes Archive
Directory entries, and creates new or modifies existing Archive File
indexes. You can also use it to browse an Archive File, or the Access
Definition used to create an Archive File.
- Archive File
- An Archive File contains the selected, relationally
intact data described in the Access Definition, and the object definitions
needed to recreate the database, if necessary. Archive Files have
a default .af extension and are stored in the Archive Directory specified
in Personal Options.
You can browse or selectively
restore the data in an Archive File at any time. You can share and
use an Archive File as often as needed.
- Archive File Security
- Archive File Security allows you to control access
to data in Archive Files. For example, you might use Archive File
Security to prevent any access to data in a specific table or column
for most users while granting access to members of selected roles
for the same data. Each secured Archive File is associated with a
File Access Definition (FAD), which is a security definition that
lists tables and columns for which access privileges are defined and,
for each listed role, grants or denies privileges to access the archived
data.
- Archive Index File
- An Archive Index File stores index information for
a corresponding Archive File. The Archive Index File facilitates the
searching, browsing, and restoring of archived data. The default extension
for Archive Index Files is .axf.
- Archive Process
- An Archive Process copies a set of related rows
from one or more tables and stores this data in an Archive File. Initiate
the Archive Process with an Archive Request that specifies an Access
Definition for the data to be extracted and other process parameters,
such as delete options.
- Archive Request
- An Archive Request defines the parameters for archiving
and (if desired) deleting data from source tables, and saving that
data to an Archive File. An Archive Request references an Access Definition
to define the data to archive and the parameters needed to run the
Archive Process.
Use the Archive Request Editor to
specify an Archive File, an Archive Index File, and a named or local
Access Definition. Also, select explicit database objects to extract,
override Point and Shoot List parameters, provide values for Variables
specified in the Access Definition, and specify Delete options.
You can save and reuse Archive Requests stored in the Optim Directory.
- Boolean Constant
- A Boolean constant specifies a TRUE or FALSE value.
Use a Boolean constant to specify the value of a Boolean column in
a Column Map or Relationship.
- Browse Utility
- The Browse Utility allows you to review the contents
of an Archive, Extract, Compare, or Control File. Use the Browse Utility
to:
- Verify the contents of a file.
- Identify discarded rows and review diagnostic information
in a Control File, when errors occur during a Convert, Delete, Insert,
or Load Process.
- Calendar
- A calendar consists of general options for adjusting
and formatting dates and weekend days, dates that have significant
meaning for your site (e.g., holidays), and rules to resolve differences
when an aged date occurs on a special day.
- Calendar Utility
- The Calendar Utility allows you to define the calendar
year, dates, and business rules to use for date aging and process
scheduling. Use date aging when you Convert, Insert, or Load data. Optim includes
sample calendars and business rules.
- Child Expression
- A child expression is a list of columns in the child
table that relate to corresponding columns in the parent table. You
can accept, modify, or replace these column names.
- Column Map
- A Column Map defines the specifications for mapping
columns of compatible data between source and destination tables.
You can map unlike-named columns, modify data, or exclude columns
from a process. You can include one or more Column Maps in a Table
Map when you create a request to Compare, Convert, Insert, Load, or
Restore data.
When you define a Column Map, you can
specify the source column value as an explicit column name, NULL,
constant (numeric or Boolean), special register, literal (string,
hexadecimal, or date/time), function (Substring, Random, Sequential,
Age, or Currency), expression (concatenated or numeric), or exit routine.
- Column Map Procedure
- A Column Map Procedure is a custom program that
is referenced by a Column Map and is used for special processing and
data manipulation that is beyond the scope of native Column Maps.
- Compare
- Compare facilitates comparisons of sets of
relationally intact data. Using Compare, you can compare data
resulting from application tests to the original data with all differences
highlighted, allowing you to rapidly analyze the effects of your application
software or modifications to it.
- Compare File
- A Compare File contains the results of the Compare
Process, including details about changes, matched and unmatched rows,
and non-unique values. You can browse the contents of a Compare File.
Compare Files have a .cmp extension and are stored in the Data Directory
specified in Personal Options.
- Compare Process
- The Compare Process retrieves the data from Source
1 and Source 2 specified in the Compare Request, compares the rows
in each pair of tables, identifies the differences between the two
versions of data, and records the results in the Compare File.
Initiate the Compare Process with a Compare Request.
The Compare Process uses the Primary Key or a user‑defined Match Key
to identify rows to compare from Source 1 and Source 2. You can use
the Browse Utility to review the results in the Compare File.
- Compare Request
- A Compare Request specifies the data to compare
(Source 1 and Source 2) and the parameters for the Compare Process.
Use the Compare Request Editor to specify the comparison mode and
the data sources:
- In Single Table mode, you can compare one table
to another. The source tables can come from an Extract File or the
database, and you can specify a Column Map to focus on data in specific
columns.
- In Multiple Tables mode, you can compare two sets
of tables. The source tables can come from an Extract File, an Access
Definition, or include all tables in the database. You can specify
a Table Map to focus on specific data.
You can save and reuse Compare Requests stored
in the Optim Directory.
- Composite Columns
- A composite column contains data that corresponds
to similar data stored in two or more columns in another table. You
can relate data in composite columns using a concatenated expression
or the Substring Function.
- Concatenated Expression
- A concatenated expression combines column values
or combines a column value with another value, using a concatenation
operator (CONCAT, ||, or +), when you define a Column Map or relationship:
- A Character Concatenated Expression consists
of one or more character columns, string literals, or substrings of
character columns.
- A Binary Concatenated Expression consists
of one or more binary columns, hexadecimal literals, or substrings
of binary columns.
Note: A concatenated expression cannot include a zero-length
string literal (‘ ‘), a special register, or the Age Function.
- Configuration Program
- The Configuration program allows you to prepare
your system and workstations to use Optim. You
can start this program immediately following installation, or you
can select the Configuration icon on your desk top. For details on
using this program, see the Installation and Configuration Guide .
- Connection String
- A connection string permits a workstation to access
a particular database. The DBMS uses this connection string to recognize
the database. The database administrator specifies this connection
string when configuring Optim.
- Control File
- A Control File records process specifications and
the success or failure of processing. A Control File is generated
automatically during Convert, Delete, Insert, or Load Processing,
or if you run an Archive Request that deletes rows after they are
archived. The Control File provides details on discarded rows and
may provide diagnostic information. Specify the name of a Control
File when you create a process request. Use the Browse Utility to
review the contents of a Control File, which have a .cf extension.
- Convert Process
- The Convert Process transforms the contents of an
Extract File before you perform an Insert or Load. This process is
useful to mask sensitive data or to prepare data for download to another
platform. Use a Convert Request to initiate the Convert Process and
specify the Source File and other process parameters.
- Convert Request
- A Convert Request identifies the Extract File containing
the data to convert and the parameters needed to run the Convert Process.
Use the Convert Request Editor to specify a Source File, a destination
file to store the converted data, and a Control File to store processing
information. You can also specify Table Map options, a Discard Row
Limit, and options for date aging, currency conversion, and reporting.
You can save and reuse Convert Requests stored in the Optim Directory.
- Create Utility
- The Create Utility allows you to copy object definitions
extracted from one database and create like-defined objects in the
same or a different database.
Use the Create Utility
to clone a production database or create a test database that contains
tables identical to those in a production database. You can also create
objects within the same database, if you define new names for those
objects.
- Currency Definition
- A Currency Definition contains the following:
- General parameters for currency calculations and
display options for currency codes.
- Date ranges and conversion rates for currency calculations.
- Lookup tables to correlate database currency codes
with standard and user-defined currency codes.
You can specify a Currency Definition when
you use the Currency Function in a Column Map or when you create a
Convert, Insert, or Load Process request.
- Currency Function
- The Currency Function is used in Column Maps to
convert a source currency to another type of currency, based on a
specified conversion rate, before inserting the result at a destination.
Format the Currency Function as: CURRENCY(parameters).
For details on using the Currency Function in a Column Map, see Currency Function.
- Currency Utility
- The Currency Utility allows you to create and maintain
Currency Definitions, which specify the types of currencies, conversion
rates, and optional look-up tables for conditional currencies. Optim includes
lists of currencies and sample rates.
- Data-Driven Relationship
- In a data-driven relationship, the parent table
is related to one of several child tables, based on data in a particular
column. Define a data-driven relationship using string literals, hexadecimal
literals, numeric constants, Boolean constants, or NULL.
- Date/Time Literal
- A date/time literal specifies a value for a date
or date/time column in a Column Map. Optim uses
the time and short date formats defined for Windows 95/NT, and enclose the date/time
literal in single quotes.
Note: To check your workstation format,
select Regional Options from the Control Panel
and review the Date and Time tabs.
- DB Alias
- A DB Alias is a set of specifications that allows Optim to identify,
locate, and access a particular database. The DB Alias also qualifies
the names of objects referenced, defined, or accessed using Optim. The
specifications for defining a DB Alias are usually provided by the
database administrator.
- Default Qualifier
- A Default Qualifier is the prefix for unqualified
table names: dbalias.creatorid.
- dbalias
- Alias for the database where a table is defined
(1 to 12 characters).
- creatorid
- Identifier assigned to the table (1 to 64 characters).
(Use Creator ID for DB2®, Schema
for Oracle, and Owner ID for Sybase ASE and SQL Server.)
- Delete Process
- The Delete Process removes sets of related data
from a database after an Extract, Archive, or other process, based
on the contents of a Source File (either an Extract or Archive File).
Use a Delete Request to initiate the Delete Process. The Source File
is not changed during the Delete Process; you can use it again to
restore the deleted data.
- Delete Request
- A Delete Request identifies an Extract or Archive
File as the Source File containing the data you want to delete, and
specifies the parameters for the Delete Process. Use the Delete Request
Editor to specify the Source (Extract or Archive) File, a Control
File, and the process options, including the commit frequency, discard
row limit, and whether to lock tables during the process. You can
save and reuse Delete Requests stored in the Optim Directory.
- Destination Format Exit
- A Destination Format Exit ages dates based on a
destination exit routine. This exit routine is called to format the
destination column in an Age Function that would otherwise not be
supported in a Column Map. This exit routine converts a date into
one of four different destination formats, determined by the data
type of the destination column.
You specify this
exit in a Column Map source column as: AGE(DSTEXIT=dllname),
where DSTEXIT is the name of the Destination Format Exit.
- Discarded Rows
- Rows that cannot be processed successfully are marked
as discarded and written to a Control File. When the process terminates,
you can browse the Control File to view discarded rows and diagnostic
information.
You can specify a Discard Row Limit
in any request to Archive, Convert, Delete, Insert, or Load data.
This limit terminates the process to prevent accumulating a large
number of discarded rows.
- Edit
- Edit is used to browse and edit sets of relationally
intact data in database tables. Using Edit, you can edit database
data, review logical application paths, and browse data to ensure
that application test results are as expected. Edit supports
your rapid development of applications, allows you to analyze the
structure of your database, and facilitates your browsing of precisely
defined segments of relational data.
- Edit Definition
- An Edit Definition stores specifications for browsing
and editing a set of related data in the Table Editor. An Edit Definition
includes:
- Table names, specifications, and selection criteria
in a named or local Access Definition.
- Edit preferences, joined tables, and grid options
that define the current state of the Table Editor.
An Edit Definition allows you to save the current
state of the Table Editor and reopen the Editor using the same specifications.
You can save and reuse Edit Definitions stored in the Optim Directory.
- Exception Table
- An exception table contains copies of rows that
violate unique index or primary key rules during a Load Process, and
includes a timestamp and a description of the violation. The DBMS
Loader creates an exception table for every source table.
Use the Load Request Editor to select options for creating
exception tables. To avoid duplicating or overwriting table names,
you can view and specify the names for exception tables in the Load
Request.
- Exit Routine
- An Exit Routine is a set of instructions written
outside of Optim.
You may specify an exit routine as the source or use it within the
Age Function to define a column value. Exit routines are useful when
you want to use special processing, manipulate data, or include string
literals that exceed the total length of the selected source column.
For details on exit routines, see Exit Routines for Column Maps.
- Explicit Column Name
- An explicit column name can be used to specify a
column value in a Column Map. Column names are case-sensitive in Optim.
Note: When
you define a relationship, either the parent or the child column must
be an explicit column name.
- Explicit Relationship
- An explicit relationship is a relationship that
can be used by a single pair of related tables. The parent and child
tables used to define an explicit relationship must have the same
Creator ID. Use the Relationship Editor to create an explicit relationship
stored in the Optim Directory,
or to convert an explicit relationship to a generic relationship.
- Export Utility
- The Export Utility allows you to copy selected Optim object definitions from a
specified Optim Directory to
an external file. This utility is useful for moving Optim objects from one Optim Directory to another. After exporting
the data, use the Import Utility to copy the exported object definitions
into the destination Optim Directory.
- Extract File
- An Extract File contains a set of related rows extracted
from one or more tables, saved in proprietary format. An Extract File
can contain data, object definitions, or both. Extract Files have
a default extension of .xf and are stored in the Data Directory specified
in Personal Options.
You can browse the contents
of an Extract File, and can share and use an Extract File as often
as needed.
- Extract Process
- The Extract Process copies a set of related rows
from one or more tables and stores this data in an Extract File. The
Extract Process always includes the definitions for tables and columns.
You can also choose to extract object definitions, including primary
keys, relationships, and indexes.
Initiate the Extract
Process with an Extract Request that specifies an Access Definition
for the data to be extracted and other process parameters.
- Extract Request
- An Extract Request specifies an Access Definition
to define the data to extract and the parameters needed to run the
Extract Process. The Extract Request Editor prompts you to:
- Specify the name of an Extract File and a named
or local Access Definition.
- Choose to extract data, objects, or both. If applicable,
specify object definitions to extract.
- Choose to override the Point and Shoot List or Variables
specified in the Access Definition.
You can save and reuse Extract Requests stored
in the Optim Directory.
- Fast Load
- The Fast Load feature significantly reduces processing
time when you rerun a Load Request. When a Load Request completes
processing, Optim maintains
information about the processing parameters and specifications. When
you rerun the same Load Request, a confirmation dialog prompts you
to confirm whether to use Fast Load Processing.
- Fetch Set
- A fetch set is a set of rows that Optim reads
from the database for each table or view in the Table Editor. You
retrieve a new fetch set each time you:
- Join a table in the active Edit Definition.
- Move the Join Arrow in a selected table to retrieve
related rows from subordinate tables.
- Set Table Specifications for a selected table.
- Click the Refetch button in a selected table.
You can set a value for Maximum Fetch Rows
in Personal Options, up to the site-specific maximum set in Product
Options. If you do not set a limit in Personal Options, the limit
set in Product Options is used by default. (If a limit is not specified
in Product Options, 1000 rows is the default limit.)
- File Access Definition
- The File Access Definition (FAD)
is the basis for Archive File Security. All Archive Files generated
by running an Archive Request that references an FAD are secured by
the FAD.
- Functional Security
- As the most general level of Optim Security, Functional Security allows
you to control user access to the interface for functions provided
by Optim.
For example, for a specialized administrator role that is intended
to create process requests and objects needed to run these requests,
you can grant unlimited access to functions. For members of a role
intended only to run the pre-defined process requests, however, you
can grant more limited access to functions.
- Generic Primary Key
- A generic primary key is a primary key that can
be used by a set of tables that have the same base name, key columns,
and attributes, but different Creator IDs. Generic primary keys are
stored in the Optim Directory
and are identified by an asterisk (*) as the Creator ID.
- Generic Relationship
- A generic relationship is a relationship that can
be used by related tables that are identical, but have different Creator
IDs. Generic relationships are stored in the Optim Directory and are identified by an asterisk
(*) as the Creator ID.
Note: You can convert an explicit relationship
to a generic relationship; however, you cannot convert a generic relationship
to an explicit relationship.
- Group Selection
- Group selection defines a sample set of rows to
extract from a Start Table. You specify a maximum number of rows for
a number of unique values based on a selected column in the Start
Table. For example, you can extract five rows of customer data from
any ten states.
- Hexadecimal Literal
- A hexadecimal literal specifies a column value in
a Column Map or Relationship when the corresponding column contains
binary data. Define a hexadecimal literal using the following characters:
X ‘1234567890ABCDEF' or 0X1234567890ABCDEF
For example, to define a Column Map to mask CUSTOMERS
data for a test database, where the CUST_ID column has a VARBINARY
data type, specify the source column value for the CUST_ID as: X ‘1234CD'.
- Import Utility
- The Import Utility copies selected Optim object definitions from an external file
(created using the Export Utility) to the current Optim Directory. The Import Utility is useful
for moving Optim objects from
one Optim Directory to another.
- Incremental Aging
- Incremental Aging is a feature you can use with
the Age Function to age dates based on a specified number of years
(Y), months (M), weeks (W), days (D), or any combination of these
units. For example: [+ or -] nY.
- Insert Process
- The Insert Process copies data from a Source File
into specified destination tables. Use an Insert Request to initiate
the Insert Process and specify one of the following methods to perform
the Insert Process:
- Insert adds only new rows to a destination table.
- Update replaces existing rows in the destination
table.
- Update/Insert updates existing rows and inserts
new rows.
- Mixed allows you to specify Insert, Update, or Update/Insert
Processing for any table individually.
- Insert Request
- An Insert Request specifies a Source File containing
the data you want to insert or update, and the parameters needed to
run the process. The Insert Request Editor prompts you to:
- Specify a Source File and a Control File.
- Specify Table Map and Delete Options.
- Select insert, update, update/insert, or mixed Process
Options.
- Choose options for reporting and date aging, as
needed.
You can save and reuse Insert Requests stored
in the Optim Directory.
- Join
- When viewing a table using the Table Editor, the
Point and Shoot Editor, or the Browse Utility, you can use the Join
command to display the related data from other tables.
- Large Object (LOB)
- The term Large Object (LOB) refers to two data types,
BLOB (Binary Large Object) and CLOB (Character Large Object). A LOB
typically contains a large amount of data (for example, objects such
as audio files, photos, and video files).
You can
view LOBs through the Table Editor, the Point and Shoot Editor, or
the Browse Utility. LOBs are displayed in Native or Non-Native Mode:
- In Native LOB Mode, a set of three icons displays
in a LOB column; you can select the corresponding icon to view LOB
data in an associated application, in character mode, or in hexadecimal
mode.
- In Non-Native LOB Mode, LOB data displays as normal
table data (either VARCHAR or VARBIN).
- Load Process
- The Load Process transforms the contents of a Source
File into the load utility format for a supported database. Initiate
the Load Process with a Load Request that specifies the Source File
containing the data to load and other process parameters.
- Load Request
- A Load Request specifies a Source File (either an
Extract or Archive File) containing the data you want to load and
the parameters needed to run the process for the DBMS Loader you are
using. The Load Request Editor prompts you to specify:
- A Source File, Control File, and Table Map options.
- DBMS Loader options.
- Options for reporting and date aging, as needed.
You can save and reuse Load Requests stored
in the Optim Directory.
- Match Key
- A Match Key is used in a Compare Process to match
rows from Source 1 and Source 2 specified in a Compare Request. Typically,
the Compare Process uses the Primary Key from one of the source tables
to process the comparison. However, if neither source table has a
Primary Key, you can specify one or more other columns to define a
Match Key.
Note: Match Keys are only used in the active Compare Request
and are not saved to the Optim Directory.
- Move
- Move facilitates the extraction and migration
of sets of relationally intact data. Using Move, you can create
test databases that are referentially intact subsets of a production
database or extract sets of related data and transform it as you migrate
the data to the test database.
- Multi-byte
- A multi-byte character has a code point that may
require more than a single 8-bit byte to be expressed. Multi-byte
character sets may be of either fixed width, in which all code points
require the same number of bytes, or variable width, in which different
code points may require a different number of bytes. JA16SJIS is a
variable width character set, as are UTF8 and AL32UTF8.
- Naming Conventions
- Optim uses
the following naming conventions.
Optim Objects:
identifier.name
Table Names and Primary Keys:
dbalias.creatorid.tablename
Relationships:
dbalias.creatorid.tablename.constraint
- NULL
- NULL indicates a column value in a Column Map or
Relationship is unknown. The destination column must be null eligible
or defined as NULL.
- Numeric Constant
- A numeric constant specifies a number for a column
value in a Column Map or Relationship. You can use a numeric constant
as the source for numeric destination columns.
- DB2
- INTEGER, SMALLINT, DECIMAL, FLOAT, DOUBLE
- Oracle
- NUMBER, FLOAT
- Sybase ASE
- TINYINT, INT, SMALLINT, DECIMAL, FLOAT, REAL, MONEY,
SMALL MONEY
- SQL Server
- TINYINT, INT, SMALLINT, DECIMAL, FLOAT, REAL, MONEY,
SMALL MONEY
- Informix®
- DECIMAL, INT, SMALLINT, FLOAT, SMALLFLOAT, NUMERIC,
REAL, SERIAL, MONEY, DOUBLE PRECISION
Note: The numeric constant must represent a value that
fits into the destination column, based on data type, precision, and
scale.
- Numeric Expression
- A numeric expression specifies a value in the source
column in a Column Map. The data types for the corresponding source
and destination columns must be compatible. A numeric expression consists
of:
(Operand 1) Operator (Operand 2)
where operand must be a numeric column
or a numeric constant, and the operator specifies
whether to add ( + ), subtract ( - ), divide ( / ), or multiply (
* ).
- Object Definition
- An object definition specifies the set of parameters
a database requires to create a table, primary key, relationship,
index, view, or alias.
- Object Security
- Object Security allows you to control access to
specific objects in the Optim Directory,
using an Access Control List (ACL). Any Optim object
can be secured by associating it with an ACL. An ACL lists roles and
grants or denies privileges for each role to read, update, delete,
or execute (where appropriate) the object and the ACL. For example,
you might use Object Security to allow members of a role to read and
execute, but not edit, a specific Archive Request.
- Optim
- Optim enhances
database performance by automating the process of archiving, editing,
migrating, and comparing relationally intact data from multiple database
tables. Optim includes
the following components: Archive allows you to identify and
archive sets of relationally intact data before removing selected
data from your database. Move facilitates the extraction and
migration of sets of relationally intact data. Edit is used
to browse and edit sets of relationally intact data in multiple tables. Compare facilitates
comparisons of sets of relationally intact data.
- Optim Directory
- The Optim Directory
contains a set of tables that store all the product-specific object
definitions you create using Optim.
Typically, a site uses one shared Optim Directory,
regardless of the number of database instances to be accessed or the
number of workstations using the product. However, you may create
more than one Optim Directory,
as needed for your site. Use the Optim Directory Editor to
view or modify general, server, and connection settings for an Optim Directory.
- Optim Object
- An Optim Object
is a user-defined object that is unique to Optim and is
stored in the Optim Directory. Optim Objects include Access Definitions,
Table Maps, Column Maps, primary keys, relationships, Column Map Procedures,
Storage Profiles, various process requests, security definitions,
and Archive File registrations.
- Oracle Sequence Function
- The Oracle Sequence Function is used in a Column
Map (for Insert or Load Processing) to assign a value to a destination
column based on the Oracle Sequence. This function is formatted as: schema.seqname.NEXTVAL(INCL_UPD)
- schema
- Identifier for the name of the Oracle Sequence.
- seqname
- Name of the Oracle Sequence that assigns sequential
values.
- NEXTVAL
- Inserts the next Oracle Sequence value into the
destination column.
- INCL_UPD
- Updates a sequence value assigned to a column when
rows are updated during an Insert.
- Parent Expression
- A parent expression is a list of columns in the
parent table that relate to corresponding columns in the child table.
If the parent table has a primary key, the column names are inserted
automatically. You can accept, modify, or replace the column names.
- Passwords and User IDs
- Passwords and User IDs allow you to connect to a
particular database. You can set passwords and User IDs on the Logon tab
in Personal Options. The maximum length for passwords and User IDs
varies depending on the DBMS.
- Permission
- A permission indicates whether a user is allowed
or denied access to Functional and Object Association privileges, Optim objects, and Archive File
data.
Functional privilege permissions can be set
for each role in the (Default) Access Control Domain (ACD). Object
Association privilege permissions can be set for roles in any ACD.
Each secured object, including ACDs and File Access
Definitions (FADs), has an Access Control List (ACL) that allows or
denies Read, Update, Delete, and Execute permissions for the object
to roles defined in the associated ACD. The ACL also allows or denies
Read, Update, and Delete permissions for the ACL itself.
Access permissions for Archive File data are defined
in a FAD, which is associated with each secured Archive File. The
FAD lists tables and columns for which access permissions are defined.
For each listed role, the FAD grants or denies permissions to access
the archived data.
- Personal Options
- Personal Options set preferences for using Optim from
your workstation. You can set preferences for confirmation prompts,
display features, error messages, schedule monitoring, DBMS Loader
directories, defaults for using the Create Utility, logon passwords,
Server defaults, display options for Edit and Browse, Archive directories,
removable media options, defaults for using Actions, and default options
for automatic email notification.
To return to the
settings in place upon opening the Personal Options dialog,
click Defaults.
Note: Many site-specific
Product Options may override your Personal Options.
- Point and Shoot
- Point and Shoot allows you to select specific rows
from a Start Table to be used in a process request. Point and Shoot
is available when you create an Access Definition, or when you use
an Extract, Archive, or Restore Request.
When you
use Point and Shoot to select rows from the Start Table, the primary
keys for these rows are stored in a local Point and Shoot List or
an external Point and Shoot File. The process request uses the primary
keys to identify the rows to process first.
- Point and Shoot List
- A Point and Shoot List is a list of primary key
values for the rows you want to include in an Archive, Extract, or
Restore Process request. You can create two types of row lists using
Point and Shoot:
- A Point and Shoot List saved locally, stored with
and available only for the associated Access Definition or process
request.
- A Point and Shoot List saved as an external Point
and Shoot File, which can be referenced by other Access Definitions
and process requests.
- Primary Key
- A Primary Key defines a column or set of columns
that uniquely identify each row in a table. Although you can view
primary keys defined to the database, you can edit only those primary
keys defined to the Optim Directory.
- Privilege
- A privilege defines a type of user access to the Optim functions and objects. Optim provides Functional and Object
Association privileges, for which permissions may be granted or denied.
Functional privileges control user access to functions
and dialogs in Optim. For example,
they allow users to create, run, and access requests for actions,
definitions, security definitions, and utility definitions. They also
allow users to execute a utility from the command line, perform tasks
within the Configuration program, edit Product Options, use Security
dialogs to secure Optim objects,
functions, and Archive Files, export/import secured Archive Files,
modify a File Access Definition, and run Security Reports.
Object Association privileges control a user's ability
to secure types of objects, using an Access Control List (ACL). Objects
include action requests, definition requests, and utility definitions.
Any Optim object can be secured
by associating it with an ACL. A member of a role that is granted
the Object Association privilege for an object type (e.g., Access
Definitions) can define an ACL for any object of that type that the
member creates. Object Association privileges allow a role to use
the roles defined in an Access Control Domain (ACD) as the basis for
an ACL that protects objects of the indicated type. An ACL lists roles
in the associated Access Control Domain (ACD) and grants or denies
permissions for each role to read, update, delete, or execute (where
appropriate) the object and its ACL.
Privileges
are organized into "classes". For example, the Invoke Action Editors
Functional privilege class includes the privileges that make the Action
Editors (that is, Archive, Compare, Convert, Delete, Extract, Insert,
Load, Report, Restore, Table Editor) available to users. The Associate
Action Editors Object Association privilege class includes privileges
that allow users to secure requests created by the Action Editors.
- Product Options
- Product Options are a set of preferences that apply
to all workstations using Optim. Specify
processing limits, site defaults, database options, the current Product
Configuration File, the password to access Product Options, Edit options,
Server configuration, Archive options, DBMS Loader parameters, and
report formatting defaults.
Many site-specific Product
Options override Personal Options. To return to the settings in place
upon opening the Product Options dialog, click Defaults.
Note: Before
you can view or modify Product Options, you must provide a password.
- Propagate Function
- The Propagate Function is used in a Column Map (for
Insert, Load, or Convert Processing) to assign a value to a destination
column, and then propagate that value to all related tables. Format
this function as: PROP(value,column-name)
- value
- Value for the destination column.
- column-name
- Name of the source column containing the value for
the destination column that is to be propagated to all related tables.
- Random Function
- The Random Function specifies a column value in
a Column Map by returning a random number within the range specified
by the low and high values. This function is formatted as: RAND(low,high)
- low
- Lowest possible random value in the range.
- high
- Highest possible random value in the range.
- Relationship
- A relationship defines columns in a parent table
that relate to corresponding columns in a child table. The data types
of the corresponding columns must be compatible. Relationships can
be defined to the database or the Optim Directory;
however, you can create and edit only those relationships defined
to the Optim Directory.
Relationships defined to the Optim Directory do not have to conform to database
conventions. You can use these flexible "extended Optim relationships" to relate parent and child
columns using column names, NULL, literals, constants, concatenated
expressions, and the Substring Function.
- Relationship List
- The list of relationships (found on the Relationships tab
of the Access Definition Editor) defined for the tables in an Access
Definition. You can specify the traversal path for extracting data
from two or more pairs of related tables. Typically, Optim traverses
all relationships from parent to child; however, you can specify other
traversal options in an Access Definition.
- Report Process
- A Report Process summarizes the contents of an Archive
or Compare File according to your specifications, and stores this
data in a Report File. Use the Report Request Editor to select the
Archive or Compare File and other specifications.
- Report Request
- A Report Request contains the specifications needed
to collect data from an Archive or Compare File, and send the output
to a file, a printer, or both.
The Report Request
Editor prompts you to specify the Source File and the tables to be
included in the Report Process, layout and formatting options, and
whether to send the output to a file, printer, or both.
- Reset Object Cache
- The Reset Object Cache command
is available from the Utilities menu to reset
current database objects or configuration parameters. (Optim uses
a caching scheme to improve performance.)
- Restart/Retry
- The Restart/Retry Utility allows you to:
- Restart Processing from the last commit point when
a Delete, Insert, or Insert/Update Process ends abnormally because
of an internal error, resource limitations, or user request.
- Retry the Process for discarded rows when a Delete,
Insert, or Insert/Update Process ends normally, but a number of rows
could not be processed (due to conflicting data types or referential
integrity rules). The process writes these discarded rows to a Control
File, which you can browse. Once you resolve any problems, you can
retry the process.
- Restore Process
- A Restore Process selects data from one or more
Archive Files and restores the data to the original or a different
database. Initiate the Restore Process with a Restore Request that
specifies the Archive Files and defines the Insert or Load Request
used to restore the archived data.
- Restore Request
- A Restore Request defines the parameters for restoring
data from one or more Archive Files to the original or a different
database. Use the Restore Request Editor to specify the Archive File(s)
to be restored, global or local selection criteria, an Insert or Load
Request to restore the archived data to the database, and a Request
Selection Mode to match the Insert or Load Request with the appropriate
Archive File.
You can save and reuse Restore Requests
stored in the Optim Directory.
- Save
- Saves the current version under the same name, replaces
the original version, and displays the current version.
- Save As
- Saves the current version under a different name,
preserves the original version, and displays the newly named version.
Save As is useful for modeling a new item based on an existing item.
- Save Copy As
- Saves a copy of the current version under a different
name, preserves the original version, and displays the current version.
Save Copy As is useful if you want to save a copy of an item at a
given stage in development and continue editing the current version.
- Schedule Utility
- The Schedule Utility allows you to create and maintain
scheduled processing jobs for one or more process requests to Archive,
Compare, Convert, Delete, Extract, Insert, Load, or Restore data.
Scheduling details include the start date/time, latest start time,
cycle options, and the definition of the process requests. The Schedule
Utility interfaces with the Scheduling Monitor to track the progress
of scheduled jobs.
- Scheduling Monitor
- The Scheduling Monitor is an Optim application
that tracks each scheduling job. This monitor allows you to view and
edit the number of scheduled jobs, monitor active jobs, and review
the results of completed jobs.
- Segment Size
- When an Archive or Extract File is larger than the
storage capacity for a target media type, the file must be segmented
to span more than one volume. You can specify default segment size
values for fixed and removable media storage in Personal Options.
- Semantic Aging
- Semantic Aging is a feature of Optim that
allows you to define a set of rules for date aging. For example, you
can define a set of rules to adjust aged dates to result in valid
business days.
- Sequential Function
- The Sequential Function specifies a column value
in a Column Map by returning a number that is incremented sequentially
by the step value based on the start value. This function is formatted
as: SEQ(start,step)
- start
- Starting value for the sequence.
- step
- Value to increment the sequence.
- Set as Default
- The Set as Default command allows you to profile
the entries you specify on a process request or definition editor
as the default entries. If you select Set as Default from
the File menu, the next time you open that
editor, your default entries display automatically.
- Source File
- A Source File is an Extract File or an Archive File
used as the source of data for a process. You must specify a Source
File when you create a Convert, Delete, Insert, or Load Process request,
or when you use the Create Utility to create database objects.
- Source Format Exit
- A Source Format Exit ages dates based on a source
exit routine. This exit routine is called to format the source column
in an Age Function that would otherwise not be supported in a Column
Map. This exit routine examines the source date in a character or
integer column and converts it into a date format usable as input
to the Age Function.
Specify the Source Format Exit
in a Column Map source column as AGE(SRCEXIT=dllname),
where SRCEXIT is the name of the Source Format Exit.
- Special Registers
- A special
register stores system information that can be referenced in an SQL
statement. You can use a special register to specify a column value
in a Column Map. You can use the following special registers:
- CURDATE( )
- CURRENT DATE
- CURRENT_DATE
- CURRENT TIME
- CURRENT_TIME
- CURRENT TIMESTAMP
- CURRENT_TIMESTAMP
- CURRENT SQLID
- CURRENT_SQLID
- CURTIME ( )
- GETDATE ( )
- GETTIME ( )
- NOW ( )
- SYSTDATE ( )
- USER
- WORKSTATION_ID
- SQL WHERE Clause
- An SQL WHERE Clause specifies criteria for extracting
or archiving data. You can use an SQL WHERE Clause when you define
Table Specifications as part of your selection criteria in an Access
Definition. The statement must conform to SQL syntax.
- Standard Exit
- A Standard Exit is an exit routine that is called
to derive the value for a destination column in a Column Map. Specify
the Standard Exit in a Column Map source column as: EXIT dllname.
- Start Table
- The Start Table is the first table to use in processing
an Archive or Extract. You can specify any table in the Access Definition
as the Start Table, except a reference table. If you do not explicitly
specify a Start Table, the first table in the table list is the Start
Table.
- Storage Profile
- A Storage Profile allows you to define storage parameters
for creating an Archive File on fixed or secondary media. You can
use a Storage Profile to automatically create a duplicate Archive
File, or to copy an Archive File to a supported backup device. You
can also use a Storage Profile to override default values defined
in Personal Options for segment size and the default value defined
in Product Options for a minimum retention period (for supported devices).
Use a Storage Profile by specifying the name of the Storage Profile
in an Archive Request.
- Storage Profile Utility
- The Storage Profile Utility allows you to create
and maintain Storage Profiles. Access the Storage Profile Utility
from the Utilities menu on the main window.
To edit a Storage Profile referenced in an Archive Request, select Edit
Storage Profile from the Tools menu
on the Archive Request Editor.
- String Literal
- A String Literal specifies a column value in a Column
Map or Relationship when the corresponding column contains character
data. To define a string literal, you can use any characters, enclosed
in single quotes. For example: '90210' or 'CA'.
- Subset Extract File
- The Subset Extract File is generated during a Restore
Process when you define selection criteria to restore a subset of
an Archive File. That subset is automatically extracted from the Archive
File and stored in a Subset Extract File, which is then restored to
the selected database. You can specify whether to save or delete the
Subset Extract File after the data is restored.
- Substring Function
- The Substring Function specifies a column value
in a Column Map or Relationship by returning a substring of the named
column. This function is formatted as: SUBSTR(column-name,start,length)
- column-name
- Name of character or binary column.
- start
- Position of the first character in the string.
- length
- Number of characters to use.
- TableList
- List of table names in an Access Definition to specify
the data to extract or archive. To create the table list, specify
a Start Table and add other tables.
- Table Map
- A Table Map defines specifications for correlating
source and destination tables of compatible data. You can map tables
that have different names, modify table names, exclude tables from
a process, or include Column Maps for greater control over the data.
You can use Table Maps in a Convert, Insert, or Load
request, or with the Create Utility. You can save and reuse Table
Maps stored in the Optim Directory.
- Target Aging
- Target Aging is a feature that allows you to perform
date aging based on a specific date. For example, you can specify
the base date of the production run and specify a target date for
a particular test. Optim applies
business rules and automatically ages dates to maintain the relationship
between the base and target.
- Traversal Cycle
- A traversal cycle occurs when an Extract or Archive
Process revisits tables specified in an Access Definition. Traversal
cycles depend on the specifications for processing each relationship.
- Traversal Path
- A traversal path directs an Extract or Archive Process
through related tables specified in an Access Definition. The traversal
path is defined by relationships selected between tables, as well
as the responses to Options 1 and 2 on the Relationships tab
of the Access Definition Editor.
The
typical traversal path begins at the Start Table and proceeds through
the data model traversing all relationships from parent to child.
- Unicode
- The universal character encoding, maintained by
the Unicode Consortium. This encoding standard provides the basis
for processing, storage and interchange of text data in any language
in all modern software and information technology protocols.
The Unicode Standard provides a uniform architecture
and encoding for all languages of the world, with over 95,000 characters
currently encoded. Unicode is a fundamental component for providing
seamless data interchange around the world, and has been adopted by
such industry leaders as Apple, HP, IBM®,
JustSystem, Microsoft,
Oracle, SAP, Sun, Sybase ASE, Unisys and many others.
For additional information on Unicode or the Unicode
Consortium, please visit http://www.unicode.org.
- User ID
- A User ID specifies the authorization control that
permits individuals to use specific Optim options
and processes. The database administrator usually assigns User IDs
when setting authorizations and privileges required for accessing
a particular database.
- Variables
- Variables are user-defined default values specified
in an Access Definition. You can use these substitution variables
to specify column selection criteria or to create an SQL WHERE Clause.