The sibDDLGenerator command
generates the DDL statements needed to create the DBMS (Database Management
System) resources used by the messaging engine.
Syntax

>>-sibDDLGenerator--+---------------------+--------------------->
'- -system--DBMS name-'
>--+-------------------------+--+---------------------------+--->
'- -version--DBMS version-' '- -platform--DBMS platform-'
>--+-----------------------+--+-------------------+------------->
'- -schema--schema name-' '- -user--user name-'
>--+----------+--+----------------------+----------------------->
+- -create-+ '- -database--database-'
'- -drop---'
>--+-------------------------------+---------------------------->
'- -storagegroup--storage group-'
>--+---------------------------+-------------------------------->
'- -bufferpool--buffer pool-'
>--+-------------------------------+--+----------------+-------->
'- -statementend--statement end-' '- -nolinebreaks-'
>--+----------------+--+-------------------------+-------------->
'- -noblanklines-' '- -firstline--first line-'
>--+-----------------------+-----------------------------------><
'- -lastline--last line-'
Purpose
A messaging engine needs
DBMS resources, such as database tables, which it can create when starting.
If your installation has a policy that only a database administrator has the
authority to create database tables, use the sibDDLGenerator command
to enable your database administrator to create the DBMS resources that the messaging engine needs. The sibDDLGenerator command
generates the DDL statements that your database administrator can save, and
later process, to create the DBMS resources that are listed in Data store tables.
The command also generates DDL statements
that grant the appropriate authorities to use these tables.
Note: the SIBDDLGenerator is able to generate the
DDL statements for creating or dropping all of the data store’s
tables. It is less well suited for adding more item tables to an existing data store. However, it is possible
to reissue the DDL statements to create existing tables without harming the data store.
Optional parameters
Tip: The sibDDLGenerator command
is case-sensitive. For example, the parameter Oracle is
not the same as oracle.
Some parameters apply
to a specific DBMS only, as indicated in the parameter list; for example: -database
[Applies only to DB2 for z/OS]
- -system
- Identifies the type of DBMS on which the administrator will process the
DDL statements. Valid values are:
- db2
- oracle
- sqlserver
- sybase
- informix
- derby
- cloudscape
If you do not supply a -system parameter,
the default value is derby
- -version
- The version number of the DBMS identified by -system.
If you do not supply a -version parameter, the default
value is that shown in the following table.
system |
platform |
default version |
other supported versions |
db2 |
zos |
7.1 |
8.1 |
db2 |
unix, windows |
8.1 |
|
db2 |
iseries |
5.2 (see Note 1) |
5.3 (see Note 1) |
oracle |
– |
8i |
9i, 10g |
sqlserver |
– |
2000 |
|
sybase |
– |
12.0 |
12.5 |
informix |
– |
9.3 |
7.3, 9.4 |
derby |
– |
5.1 |
|
Note: - For iSeries, the DB2 database is part of the operating system, so the
version number given is for the OS/400 version.
- -platform
- The operating system platform on which the DBMS runs. Valid values are:
- -schema
- The name of the schema that contains all the objects used by the messaging engine.
If you do not supply a -schema parameter, the default
value is IBMWSSIB.
- -user
- The name of the user ID that is used to interact with the DBMS. If you
do not supply a -user parameter, the default value is IBMUSER.
- -create | -drop
- Indicates whether the DDL statements create the DBMS resources or delete
them. If you do not supply either parameter, the default value is -create.
- -database [Applies only to DB2 for z/OS]
- The name of the database that is allocated for the messaging engine tables.
If you do not supply a -database parameter, the default
value is SIBDB.
- -storagegroup [Applies only to DB2 for z/OS]
- The name of the storage group that is allocated for the messaging engine tables.
If you do not supply a -storagegroup parameter, the default
value is SIBSG.
- -bufferpool [Applies only to DB2 for z/OS]
- The name of the buffer pool that is allocated for the messaging engine tables.
If you do not supply a -bufferpool parameter, the default
value is BP1.
- -statementend
- Appends statement end to each DDL statement. For example,
you can use ; to append a semicolon to each DDL statement.
By default, the sibDDLGenerator command appends nothing
to each statement.
Tip: On UNIX platforms, escape the semicolon
to prevent the shell from interpreting it.
- -nolinebreaks
- Places each statement on a single line, with no line breaks. By default,
the sibDDLGenerator command breaks statements across lines
to improve readability.
- -noblanklines
- Omits blank lines between each statement. By default, the sibDDLGenerator command
inserts a blank line between each statement to improve readability.
- -firstline
- Generates first line as the first line of output. For
example, you can use first line to identify the target
database. By default, the sibDDLGenerator command does
not generate a first line.
- -lastline
- Generates last line as the last line of output. For
example, you can use last line to invoke a command that
executes the commands in the script. By default, the sibDDLGenerator command
does not generate a last line.
Tip: The optional parameters that control the format
of the DDL statements, for example -statementend, enable
you to generate output that is suitable for particular scripting tools, for
example the DB2 CLP. By default, the sibDDLGenerator command
generates blank lines between each DDL statement but does not append a semicolon
at the end of each DDL statement.
Examples
- sibDDLGenerator -system db2 -version 8.1 -platform zos
Generates DDL statements for DB2 8.1, running on z/OS, with a default
schema, user ID, database, storage group, and buffer pool.
- sibDDLGenerator -system db2 -version 8.1 -platform windows -statementend ;
Generates DDL statements
for DB2 8.1, running on Windows, with a default schema, user ID, and database.
You can input the statements directly to the DB2 CLP, which requires that
each statement is terminated with a semicolon.
- sibDDLGenerator -system oracle -version 8i -schema SIB -user fred
Generates DDL statements for Oracle
8i.
- sibDDLGenerator -system oracle -schema SIB -user fred
A concise version of the preceding example.