Reading the Q.OBJECT__DATA table

This table contains one or more rows for each query, form, and procedure in the database. Each row contains all or part of the defining text for one of these objects. Objects are reconstructed from this text by combining the text with the corresponding format number in the OBJECTLEVEL column of the Q.OBJECT__DIRECTORY table.

The Q.OBJECT__DATA table has the index Q.OBJECT__OBJDATAX, with attributes UNIQUE and CLUSTER. Keyed columns are OWNER, NAME, and SEQ.

The table has the structure shown in Table 55:

Table 55. Structure of the Q.OBJECT__DATA table
Column name Data type Length (bytes) Nulls allowed? Function/values
OWNER CHAR 8 No Shows the authorization ID of the creator of the object.
NAME VARCHAR 18 No Shows the name of the object.
TYPE CHAR 8 No Shows the type of object: FORM, PROC, or QUERY.
SEQ SMALLINT 2 No Indicates the sequence that this text occupies within the entire text of the object. For example, if this row is the first row of text in the object, SEQ is 1; if it is the second, SEQ is 2, and so on.
APPLDATA LONG VARCHAR FOR BIT DATA (see note) 3600 (see note) Yes Contains all or part of text that defines the object. Text appears in an internal QMF format. The OBJECTLEVEL column in Q.OBJECT__DIRECTORY defines this format.
Attention: The APPLDATA column must never be subjected to code page (CCSID) conversion.

Note: With DataJoiner Version 1.2.1 and DB2 for AIX, Parallel Edition Version 1.2, the data type and length for APPLDATA are VARCHAR(3600) for bit data. This is a permanent restriction for Version 1 SQL databases.

Workstation database server users:For DB2 Common Server, there is a similar table, Q.OBJECT_DATA2. This table is required for internal QMF processing of a SAVE or IMPORT command.

[ Previous Page | Next Page | Contents | Index ]