These steps are part of the larger task of creating a table. When
you complete the steps for defining table properties, return to
Creating a table.
-
Optional: In the Table owner box, specify the user identifier
to own the table
that you're creating. If you do not specify a name, the DB2 subsystem user
identifier that is used for this connection to the DB2 subsystem
is used.
-
In the Table name field, type a 1- to 18-character name for the
new table. The combination of the table owner and table name must
be unique in the DB2 subsystem.
-
Optional: In the Table space box, specify the table space in
which to create the table. This table space must not be a partitioned table
space that already contains a table. If you specify a partitioned table space,
you cannot load or use the table until its partitioned index is created.
If you specify a table space, the table space must belong to the database
in the Control Center under which you are creating the table. If you do
not specify a table space, a table space is implicitly created in the database.
The name of the table space is derived from the table name.
-
Optional: In the Edit
routine field, type the name of the program to be used as the edit
routine for the table. Edit routines are typically used to compress the
storage representation of rows to save space on DASD and to encrypt the
data.
-
Optional: In the Validate
routine field, type the name of the program to be used as the validation
exit routine for the table. Validation routines are typically used to impose
limits on the information that can be entered in a table; for example,
allowable salary ranges.
-
Optional: Use the Audit
box to specify which types of access operations on this table will cause
auditing to be performed. The default (None) specifies that no auditing
is done when this table is accessed.
Auditing is usually part of your overall security plan for keeping your
DB2 system secure. You can use auditing to determine if attempts
are to gain
unauthorized access to the table and who accessed the table data.
-
Optional: Use the Encoding
scheme box to specify the encoding scheme for data stored in the
table. If you specified a table space in the Table space field,
the encoding scheme you choose must agree with the encoding scheme already
in use for that table space. If you did not specify a table space name,
a table space with the encoding scheme that you specify here is also created
when the table is created.
-
Optional: If you want to specify an object identifier (OBID) for
this table, select
the Specify
radio button and type an
integer for the OBID in the entry field. If you want DB2
to generate an OBID for this table, select Default.
An OBID is the
identifier for an object's internal descriptor. The
integer must not identify an existing or previously used
OBID of the database, and must be in the range from 1 to 32767.
If the database
for the table is defined as ROSHARE READ, you must specify an object identifier.
-
If you want to prevent the table from being dropped, select the Restrict
on drop check box. If you select this check box, the table can be dropped
only after it is altered to remove the restriction. In addition, the database
and table space that contain the table cannot be dropped while the
restriction is in place.
-
If you plan to use this table for replication, select the Data capture check box.
If selected, data changes to this table
are written to the log in an expanded format.
-
Optional: In the Comment box, type a 1- to 254-character description
for this table.
