Creating a DB2 for z/OS database for scheduler

Why and when to perform this task

This topic describes how to create a DB2 for z/OS database for the scheduler and how to verify that it is reachable from the application server machine.

Steps for this task

  1. You must have already installed on a UNIX or Windows machine.
  2. On the z/OS machine that hosts the database:
    1. Log on to the native z/OS environment.
    2. If multiple DB2 systems are installed, then decide which subsystem you want to use.
    3. Make a note of the Internet Protocol (IP) port to which the DB2 subsystem is listening.
    4. Using the DB2 administration menu, create a new database named SCHEDDB, for example. Note the database name.
    5. Create a storage group and note the name.
    6. Decide which user ID is used to connect to the database from the remote machine running the product. Normally, for security reasons, this user ID is not the one you used to create the database.
    7. Grant the user ID the rights to access the database and storage group. The user ID must also have permission to create new tables for the database.
  3. On the server machine:
    1. Make sure that you have DB2 Connect Gateway (Version 8.1 fix pack 3 or higher) installed. This component is part of the DB2 UDB ESE package, however, you can also install it separately.
    2. Catalog the remote database using the following commands, either in a script or in a DB2 command line window:
      catalog tcpip node zosnode remote hostname server IP_port ostype mvs;
      catalog database subsystem as subsystem at node zosnode authentication dcs;
      catalog dcs database subsystem as subsystem parms ',,INTERRUPT_ENABLED'
      An important difference exists between DB2 UDB and DB2 for z/OS. DB2 UDB does not have the concept of a subsystem, but DB2 for z/OS does have subsystems. To avoid confusion between Database name and Subsystem name, it is important to understand that because DB2 for z/OS runs in a subsystem, the catalog node and catalog database commands must identify the appropriate subsystem. On DB2 UDB, the subsystem name is not a known concept, and the database name to which it connects is actually the name of the DB2 for z/OS subsystem.
    3. Verify that you can establish a connection to the remote subsystem by entering the following command:
      db2 connect to subsystem user userid using password
    4. Change to the Scheduler subdirectory in the application server installation root directory.
    5. Edit the createTablespaceDB2ZOS.ddl script. Replace @STG@ with the storage group name. Replace @DBNAME@ with the database name (not the subsystem name), and replace @SCHED_TABLESPACE@ with the name of a valid tablespace.
    6. Run your customized version of createTablespaceDB2ZOS.ddl, as described in the header of the script.
      If this script does not work, or if you want to remove the tablespace, edit and run the dropTablespaceDB2ZOS.ddl script.
    7. Edit the createSchemaDB2ZOS.ddl script. Replace @STG@ with the storage group name. Replace @DBNAME@ with the database name (not the subsystem name). Replace @TABLE_PREFIX@ with the Table Prefix in the configured scheduler resource, and replace @SCHED_TABLESPACE@ with a valid tablespace that was created by the createTablespaceDB2ZOS.ddl script.
    8. Run your customized version of the createSchemaDB2ZOS.ddl script, as described in the header of the script.
      If this script does not work, or if you want to remove the tables and views, use dropSchemaDB2ZOS.ddl to drop the schema.
    9. To avoid deadlocks, verify that the DB2_RR_TO_RS DB2 flag is set to YES. If necessary, restart the DB2 instance to activate the change.

Results

The DB2 for z/OS database for the scheduler service is created.



Searchable topic ID:   tsch_codb2forz
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/scheduler/tasks/tsch_codb2forz.html

Library | Support | Terms of Use | Feedback