Creating databases in DB2 on z/OS
The ArcSDE implementation on DB2 z/OS requires at least two DB2 databases within the spatially-enabled database subsystem: one to store the ArcSDE geodatabase repository and one to store user data. Together, the database with the ArcSDE geodatabase repository and the database or databases containing the user data make up one geodatabase. Therefore, these databases must be created before you can set up the ArcSDE geodatabase.
The JCL script, ESRIUDFI, is provided to create databases and UDFs for ArcSDE. This script is installed to the tools folder of SDEHOME. You must customize the ESRIUDFI script using information specific to your implementation, then upload and run the script on z/OS. The script itself includes instructions to create two databases.
To customize ESRIUDFI, refer to the instructions in the JCL script and carefully check the following:
- In the body of ESRIUDFI, there are several strings that need to be replaced with the corresponding user environment parameters. Details of the meaning of each string and how to replace them are explained at the top of the ESRIUDFI script.
Step ESRIS1 of the JCL script creates two databases and sets the collation. To use these lines, you must uncomment them and provide names and collations for the databases. An example for this is as follows:
CREATE DATABASE SDEDBR00 CCSID UNICODE; CREATE DATABASE SDEDBU00 CCSID UNICODE;Note:
The name of a database used to store a geodatabase cannot contain special characters.
- The database subsystem must be spatially enabled. See the DB2 z/OS documentation for instructions on how to do this.
Optionally, you can create a storage group for managing the ArcSDE data more efficiently. You need to create a storage group first, so you must add an additional line to the ESRIUDFI script, as shown in this example:
CREATE STOGROUP ARCSDE VOLUMES (VOL1, VOL2, …) VCAT SDECAT; CREATE DATABASE SDEDBR00 CCSID UNICODE STOGROUP ARCSDE; CREATE DATABASE SDEDBU00 CCSID UNICODE STOGROUP ARCSDE;Note:
Additional user privileges need to be authorized if you use a storage group. See Granting permissions and privileges to sde and the ArcGIS users group in DB2 on z/OS for more information.
Once you have finished customizing the ESRIUDFI script, you need to submit it on your target machine.
When the ESRI UDF installation job has completed, you will notice that during the last step, the package binding and creation of the SDE.SDE_UPDT_LMOD procedure were successful but had warnings. These warnings are due to the fact that the ArcSDE geodatabase system tables have not yet been created in the database. You can ignore these warnings, because when you run the sdesetup command, the tables will be created and the package object will be autobound when it is referenced by sdesetup.
- Spatially-enable the database subsystem. See the IBM DB2 z/OS documentation for instructions.