Run the job to create the Output Manager database
Your Db2® installation might have multiple instances of Db2 running. Before attempting to execute the Output Manager DDL, check with your Db2 system administrator to verify that you have the proper authority to do so. Additionally, ask your Db2 system administrator which subsystem you should use. Each Db2 installation is likely to have unique conventions regarding DDL execution, tracking, and management.
If your Db2 security policies require GRANTs for specific table privileges, edit SBJTSAMP member BJT@TBCR to implement security settings on the database and the tables. Uncomment the DD statement in BJT@JCDB to issue the GRANTs in BJT@TBGR.
You can use either of the following approaches to execute the DDL:
- Submit job BJT@JCDB to execute the SQL statements to create the database, table spaces, tables and indexes. Uncomment the DD statement for BJT@TBGR if your site security policies require privileges to be defined for each user.
- Submit each DDL member individually with SPUFI. Run in the following order: BJT@DBCR, BJT@TSC1, BJT@TBCR, BJT@INCR, and then BJT@TBVO. Run BJT@TBGR if your site security policies require privileges to be defined for each user.
Note: Do not change the index definitions in BJT@INCR except to change parameters such as STOGROUP, PRIQTY, and SECQTY. The columns, column order, and whether ASC or DESC have been tuned in conjunction with the queries issued by the ITOM programs to ensure queries are index-only and avoid table scans, creation of work files, and external sorts wherever possible.