Creating databases in the DB2 for z/OS subsystem

You can use the BPMConfig script to generate the database scripts that are required to create the databases for the IBM® Business Process Manager components.
You can use various tools to run these database scripts:
  • The createDatabase.sh script, which was additionally created with the database scripts
  • Tools such as the DB2® command line processor, SPUFI, or DSNTEP2

Choosing which tool to use

You can choose one tool over another based on experience and familiarity, or personal preference. Your organization might also have implemented standards or conventions for the tools that are used to create DB2 for z/OS® objects, particularly in a production environment.

Considerations for choosing the createDatabase.sh script

  • createDatabase.sh can create all your database objects in a single execution of the tool, for each database to be created. Therefore, using this script is a good choice if this is your first server implementation.
  • createDatabase.sh runs the database scripts that the BPMConfig script generates.
  • createDatabase.sh runs the SQL for each component in the correct sequence.
  • createDatabase.sh creates database objects according to a naming convention that you define.
  • createDatabase.sh organizes the layout of database objects across DB2 for z/OS databases.
  • createDatabase.sh issues GRANT permissions to database, storage group, and buffer pool objects.
  • createDatabase.sh runs in a UNIX System Services environment.
  • createDatabase.sh produces an audit trail of the objects that it creates.

Considerations for choosing other tools

  • You might prefer to use the DB2 command line processor to run the SQL statements in the UNIX Systems Services environment.
  • There is no restriction on the naming or organization conventions that apply to the database objects other than the standard database subsystem restrictions.
  • Some tools can be run from a z/OS environment.
  • The tools can produce an audit trail of the DB2 database commands that have been issued.
Restriction: The SQL files that you need to run are in ASCII format. If you intend to use tools like the SQL processor using file input facility (SPUFI) or DSNTEP2 to run the SQL statements, some manual effort might be required to reformat SQL statements that exceed 71 characters in length after EBCDIC conversion. You can use the lineLength.sh utility to help you identify and fix SQL statements that exceed 71 characters in length.
Parent topic: Creating and configuring DB2 for z/OS databases after network deployment profile creation