Information Catalog Manager Administration Guide

Exchanging MDIS-conforming metadata with other products

The Information Catalog Manager includes predefined object types that can be exchanged with metadata from other Data Warehouse Center components and other MDIS-conforming products from IBM and other companies. This section describes how to use the MDIS conversion utility to convert MDIS-conforming metadata from another product into an Information Catalog Manager tag language file. It also explains how to use the utility to convert the Information Catalog Manager metadata into an MDIS-conforming tag language file.

This section also describes how to import MDIS metadata directly into, and export MDIS metadata directly from, your information catalog.

For information about the Metadata Interchange Specification, including complete MDIS object type definitions, visit the Meta Data Coalition's Web site at http://www.MDCinfo.com.

Exchanging metadata by using the MDIS conversion utilities

You can use the MDISDGC command to convert metadata that conforms to the Metadata Interchange Specification (MDIS) into an Information Catalog Manager tag language file. You can then import the tag language file into Information Catalog Manager by using the methods that are described in Importing tag language files.

You can export metadata from the Information Catalog Manager as described under Exporting metadata. You can convert the exported tag language file into an MDIS-conforming tag language file by using the DGMDISC command.

Converting MDIS-conforming metadata into a tag language file

Use the MDISDGC command from the MS-DOS command prompt to convert MDIS-conforming metadata into an Information Catalog Manager tag language file, which you can then import into your information catalog. All MDISDGC command variables are required.

MDISDGC userid password input_tagfile output_tagfile logfile

userid

Your Windows NT user ID. User IDs for Windows NT are case-sensitive; you must enter them exactly as specified.

password

The password for userid. Passwords for Windows NT are case-sensitive; you must enter them exactly as specified.

input_tagfile

Full path and file name of the MDIS-conforming tag language file that you want to convert into a tag language file. If you type only the file name, the Information Catalog Manager assumes the file exists on the drive and path that is pointed to by the DGWPATH environment variable.

output_tagfile

Full path and file name for the tag language file that is created by MDISDGC. If you type only the file name, the Information Catalog Manager places the file on the drive and path pointed to by the DGWPATH environment variable.

logfile

Full path and file name destination for messages that are generated during conversion by the Information Catalog Manager. If you type only the file name, the Information Catalog Manager places the file on the drive and path pointed to by the DGWPATH environment variable.

Converting a tag language file into MDIS-conforming metadata

Use the DGMDISC command from the MS-DOS command prompt to convert an Information Catalog Manager tag language file into MDIS-conforming metadata. You can then use this metadata with other MDIS-compliant products. All DGMDISC command variables are required.

DGMDISC userid password input_tagfile output_tagfile logfile

userid

Your Windows NT user ID. User IDs for Windows NT are case-sensitive; you must enter them exactly as specified.

password

The password for userid. Passwords for Windows NT are case-sensitive; you must enter them exactly as specified.

input_tagfile

Full path and file name of the tag language file that you want to convert into an MDIS-conforming tag language file. If you type only the file name, the Information Catalog Manager assumes the file exists on the drive and path that is pointed to by the DGWPATH environment variable.

output_tagfile

Full path and file name for the MDIS-conforming tag language file that is created by DGMDISC. If you type only the file name, the Information Catalog Manager places the file on the drive and path pointed to by the DGWPATH environment variable.

logfile

Full path and file name destination for messages that are generated during conversion by the Information Catalog Manager. If you type only the file name, the Information Catalog Manager places the file on the drive and path pointed to by the DGWPATH environment variable.

Importing MDIS-conforming tag language files

To import an MDIS tag language file directly into your information catalog, enter the Information Catalog Manager command from a an MS-DOS command prompt. Adhere to the following rules for the command syntax:

• All the parts, except where specified, are case-insensitive.
• Either a slash (/) or a hyphen must precede each keyword (-).
• All keywords that follow the DGUIDE command are required. All keywords that follow the /MDIS_IMPORT keyword are required.
• Underlined choices are defaults.

DGUIDE /USERID userid /PASSWORD password /DGNAME dgname /MDIS_IMPORT filename /LOGFILE filename name/ADMIN Optional keywords: /TRACE 0|1|2|3|4

For example, to import MDIS metadata into your information catalog, type the following command (do not enter a line break):

DGUIDE /USERID longods /PASSWORD secret /DGNAME ICMSAMP /ADMIN
/MDIS_IMPORT c:\mdis.tag /LOGFILE c:\mdis.log

/ADMIN

Specifies that you are logging on as an administrator. You must log on as an administrator to import metadata.

/DGNAME

Your information catalog name.

If the information catalog is local, specify the database name. If the information catalog is remote, specify the alias under which it was cataloged.

Example:

/DGNAME ICMSAMP

/LOGFILE

This parameter is required.

Specifies the file destination for messages that the Information Catalog Manager generates during MDIS import or MDIS export. Unless you specify a full drive, path, and file name, the Information Catalog Manager places the file in the path specified on the DGWPATH environment variable. You must specify a fixed drive.

Example:

/LOGFILE d:\tagfile.log

/MDIS_IMPORT

Imports the MDIS-conforming tag language file that you specify. Unless you specify the full drive, path, and file name, the Information Catalog Manager assumes that the file is in the path specified on the DGWPATH environment variable.

Example:

/MDIS_IMPORT d:\tagfile.tag

The information catalog into which you import MDIS metadata must include, but is not limited to, valid MDIS object type definitions.

/PASSWORD

Your password for this user ID.

Example:

/PASSWORD secret

Passwords are case-sensitive for accessing databases on the following operating systems, you must type them exactly as specified.

• AIX
• Windows NT and Windows 2000
• Solaris Operating Environment

/TRACE

The level of trace information to send to the Information Catalog Manager trace file. Each higher level includes the functions of the levels below it (for example 3 includes the functions of levels 0, 1, 2, and 3). You might need to specify a higher level if you call IBM Software Support to diagnose the Information Catalog Manager problems.

0

The default. Includes all messages and warning, error, and severe error conditions.

1

Includes entry and exit records of the highest level Information Catalog Manager functions.

2

Includes extremely granular entry and exit records of the Information Catalog Manager functions.

3

Includes input and output parameters (that exclude input or output structures).

4

Includes all input or output structures that are passed to and used by the Information Catalog Manager.

/USERID

Your information catalog user ID. Type the user ID required by the database where the information catalog resides. For example, the user ID might be your local, LAN, AS/400, AIX, or OS/390 TSO user ID.

Example:

/USERID longods

Exporting MDIS-conforming tag language files

To export an MDIS tag language file directly from your information catalog, enter the DGUIDE command from an MS-DOS command prompt. Adhere to the following rules for the command syntax:

• All the parts, except where specified, are case-insensitive.
• Either a slash (/) or a hyphen must precede each keyword (-).
• All keywords that follow the DGUIDE command are required. All keywords that follow the /MDIS_EXPORT keyword are required.

DGUIDE /USERID userid /PASSWORD password /DGNAME dgname /MDIS_EXPORT filename /LOGFILE filename /OBJTYPE object_type /OBJECTS name Optional keywords: /ADMIN /TRACE 0|1|2|3|4

For example, to export MDIS metadata from your information catalog to a file, type the following command (do not enter line breaks):

DGUIDE /USERID longods /PASSWORD secret /DGNAME ICMSAMP /ADMIN
/MDIS_EXPORT c:\mdis.tag /LOGFILE c:\mdis.log 
/OBJTYPE database /OBJECTS server01.payroll.valdezma

/ADMIN

Specifies that you are logging on as an administrator. If you do not specify this optional keyword for the DGUIDE command, you log on as a user. You can export metadata as a user; however, you cannot perform all administrator tasks.

/DGNAME

Your information catalog name.

If the information catalog is local, specify the database name. If the information catalog is remote, specify the alias under which it was cataloged.

Example:

/DGNAME ICMSAMP

/LOGFILE

Specifies the file destination for messages that the Information Catalog Manager generates during MDIS import or MDIS export.

Unless you specify a full drive, path, and file name, the Information Catalog Manager places the file in the path specified on the DGWPATH environment variable. You must specify a fixed drive.

Example:

/LOGFILE d:\tagfile.log

/MDIS_EXPORT

Exports MDIS-conforming metadata into an MDIS-conforming tag language file with the name that you specify. Unless you specify the full drive, path, and file name, the Information Catalog Manager places the file in the path specified on the DGWPATH environment variable.

Example:

/MDIS_EXPORT d:\tagfile.tag

The information catalog from which you export MDIS metadata can contain metadata other than MDIS metadata, but /MDIS_EXPORT exports only metadata that conforms to MDIS.

/OBJECTS

This parameter is required.

Specifies the objects you want to export. Depending on the object type that you specified on the /OBJTYPE keyword, the name value is from three to five property values, separated by periods.

/OBJTYPE

/OBJECTS

Database

ServerName.DatabaseName.OwnerName

Dimension

ServerName.DatabaseName.OwnerName.DimensionName

Subschema

ServerName.DatabaseName.OwnerName.SubschemaName

Record

ServerName.DatabaseName.OwnerName.RecordName

Element

ServerName.DatabaseName.OwnerName.RecordName.ElementName

In this list, the parts of the name are represented with their MDIS name. To find the equivalent information catalog names, see Data Warehouse Center Application Integration Guide, available from the Data Warehouse Center Web site at http://www.software.ibm.com/data/vw/.

/OBJTYPE

This is a required parameter.

Specifies one of the following MDIS object types that you want to export:

Database

Dimension

Subschema

Record

Element

The object type name is not case sensitive.

Example:

/MDIS_EXPORT d:\tagfile.tag /OBJTYPE record

/PASSWORD

Your password for this user ID.

Example:

/PASSWORD secret

Passwords are case-sensitive for accessing databases on the following operating systems, you must type them exactly as specified.

• AIX
• Windows NT and Windows 2000
• Solaris Operating Environment

/TRACE

The level of trace information to send to the Information Catalog Manager trace file. Each higher level includes the functions of the levels below it (for example 3 includes the functions of levels 0, 1, 2, and 3). You might need to specify a higher level if you call IBM Software Support to diagnose the Information Catalog Manager problems.

0

The default. Level includes all messages and warning, error, and severe error conditions.

1

Includes entry and exit records of the highest level Information Catalog Manager functions.

2

Includes extremely granular entry and exit records of the Information Catalog Manager functions.

3

Includes input and output parameters (that exclude input or output structures).

4

Includes all input or output structures that are passed to and used by the Information Catalog Manager.

/USERID

Your information catalog user ID. Type the user ID required by the database where the information catalog resides. For example, the user ID might be your local, LAN, AS/400, AIX, or OS/390 TSO user ID.

Example:

/USERID longods