Space announcements

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Old objects data set syntax

Note

OLD OBJECTS is deprecated with PTF BQU2282.

To direct Log Master to read an old objects data set as input, use the appropriate syntax of the OPTION statement.

For more information about the OPTION syntax, see OLD OBJECTS dataSetName. For more information about the old objects data set, see the LOGSCAN statement.

The following figure shows the syntax used within the old objects data set.


Log Master can read descriptions of DB2 objects that are no longer in the DB2 catalog from an old objects data set. The basic syntax is similar to the DB2 syntax for a CREATE TABLE statement. Notice that the old objects data set syntax precedes the actual DDL that created the table (createTableDDL).

The n values used with the CCSID keyword represent coded character set IDs, (in order, a single-byte character set ID, a double-byte character set ID, or a mixed/graphic CCSID).

You can repeat the old objects definition syntax as many times as necessary to define multiple objects in a single old objects data set. In addition, you can use the UNIQUE or PRIMARY KEY clause of the CREATE TABLE data definition language (DDL) statement to associate an index with a table definition. The index name is tbcreator.OLDINDEX. To allow for ascending or descending columns in the index, Log Master supports the optional keywords ASC or DESC after each column in the UNIQUE or PRIMARY KEY clause.



Was this page helpful? Yes No Submitting... Thank you

Comments