Before you begin
This task requires that you configure a database and make it available. See the "Creating DB2 for z/OS databases for schedulers" topic for more information.
Why and when to perform this task
This topic describes how to create tables for a scheduler on a DB2 for z/OS database using data definition language (DDL) or structured query language (SQL) files.Steps for this task
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, remember 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.
db2 connect to subsystem user userid using password
Result
The DB2 for z/OS tables and schema for the scheduler exist.Related tasks
Creating DB2 for z/OS databases for schedulers
Related reference
Vendor-specific data sources minimum required settings