Generating the DDL statements needed to create or alter data store tables

To enable the database administrator to create or alter the data store tables manually, generate DDL statements.

Before starting, review the information in Configuration planning for a messaging engine to use a data store, and ensure that the database administrator has taken any appropriate action.

Use the sibDDLGenerator command to generate the DDL statements that the database administrator needs to create the tables for the messaging engine data store. Use the sibDBUpgrade command to generate the DDL statements that the database administrator needs to alter the tables for the messaging engine data store.

1. At a command prompt, issue the sibDDLGenerator to create or sibDBUpgrade command to alter the data store tables and redirect the output to a file. For information on these command-line utilities, refer to sibDDLGenerator command and sibDBUpgrade command.

   Important: To process the DDL statements with a command line processor that requires the statements to conform to a specific format, use the optional parameters that control the format of the DDL statements. For example, if each statement must end with a semicolon, use -statementend ;

   (iseries) To access the IBM i command line, or run an IBM i command line program, use the STRQSH command to start a Qshell session. For more information, see Configure Qshell to run WebSphere scripts .

2. Send the output file to the database administrator to process the DDL statements that are generated. The DDL statements can be ported across operating systems, for example, we can generate the DDL statements on a machine running the Windows operating system and then run them on a machine running the z/OS operating system.

   (zos) The DDL statements can be processed by using SPUFI.

   • Your database administrator can modify the DDL statements, but must not modify the table names or the column names in any way because doing so might prevent the messaging engine from starting.

   • If the DDL statements are to be run on the z/OS operating system, the database administrator must change the VCAT name in the first line of the DDL statements (the create storage group statement) to a valid high-level qualifier for their system.

   • Service integration bus does not support padded values in the XID column of the SIBXACTS table. Hence, any database parameter setting that might add padded values to the column must not be applied to the database.

     For example, changing the value of the RETVLCFK DB2 parameter from NO to YES might introduce padded values.

     For more information about the RETVLCFK parameter, see VARCHAR FROM INDEX field (RETVLCFK subsystem parameter) in the DB2 information center.

Related tasks

Migrate a messaging engine based on a data store

sibDDLGenerator command

Data store tables

sibDBUpgrade command

Altered database tables