Define and generate the database name table using the steps listed as follows.
The database name table must exist as a module in a load library in order to be usable by the runtime system. The name of the load module assigned in the link-edit must match the name specified in the DMCL.
|
Action |
Statement |
|---|---|
|
Create the database name table, adding DBTABLE mappings to define a default dictionary and for non-SQL applications binding without a DBNAME |
CREATE DBTABLE |
|
Create the database names, adding the segments and subschema mappings required by your applications |
CREATE DBNAME |
|
Generate the database name table |
GENERATE DBTABLE |
|
Associate the database name table with a DMCL |
ALTER DMCL |
|
Punch the database name table load module and link-edit it to a load library |
PUNCH DBTABLE LOAD MODULE |
The example below defines a basic database name table that is suitable if all non-dictionary segments in your runtime environment are in the same page group and have unique area names.
It has the following characteristics:
create dbtable alldbs
subschema idmsnwk? maps to idmsnwk? dbname defdict
subschema ???????? maps to ???????? dbname defdb;
create dbname system
segment catsys
segment system
segment sysmsg;
create dbname defdict
segment defdict
segment defcat ◄-- for SQL users
segment sysmsg;
create dbname defdb
segment user-segment1
segment user-segment2
.
.
.
generate dbtable alldbs;
|
Copyright © 2014 CA.
All rights reserved.
|
|