A database administrator must run a script to create a set of tablespaces required for the content store database. The script must be modified to replace the placeholder parameters with ones that are appropriate for your environment.
Ensure that you use the naming conventions for DB2 on z/OS. For example, all names of parameters must start with a letter and the length must not exceed eight characters. For more information, see the IBM DB2 Information Center.
Connect to the database as a user with privileges to create and drop tablespaces and to allow execution of SQL statements.
Open the tablespace_db2zOS.sql script file and use the following table to help you to replace the generic parameters with ones appropriate for your environment.
Not all of the parameters listed are in the script, but may be added in the future.
Parameter Name | Description |
CMSCRIPT_CREATE_IN | Specifies the base tables location For example, databaseName.baseTablespaceName |
CMSCRIPT_STOGROUP | Specifies the name of the storage group. |
CMSCRIPT_DATABASE | Specifies the name of the content store database. |
CMSCRIPT_CS_ID | Specifies the instance identification for the content store database. The ID must not be longer than two characters. |
CMSCRIPT_TABLESPACE | Specifies the name of the tablespace that will contain all of the base tables in the content store. Auxiliary tables are not included. The name cannot be longer than six characters. |
CMSCRIPT_LARGE_BP | Specifies the name of the large buffer pool allocated for especially large objects. |
CMSCRIPT_REGULAR_BP | Specifies the name of the regular size buffer pool allocated for regular and large objects. |
CMSCRIPT_USERNAME | Specifies the user account that accesses the content store database. |
Save and run the script.
Grant the IBM Cognos user rights to the tablespaces that were created when you ran the tablespace_db2zOS.sql file script:
In the remote access tool, open the rightsGrant_db2zOS.sql script file and replace the placeholder parameters with values that are appropriate for your environment.
Tip: Ensure that you use the same values that you used when you allocated resources to the buffer pools and user account.
Save and run the file.
The content store database is created. You can now configure a database connection.