General page

The General page contains general information about the table definition.

The following fields are on this page:

  • Data source type. The type of data source, for example, UniVerse.
  • Data source name. If you imported the table definition, this contains a reference to where the original data is found. For UniVerse and ODBC data sources, this is the data source name. For hashed file data sources, this is an account name. For sequential file sources, this is the last component of the directory path where the sequential file is found.
  • Table definition. The name of the table definition.
  • Mainframe platform type. The type of mainframe platform that the table definition applies to. Where the table definition does not apply to a mainframe data source, it displays <Not applicable>.
  • Mainframe access type. Where the table definition has been imported from a mainframe or is applicable to a mainframe, this specifies the type of database. If it is not a mainframe-type table definition, the field is set to <Not applicable>.
  • Metadata supports Multi-valued fields. Select this check box if the metadata supports multivalued data. If the check box is selected, three extra grid columns used for multivalued data support will appear on the Columns page. The check box is disabled for ODBC, mainframe, and stored procedure table definitions.
  • Fully Qualified Table Name. This read-only field shows the fully qualified table name, as derived from the locator (see "Locator Page").
  • ODBC quote character. Allows you to specify what character an ODBC data source uses as a quote character. Specify 000 to suppress the quote character.
  • Short description. A brief description of the data.
  • Long description. A full description of the data.

The combination of the data source type, data source name, and table or file name forms a unique identifier for the table definition. The entire identifier is shown at the top of the General page. No two table definitions can have the same identifier.

The table definition can be located anywhere in the repository that you choose. For example, you might want a top level folder called Tutorial that contains all the jobs and table definitions concerned with the server job tutorial.