If you are a system administrator at a DB2 site, you might prefer to create the extended attribute system tables outside PowerBuilder for two reasons:
The first user to connect to the DB2 database using PowerBuilder might not have the proper authority to create tables.
When PowerBuilder creates the extended attribute system tables, it places them in the default tablespace. This might not be appropriate for your needs.
When using the DirectConnect interface
You must create the extended attribute
system tables outside PowerBuilder if you are using the DirectConnect
interface. You need to decide which database and tablespace should
store the system tables. You might also want to grant update privileges
only to specific developers or groups.
To create the extended attribute system tables, you run the DB2SYSPB.SQL script outside PowerBuilder. This script contains SQL commands that create and initialize the system tables with the table owner and tablespace you specify.
The DB2SYSPB.SQL script is in the Server directory on the PowerBuilder CD-ROM. This directory contains server-side installation components and is not installed with PowerBuilder on your computer.
You can access the DB2SYSPB.SQL script directly from your computer’s CD-ROM drive or you can copy it to your computer.
Use the following procedure from the database server to create the extended attribute system tables in a DB2 database outside PowerBuilder. This procedure assumes you are accessing the DB2SYSPB.SQL script from the product CD in your computer’s CD-ROM drive and the drive letter is Z.
To create the extended attribute system tables
in a DB2 database outside PowerBuilder:
Log in to the database server or gateway as the system administrator.
Insert the PowerBuilder CD-ROM into the computer’s CD-ROM drive.
Use any text editor to modify Z:\Server\DB2SYSPB.SQL for your environment. You can do any of the following:
Change all instances of PBOwner to another name.
Change all instances of database.tablespace to the appropriate value.
Add appropriate SQL statement delimiters for the tool you are using to run the script.
Remove comments and blank lines if necessary.
Save any changes you made to the DB2SYSPB.SQL script.
Execute the DB2SYSPB.SQL script from the database server or gateway using the SQL tool of your choice.
