Create Table -- Fields and controls

Table page



Table page

Edit routine
Validate routine
Audit
Encoding scheme
Specify

Edit routine

Type the name of the program that you want to be the edit routine for the table; for example, 

DSN8EAE1
The edit routine, which must be provided by the current server's site, is invoked during the execution of LOAD, INSERT, UPDATE, and all row retrieval operations on the table. An edit routine receives the table row in internal DB2 format and transforms the row when it is stored by an INSERT, UPDATE, or LOAD operation. During retrieval operations, it transforms the row back to its original form. Typical uses are to compress the storage representation of rows to save space on DASD and to encrypt data.

Validate routine

Type the name of the program that you want to be the validation exit routine for the table; for example, 

EMPLNEWE
The validation routine can inhibit a LOAD, INSERT, UPDATE, or DELETE operation on any row of the table. Before the operation takes place, the row is passed to the procedure. After examining the row, the procedure returns a value that indicates whether the operation can proceed.

Audit

Use this box to specify the type of access to this table that causes auditing to be performed.

Auditing is usually part of your overall security plan for keeping your DB2 system secure. You can use auditing to determine if attempts are made to gain unauthorized access to the table and who accessed the table data.

The audit type can be one of:

NONE
No auditing is done when the table is accessed.
CHANGES
Auditing is done when the table is accessed during the first INSERT, UPDATE, or DELETE performed by each unit of work. However, the auditing is done only if the appropriate audit trace class is active.
ALL
Auditing is done when the table is accessed during the first operation of any kind performed by each unit of work of a utility or application process. However, the auditing is done only if the appropriate audit trace class is active and only if the access is not performed with COPY, RECOVER, REPAIR, or any stand-alone utility.

Encoding scheme

Use this box to specify the encoding scheme for data stored in the table. It must agree with the encoding scheme used by any table space that you specified in the Table space field. If no table space is specified, but an encoding scheme is specified here, a table space with this encoding scheme is created when the table is created. The encoding scheme can be one of:

System default
The table space's encoding scheme is used for the table. If table space does not have an encoding scheme specified, the database's encoding scheme is used. If the database does not have an encoding scheme specified, the default encoding scheme that was in place at installation time is used.
ASCII
The data must be encoded by using the ASCII coded character sets (CCSIDs) specified during installation.
EBCDIC
The data must be encoded by using the EBCDIC CCSIDs specified during installation.

If you do not specify an encoding scheme but specified an existing table space name in the Table space field, the encoding scheme used by the table space is used. If the table space does not have a specified encoding scheme, the database's encoding scheme is used. If the database does not have an encoding scheme, the default installation encoding scheme is used.

Specify

Select this radio button to identify the object identifier to be used for this table. An object identifier (OBID) is the identifier for an object's internal descriptor, and is required if the database for the table is defined as ROSHARE READ. When so defined, the current server is using shared read-only data to share the database as a reader.

When you select this radio button, you must type an integer for the OBID in the entry field; for example, 42. The integer must lie in the range from 1 to 32767.

If the database is not defined as ROSHARE READ, the integer you type in the entry field must not identify an existing or previously used OBID of the database. The OBIDs for the tables in a database can be retrieved from the SYSIBM.SYSTABLES table. For example, this statement queries the OBID of DON.EMP: 

SELECT OBID FROM SYSIBM.SYSTABLES
   WHERE CREATOR='DON' AND
   NAME='EMP';