Saturday, October 8, 2011

QuickBase - Overview

QuickBase Applications

QuickBase versatility sets it apart in giving you a single platform for improving many functions in your organization; the list of strong applications for QuickBase is long and growing. Applications have:

*                       Enterprise Project Management (PMO Offices)  Project mgmt Office

*                       Enterprise KPI (Key Performance Indicator) tracking and reporting

*                       Sales and Customer Management (CRM)

*                       Sarbanes-Oxley audit tracking

*                       Program and Affiliate Tracking

*                       Procurement and Marketing Workflow systems (Including RFQ and Contracts generation and tracking)

*                       Property, Asset, Personnel and other Resource Tracking and Assignment

*                       Capital Expenditure Budgeting and Tracking

*                       Online surveys with real-time results reporting


QuickBase applications solve critical business problems and help improve productivity and efficiency because they are tailored by the user to match the exact workflow and unique needs of their team - something complex point solutions or generic spreadsheets simply can't match.

  • Capture and modify data: Whatever kind of data you need to store--sales leads, catalog listings, project milestones, workflow checklists--you can use QuickBase's forms to record and organize that data so it makes sense to you.
  • Filter, sort, and group data: Easily find the records that match your criteria, and then sort those records into groups that make their relationships clear.
  • Display your data: QuickBase uses different views (Table, Grid Edit, Summary/Crosstab, Calendar, Chart, and Timeline) to display and summarize data. Switching between them is easy, like taking tasks listed in a table and displaying them as a timeline.
Create reports: Print out a hard copy, embed charts in the annual report, or email this month's sales numbers.


Note: Some of the articles are grab from various Websites / Blogs.

Thursday, October 6, 2011

Optim - Overview -- II

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 specify Table Maps in a request to compare, convert, insert, load, or restore data, or with the Create Utility.

Using the Command Line Interface

The Command Line Interface (PR0CMND.exe) allows you to automate Optim™ processing:
  • Run process requests to archive, convert, delete, extract, insert, load, or restore data.
  • Run multiple process requests in a scheduled job.
  • Browse and edit data in the Table Editor.

How to Run PR0CMND

  • You can run PR0CMND.EXE from the command line, a batch file, or another program.
  • You must be in the application software BIN directory or specify the path for this directory on the command line.

Syntax Guidelines

The typical command consists of PR0CMND followed by the command-line keywords and associated arguments. The following guidelines apply:
  • Command-line keywords can be specified in any order, separated by one or more spaces, but no commas.
  • Keywords can be specified in mixed case. (Most keywords are shown bold and uppercase in the help for emphasis only).
  • Command-line keywords and associated arguments must be separated with an equal sign (=) or a colon (:).
  • An override keyword must be separated from the associated argument with a blank space.
  • Keywords may be prefixed by a forward slash (/) or a dash ( ). For example, all of the following are equal:
PST=MARKET
/PST=MARKET
—PST=MARKET

  • The first operation argument must be prefixed by a forward slash (/) or a dash ( ), for example:
/X or —X
Browse
/R or —R
Run
/E or —E
Edit

  • An argument associated with a command-line keyword that includes spaces must be enclosed in single or double quotes.
  • When overrides are specified for a process request defined in a parameter file, the command-line keyword indicating that overrides are used (OV) must follow other command-line keywords and precede the override parameters. The first override keyword and associated argument must begin on the following line, and each additional override must be on a separate line. The override keyword END must follow the last override, and must also be on a separate line.
Note: You can also specify a variety of overrides for each process request or specify overrides that apply to browsing and editing data.

Ref: IBM Guide
Note: Some of the articles are grab from various Websites / Blogs.

Optim - Overview I

Access Definition

An Access Definition specifies the Start Table, related tables, relationships, and selection criteria to define the data you want to archive, extract, edit, or compare.
Note: You can save and reuse Access Definitions, which are stored in the Optim™ Directory.

Use Access Definitions to

  • Manage and maintain lists of tables and relationships that describe the data you want to archive, extract, or edit.
  • Specify the selection criteria you want to use to archive or extract data.
  • Specify variables and default values to use in your selection criteria.
  • Select columns and sort options to display for Point and Shoot.
  • Use Point and Shoot to narrow the focus for archiving or extracting data.
Because Access Definitions provide flexibility in managing your data, it is easy to:
  • Create new Access Definitions and modify or reuse existing definitions.
  • Share Access Definitions with other users.
  • Include a named or local (temporary) Access Definition with an Archive Request, Edit Definition, or Extract Request.

Column Map

A Column Map defines the specifications for mapping columns of compatible data between source and destination tables.
You can map columns that have different names, modify column 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.
Note:
  • If you define a Column Map in a Convert, Insert, Load, or Restore Request, you can specify the source column value, an explicit column name, NULL, constant, literal, function, expression, special register, or exit routine.
  • If you define a Column Map in a Compare Request, you can map only explicit column names.

Column Map Procedure

A Column Map Procedure is a custom program that is referenced by a Column Map and is written and compiled using the Column Map Proc Editor.
These programs are used in a Convert, Insert, Load, or Restore Request for special processing and data manipulation that is beyond the scope of native Column Maps. You can use a Column Map Procedure by specifying the name of the procedure as the source column.

DB Alias

A DB Alias is a set of specifications used to identify, locate, and access a particular database.
The DB Alias serves as a high-level qualifier for names of database objects referenced, defined, or accessed using Optim™, for example, dbalias.creatorid.tablename.
The specifications for defining a DB Alias are usually provided by the database administrator.

About DB Aliases

A DB Alias is a user-defined object associated with a database.
When you define a DB Alias, you provide parameters that Optim™ uses to communicate with that database. These parameters include the type and version of the database management system (DBMS) and any required connection specifications.
Note: DB Aliases are defined using the Configuration Program and are stored in the Optim Directory. You must be authorized to define a DB Alias. See the Installation and Configuration Guide for additional information.
A DB Alias name serves as a high-level qualifier that allows you to access a specific database to perform requested functions. For example, in an Access Definition, you must qualify the name of a table with a DB Alias name. The referenced DB Alias supplies the parameters needed to connect to the database in which the table resides.

Databases

A DB Alias identifies a specific database and serves as a prefix in the fully qualified names of primary keys, database tables, and relationships. DB Aliases are essential elements in managing your databases. Keep in mind that each:
  • Database can have only one DB Alias.
  • DB Alias name must be unique.
Also, objects in the Optim Directory cannot have the same name as a DB Alias.

Ref: IBM Guide and Materials (www.ibm.com)

Note: Some of the articles are grab from various Websites / Blogs.