Installation Guide: ArcSDE for IBM DB2 on...

ArcGIS®

9Installation Guide: ArcSDE® for IBM® DB2® on z/OS®

Copyright © 2008 ESRI All Rights Reserved. Printed in the United States of America.

The information contained in this document is the exclusive property of ESRI. This work is protected under United States copyright law and the copyright laws of the given countries of origin and applicable international laws, treaties, and/or conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying or recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI. All requests should be sent to Attention: Contracts Manager, ESRI, 380 New York Street, Redlands, CA 92373, USA.

The information contained in this document is subject to change without notice.

RESTRICTED/LIMITED RIGHTS LEGEND

U.S. Government Restricted/Limited Rights: Any software, documentation, and/or data delivered hereunder is subject to the terms of the License Agreement. In no event shall the Government acquire greater than RESTRICTED/LIMITED RIGHTS. At a minimum, use, duplication, or disclosure by the Government is subject to restrictions as set forth in FAR §52.227-14 Alternates I, II, and III (JUN 1987); FAR §52.227-19 (JUN 1987); and/or FAR §12.211/12.212 [Commercial Technical Data/Computer Software]; DFARS §252.227-7015 (NOV 1995) [Technical Data]; and/or DFARS §227.7202 [Computer Software], as applicable. Contractor/Manufacturer is ESRI, 380 New York Street, Redlands, CA 92373-8100, USA. ESRI, MapObjects, ArcView, ArcIMS, ArcSDE, ArcInfo, ArcEditor, ArcGIS, ArcMap, ArcCatalog, ArcToolbox, ArcObjects, MapObjects, SDE, and the ESRI globe logo are trademarks of ESRI, registered in the United States and the European Community, or certain other jurisdictions. www.esri.com is a service mark of ESRI. The names of other companies and products mentioned herein are trademarks or registered trademarks of their respective trademark owners.

iii

Table Of Contents Introduction .................................................................................................. 5

System requirements for ArcSDE for DB2 on z/OS .............................................. 6

Installation and configuration........................................................................... 7

ArcSDE for DB2 z/OS installation overview...................................................... 7

Installing the ArcSDE component for DB2 for z/OS ........................................... 8

Configuring DB2 for z/OS ............................................................................. 9

Configuration of the DB2 for z/OS subsystem ............................................... 9

Creating an ArcSDE geodatabase in DB2 for z/OS ...........................................15

ArcSDE authorization ..................................................................................20

Multiple installations on the same machine.....................................................21

Uninstalling ArcSDE for DB2 for z/OS ...............................................................22

5

Introduction This installation guide includes instructions for installation and setup of ArcSDE® for IBM® DB2® on the IBM Z series mainframe operating system (z/OS®). The ArcSDE component is installed on a Microsoft® Windows® machine that is a client to the DB2 z/OS database subsystem.

For guidelines on optimizing both your DB2 and ArcSDE configurations, see the topics in the Geodatabases and ArcSDE/Administering ArcSDE geodatabases section of the ArcGIS Server help prior to installing the ArcSDE component of ArcGIS Server Enterprise. These topics can be accessed from the ESRI support site.

Each ArcSDE disk contains:

• Directories named for each platform, which contain directories named for each supported database implementation (e.g. ArcSDEDB2 or ArcSDEDB2zOS)—Each ArcSDE<DBMS> directory contains the installation files specific to that database.

• Directories named documentation_server and documentation_sdk—These contain the ArcSDE Developer Help, the administration command references documentation, and installation guides. The installation guides are not installed, so if you want these to be on your computer, you must copy them from the installation media to disk.

The installation of ArcSDE for DB2 for z/OS is a three step process.

1. Install your DBMS and configure it and the server for ArcSDE.

2. Install the ArcSDE component for DB2 z/OS.

3. Perform the postinstallation setup. After you define the SDE user environment, the postinstallation setup creates or upgrades the geodatabase repository, authorizes the ArcSDE component, and creates the ArcSDE service.

On Windows, the ArcSDE setup program will install the Microsoft Windows Installer if required, before continuing with the ArcSDE for DB2 z/OS installation. After ArcSDE for DB2 z/OS is installed, you will manually perform the postinstallation setup of the ArcSDE geodatabase.

Installation Guide: ArcSDE for DB2 z/OS

6

System requirements for ArcSDE for DB2 on z/OS The installation of the ArcSDE component for DB2 on IBM z/OS requires:

• IBM DB2 9.1 for z/OS

• IBM Spatial Support for DB2 for z/OS

• Required DB2 Authorized Program Analysis Report (APAR) fixes for spatial support

• A Windows client machine with the DB2 Connect Version 9.1, fix pack 2 level or later installed, which includes the DB2 Control Center application.

• The version of the operating system on the Windows machine should meet both the ArcGIS Server Enterprise 9.3 and DB2 Connect 9.1 system requirements.

For DB2 for z/OS installation requirements, consult the IBM DB2 for z/OS documentation.

Uninstalling ArcSDE from z/OS

7

Installation and configuration

ArcSDE for DB2 z/OS installation overview

You will be running ArcSDE remotely from a Windows computer connecting to the DB2 database subsystem on z/OS; therefore, you will install ArcSDE for DB2 z/OS on the client machine.

You must install and create your DB2 for z/OS subsystem, enable it for spatial support, and install any Authorized Program Analysis Report (APAR) fixes needed for spatial support. Consult your IBM DB2 for z/OS documentation for instructions on how to do this.

The following is a summary of the steps you need to perform to successfully install the ArcSDE component to use with DB2 for z/OS and create a geodatabase. Detailed instructions for each step are included in other topics in this guide.

1. Install the ArcSDE component.

2. Configure the ZPARMs on DB2 and refresh DB2 with the setting.

3. Use the Resource Access Control Facility (RACF) to create a user, SDE, for ArcSDE administration. To simplify the user privilege authorization, it is highly recommended you enable secondary authorization IDs (RACF groups).

4. Transfer z/OS specific files to the target Multiple Virtual Storage (MVS) system.

5. Submit the JCL script, ESRIUDFI, to create the storage groups, databases, and user defined functions (UDFs) for ArcSDE.

6. Grant privileges to the SDE user and ArcSDE user group on DB2.

7. Alter configuration files, run sdesetup.exe, and authorize the ArcSDE component from the ArcSDE client.

8. Submit the JCL script, ESRIUDFB, that binds the DBRMs required to run the ESRI UDFs.

9. Verify the installation.

10. Create ArcSDE users for the usage of ArcSDE and ArcGIS applications.


8

Installing the ArcSDE component for DB2 for z/OS

You will install the ArcSDE component of ArcGIS Server Enterprise on a Windows machine that is a client to the DB2 for z/OS subsystem.

Make sure the SDE user, which was created during step 2 of the DB2 z/OS configuration stage of the setup, is used to install the ArcSDE component and has write permissions to the installation directory.

1. Place the ArcSDE component media into the drive on your Windows client computer.

2. The installation options dialog box should open automatically. Choose the ArcSDE for DB2 z/OS setup to run the client installation wizard.

If the installation options dialog box does not open, open Windows Explorer, navigate to your DVD drive, double-click the ESRI.exe, and choose the ArcSDE DB2 z/OS setup.

3. Read the information on the Welcome dialog box and click Next.

4. Read and accept the license agreement and click Next. If you do not accept the license agreement, the installation terminates.

5. Browse to the destination folder for the ArcSDE files or accept the default and click Next.

6. Click Next to start the ArcSDE component installation. This will copy the necessary files to your computer.

7. Once the installation is finished, click Finish.

Continue with the steps in DB2 for z/OS setup.


9

Configuring DB2 for z/OS

Several steps must be executed before you create the ArcSDE geodatabase to ensure that the z/OS and DB2 environments are set correctly.

To begin with, you need to successfully install the following products. For the first three installations, consult the IBM DB2 for z/OS documentation for instructions.

• IBM DB2 9.1 for z/OS

• IBM DB2 Accessories Suite (Spatial Support - APARs PK51020, PK60624, and PK60137)

• ArcSDE for DB2 z/OS (to get the files and script for steps 3 and 4)

Configuration of the DB2 for z/OS subsystem

Once DB2 for z/OS is installed and enabled for spatial support, the necessary APAR fixes are installed, and the ArcSDE component of ArcGIS Server Enterprise is installed, you need to set up DB2 for z/OS to store the geodatabase. The following is a summary of the steps you need to perform prior to setting up the ArcSDE geodatabase. Click the links to the detailed instructions for each step.

1. Configure the ZPARMs on DB2 z/OS and refresh DB2 with the setting.

2. Create a user, SDE, for ArcSDE administration. To simplify the user privilege authorization, it is highly recommended you use the Resource Access Control Facility (RACF) and enable secondary authorization IDs (RACF groups).

3. Transfer files from the client machine to the target Multiple Virtual Storage (MVS) system.

4. Submit the JCL script, ESRIUDFI, to create the storage groups, databases, and user defined functions (UDFs) for ArcSDE.

5. Grant privileges and permissions to the SDE user and ArcSDE user group on DB2.

1. Configuring ZPARM

a. To enable ArcGIS to run as a distributed client to DB2, the distributed data facility (DDF) must be started. To optimize the performance of ArcSDE with ArcGIS and other clients, the following DB2 ZPARM values are highly recommended. You need to login as the administrator on z/OS to perform the following steps.

Set the following in the DSN6FAC section of DSNTIJUZ:

CMTSTAT=INACTIVE

IDTHTOIN=3600


10

TCPKPALV=120

Set these parameters in section DSN6SYSP:

CONDBAT=10000

EXTSEC=YES

IMPDSDEF=YES

IXQTY=0

MAXDBAT=1000

TSQTY=0

XMLVALA=204800

XMLVALS=10240

You also need to set the correct default WLM environment in WLMENV in this section.

Set the following parameters in the DSN6SPRM section:

CACHEDYN=YES

EDMDBDC=102400

EDMPOOL=32000

EDMSTMTC=102400

EDM_SKELETON_POOL=102400

Note: Be sure your EDM buffer is large enough to allow you to set EDMDBDC to 102400.

b. After changing the ZPARM values above, you also need to make sure that SYSLMOD in job step DSNTIZL points to the correct dataset name so that DB2 will load the correct ZPARM module when it starts.

c. Stop and start DB2 using the SET SYSPARM command to bring the changes online.

2. Creating the SDE operating system account and other ArcGIS accounts

To install the ArcSDE component, you must create a primary authorization ID in RACF on z/OS (SDE by default) with access to the Time Sharing Option (TSO). For information on creating users via RACF, refer to the z/OS administration manual. Only the user who is responsible for managing the GIS data and the ArcSDE application server should log in as the SDE user. Other ArcGIS users should connect using accounts other than SDE. Privileges


11

for these other users are discussed in Creating a geodatabase in DB2 for z/OS.

To simplify user authority management, a secondary authorization ID (a user group in RACF on z/OS) is recommended. You need to enable the secondary authorization IDs on z/OS. Refer to the z/OS manual for information on enabling secondary authorization.

a. Create a stand-alone user account named SDE in the system using RACF.

b. Create a user group, such as SDEUSERS, on z/OS via RACF.

Do this by submitting the name of the group (in this example, SDEUSERS) on VM14 to your EC.

c. Add the SDE user to the SDEUSERS group via RACF.

To connect as the administrative user from a Windows client machine to ArcSDE, a local Windows user with the same name (SDE) as specified for the connection to the server must be present on the client machine. This user does not require any special permission. To create a local Windows user, refer to Microsoft's Windows documentation.

3. Transferring the z/OS files

To use ArcSDE on DB2 version 9.1 for z/OS system, you must transfer two datasets to the target z/OS system. Part of that data (ESRIOBJ.XMIT) will be images of programs that must be link-edited into load libraries on z/OS. DBRM (ESRIDBRM.XMIT) is the other data that will be bound into DB2. The following steps are required to accomplish this setup:

a. As a SYSADM, upload the datasets to the z/OS system using ftp.

The data is in Time Sharing Option/Extension (TSO/E) Transmit/Receive format and must be uploaded to the z/OS using a BINARY transfer.

b. Assuming ftp is used for the transfer, the two datasets must eventually be defined on z/OS with the following characteristics:

RECFM=FB,LRECL=80,BLKSIZE=3120.

Typically, ftp systems are setup such that for any data that is received and results in a new dataset, the resultant new dataset will not be in the required format. However, that can be changed by using ftp commands.

The command to ftp from Windows is

quote site recfm=fb lrecl=80 blksize=3120

If you are logged onto the z/OS and pull the files using ftp, the command is


12

locsite recfm=fm lrecl=80 blksize=3120

Make sure the ftp is in binary mode and type the command appropriate to your operating system.

c. The datasets must be TSO/E RECEIVED by a user account on the z/OS system . Log onto a SYSADM user account id on the z/OS system and open option 6 (the command panel) of Interactive System Productivity Facility (ISPF).

d. The two datasets that are uploaded are named ESRIOBJ.XMIT and ESRIDBRM.XMIT, so issue the following TSO/E commands, one at a time, to receive the datasets:

RECEIVE INDA('SYSADM.ESRIOBJ.XMIT')

RECEIVE INDA('SYSADM.ESRIDBRM.XMIT')

For each of these commands, a prompt for specification of dataset creation overrides will be returned. If you do not provide any overrides, two datasets will be created under the high-level qualifier (HLQ) of the user ID with which you logged in.

You should now have two corresponding datasets in SCR03.

<user>.ESRI.OBJLIB <user>.ESRI.DBRMLIB

e. Review the names of the datasets. If they are correct, they are to be referenced in the ESRI UDF installation job that must now be uploaded to z/OS, edited, and run on z/OS. This is explained in the next step.

4. Creating the databases and UDFs

The JCL script, ESRIUDFI, is provided to create databases and UDFs for ArcSDE. This script is installed to the tools folder of SDEHOME.

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 setup the ArcSDE geodatabase.

To create the databases that will contain the ArcSDE geodatabase, the ESRIUDFI script must be customized using information specific to your implementation and uploaded and run on z/OS. Refer to the instruction of step ESRIS1 in the ESRIUDFI script to create these two databases.

Additionally, the ESRIUDFI JCL script prelinks and link-edits the code required to run the UDFs and creates the UDFs for ArcSDE. See the next section for information on customizing ESRIUDFI.

*To store spatial data, the database subsystem must be spatially-enabled. See the DB2 z/OS documentation for instructions on how to do this:


13

http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/com.ibm.db29.doc.spatial/db2sb23.htm.

Customizing the script

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;

• Optionally, you can create a storage group for managing the ArcSDE data more efficiently. You need to create a storage group first, so you will have to 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. Refer to the section "Granting permissions and privilieges to SDE and the ArcGIS users group" for more details.

Submitting the script

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 via sdesetup.


14

5. Granting permissions and privileges to SDE and the ArcGIS users group.

At this point, permissions and database privileges must be granted to the SDE user and the ArcGIS user group.

Logon as a DB2 account with the SYSADM role to grant the necessary privileges to the ArcGIS user group you set up and the SDE user. In the example GRANT statements, the group is named SDEUSERS.

Grant the following permissions to the ArcGIS user's group:

GRANT SELECT ON SYSIBM.SYSTABAUTH TO SDEUSERS; GRANT SELECT ON SYSIBM.SYSDBAUTH TO SDEUSERS; GRANT SELECT ON SYSIBM.SYSROUTINES TO SDEUSERS; GRANT SELECT ON SYSIBM.SYSTABCONST TO SDEUSERS; GRANT SELECT ON SYSIBM.SYSINDEXES TO SDEUSERS; GRANT SELECT ON SYSIBM.SYSKEYS TO SDEUSERS; GRANT SELECT ON SYSIBM.SYSCOLUMNS TO SDEUSERS; GRANT SELECT ON SYSIBM.SYSCHECKS TO SDEUSERS; GRANT SELECT ON SYSIBM.SYSSCHEMAAUTH TO SDEUSERS; GRANT SELECT ON SYSIBM.SYSTABLES TO SDEUSERS; GRANT SELECT ON SYSIBM.SYSSEQUENCES TO SDEUSERS; GRANT SELECT ON SYSIBM.SYSDUMMY1 TO SDEUSERS;

Grant the following additional privileges to the SDE user:

GRANT BINDADD TO SDE; GRANT CREATE ON COLLECTION SDE TO SDE; GRANT DBADM ON DATABASE <repository_database_name> TO SDE; GRANT DBADM ON DATABASE <user_data_database_name> TO SDE;

Grant the following permission to the PUBLIC role:

GRANT EXECTUE ON PACKAGE SYSPROC.* TO PUBLIC;

The following statement is required if you use a storage group (e.g., ARCSDE in the example in step 4):

GRANT USE OF STOGROUP ARCSDE to SDE;

After these steps have been completed, you should proceed with the creation of the ArcSDE geodatabase.


15

Creating an ArcSDE geodatabase in DB2 for z/OS

After the ArcSDE component is installed and the DB2 for z/OS subsystem is setup, you must complete the following steps to create an ArcSDE geodatabase.

1. Modify the dbinit.sde file in SDEHOME\etc.

a. On your client computer, use the DB2 Control Center to setup a database connection to your DB2 database on z/OS.

b. Locate the dbinit.sde file in the SDEHOME\etc directory (ArcSDE\db2zosexe\etc) on your client computer. Add the following for the first line of the dbinit.sde file, substituting the name of your DB2 subsystem:

set SDE_DATABASE=<DB2_subsystem_name>

See the ArcGIS Server and Desktop help topic The dbinit.sde file for more information on variables you can set in this file.

2. Customize the SDEHOME\etc\dbtune.sde file

The dbtune.sde file populates the DBTUNE geodatabase system table with keywords, parameters, and values that control the physical storage of tables in the database. For DB2 for z/OS databases, it is important that you edit this file prior to running the sdesetup command to specify in which database certain tables will be created. For more information on how the dbtune file and table work, see the ArcGIS Server and Desktop help topics The dbtune file and the DBTUNE table, DBTUNE configuration keywords, and DBTUNE configuration parameter name-configuration string pairs.

a. Locate and open the dbtune.sde file in the ArcSDE\db2zosexe\etc directory on your client computer.

b. Make sure the BLOB_OPTION and CLOB_OPTION parameters are set to be empty strings.

c. Uncomment and change the configuration string values throughout the file to indicate in which database you want specific objects created. The following are suggested settings. Database names in the following example are SDEDBR00 for the database that will store the ArcSDE geodatabase repository tables and SDEDBU00 is the database that will store user-defined data within the database subsystem.

Under the DATA_DICTIONARY keyword, uncomment and set the following parameters:

B_STORAGE "IN DATABASE SDEDBR00" MVTABLES_MODIFIED_TABLE "IN DATABASE SDEDBR00" STATES_TABLE "IN DATABASE SDEDBR00" STATE_LINEAGES_TABLE "IN DATABASE SDEDBR00" VERSIONS_TABLE "IN DATABASE SDEDBR00" XML_INDEX_TAGS_TABLE "IN DATABASE SDEDBR00"


16

Under the DEFAULTS keyword, uncomment and alter these parameters:

AUX_STORAGE "IN DATABASE SDEDBU00" A_STORAGE "IN DATABASE SDEDBU00" BLK_STORAGE "IN DATABASE SDEDBU00" BND_STORAGE "IN DATABASE SDEDBU00" B_STORAGE "IN DATABASE SDEDBU00" D_STORAGE "IN DATABASE SDEDBU00" RAS_STORAGE "IN DATABASE SDEDBU00"

Finally, under the LOGFILE_DEFAULTS keyword, uncomment and set these parameters:

LD_STORAGE "IN DATABASE SDEDBU00" LF_STORAGE "IN DATABASE SDEDBU00" SESSION_STORAGE "IN DATABASE SDEDBU00"

3. Uncomment and alter the TEMP parameter in the giomgr.defs file (optional)

The giomgr.defs file populates the SERVER_CONFIG table at the time of geodatabase creation. There is a commented parameter in this file, TEMP, that is used to specify the full path name to a temporary disk space directory. If left commented out, the default location for this is the temporary folder of the user logged into the Windows machine at the time the geodatabase is created. If that location is acceptable, you do not have to uncomment and change this parameter value. If not, alter the giomgr.defs file, uncommenting the TEMP parameter and setting it to the full path name you want to use, then save the giomgr.defs file. If you do not alter this value before setting up the ArcSDE geodatabase repository, you can alter it after the geodatabase is created using the sdeconfig alter operation. See the ArcSDE administration command reference installed with the ArcSDE component of ArcGIS Server Enterprise for information on this command.

4. Run sdesetup to create the ArcSDE geodatabase repository.

The sdesetup command will do the following:

• Create all the ArcSDE and geodatabase system tables in the DBMS.

• Create ArcSDE stored procedures.

• Populate the LOCATORS and METADATA system tables with data from %SDEHOME\geocode\templates.

The sdesetup command must execute successfully to properly create your geodatabase and for ArcSDE to function correctly.


17

a. Open a command window and change to the bin directory of %SDEHOME.

b. Type the following command:

sdesetup -o install -d DB2ZOS -D <database_subsystem> -u SDE -p <SDE_user_password> -l <license_file>

If you do not have the license file at this time, you can run sdesetup without the -l option to create the ArcSDE geodatabase system tables and files. When you obtain the file, you can run the sdesetup command with the update_key operation. See ArcSDE authorization for details.

The full usage for the sdesetup command with the install operation on DB2 for z/OS is shown below. Brackets indicate options that are not mandatory.

sdesetup -o install -d DB2ZOS [-H <sde_directory>] [-u <DB_Admin_user>] [-p <DB_Admin_password>] -D <database_subsystem> [-N] [-l <license_file>] [-q]

Options:

-d Underlying RDBMS used to store the geodatabase

-D Name of the database in which the ArcSDE repository will be stored

-h/-? Prints syntax and all possible operations and options for the command

-H SDEHOME directory

-l ArcSDE authorization key or path to and name of authorization file

-N No verification prompt given

-o Operation

-p DBMS DBA user password

-q Quiet; all titles and warnings will be suppressed

-s Datasource name

-u SDE user

More information on the sdesetup command can be obtained from the ArcSDE Administration Command Reference.

5. Binding DBRMs to ESRI UDFs


18

Once the geodatabase setup is finished, you need to submit the JCL script, ESRIUDFB, to bind DBRMs that you uploaded in step 3 of Configuring DB2 for z/OS. The script is installed to the tools folder of SDEHOME.

To customize ESRIUDFB, refer to the instruction in the JCL script itself. Specifically, in the body of ESRIUDFB, 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 ESRIUDFB script.

Once you have finished ESRIUDFB customization, you need to submit it on your target machine.

6.Verify the setup

To verify the success of ArcSDE setup, you can run the following test at the Windows command prompt:

sdetable -o create -t verify -d id integer -i sde:db2zos -D <databse_subsystem_name> -u SDE

If ArcSDE reports that the table creation was successful, type the following command to obtain the table information:

sdetable -o describe -t verify -i sde:db2zos -D <databse_subsystem_name> -u SDE

You can now delete your test table using the following command:

sdetable -o delete -t verify -i sde:db2zos -D <databse_subsystem_name> -u SDE

Note: For all these commands, you will be prompted to provide the SDE user's password.

7. Create nonadministrative ArcSDE users

You should not use the administrative ArcSDE user account (SDE) for the purpose of developing and utilizing ArcGIS applications or creating data. You should create stand-alone user accounts on the target DB2 machine for these purposes.

Here is an example of creating a nonadministrative ArcSDE user, EDITOR:

• Create a stand-alone user account, EDITOR, on z/OS via RACF.

• Add user EDITOR to the ArcGIS users group (e.g. SDEUSERS) via RACF.

• Grant the following privileges to the EDITOR user:

GRANT BINDADD TO EDITOR; GRANT CREATE ON COLLECTION SDE1 TO EDITOR; GRANT CREATETAB ON DATABASE SDEDBU00 TO EDITOR; GRANT CREATETS ON DATABASE SDEDBU00 TO EDITOR;


19

If you use the storage group, you need to grant the following additional privilege:

GRANT USE OF STOGROUP ARCSDE to EDITOR;

Related concepts found in the help

You can get more information related to setting up the repository in the the help system installed with ArcGIS Server or ArcGIS Desktop. Open the help and search for the following titles:

The dbtune file and the DBTUNE table

DBTUNE configuration keywords

DBTUNE configuration parameter name-configuration string pairs

Log file keywords

The giomgr.defs file and the SERVER_CONFIG system table

The dbinit.sde file

System tables of a geodatabase in DB2


20

ArcSDE authorization

New installations of the ArcSDE component for DB2 z/OS require an authorization file. You must obtain an authorization file (.ecp file) from ESRI Customer Service. For more information on obtaining an authorization file, see https://service.esri.com.

Every ArcSDE geodatabase that resides on the same machine must be authorized using the authorization file because the authorization information is stored in the geodatabase repository. You not be able to connect to the geodatabase unless your geodatabase repository has been configured using a valid authorization file.

You can register ArcSDE with an authorization file in one of two ways:

• If you already have an authorization file, run the sdesetup command with the install operation and specify the location of the authorization file with the -l option. See Creating an ArcSDE gedatabase in DB2 for z/OS.

OR

• If you don't yet have an authorization file, you can run the sdesetup command with the install operation without specifying the -l option. After you contact ESRI and receive your authorization file, you can run sdesetup again using the update_key operation and specifying the -l option.

• The syntax for using the update_key operation with the sdesetup command for an ArcSDE for DB2 z/OS geodatabase is as follows:

sdesetup -o update_key -d DB2ZOS -l <authorization_key> -u SDE [-p <DB_Admin_password>] [-H <sde_directory>] [-D <database_subsystem>] [-N] [-q]

For example:

sdesetup -o update_key -d DB2ZOS -D myec -l c:\Server93.ecp -u sde -p sde

More information on the sdesetup command can be obtained from the ArcSDE Administration Command Reference (%SDEHOME\documentation\Admin_Cmd_Ref).


21

Multiple installations on the same machine

It is possible to install the ArcSDE component for more than one type of DBMS on the same machine. Each SDEHOME directory will have a different name. The following is a list of the default installation directories on Windows for ArcSDE:

DBMS Default SDEHOME path on Windows

DB2 LUW Program Files\ArcGIS\ArcSDE\db2exe

DB2 for z/OS

Program Files\ArcGIS\ArcSDE\db2zosexe

Informix Program Files\ArcGIS\ArcSDE\infxexe

Oracle 9i Program Files\ArcGIS\ArcSDE\ora9iexe

Oracle 10g Program Files\ArcGIS\ArcSDE\ora10gexe

PostgreSQL Program Files\ArcGIS\ArcSDE\pgexe

SQL Server Program Files\ArcGIS\ArcSDE\sqlexe

If you have licensed and installed, for example, ArcSDE for DB2 z/OS and ArcSDE for PostgreSQL on the same computer, you should specify such options as -D, -i, and -H when running ArcSDE administration commands to be sure you are pointing to the correct SDEHOME.


22

Uninstalling ArcSDE for DB2 for z/OS Uninstalling an existing version of the ArcSDE component of ArcGIS Server Enterprise consists of removing the ArcSDE files from disk.

Since the ArcSDE files are installed on a Windows client machine, you can use the Windows Add/Remove Programs tool to uninstall the ArcSDE component.

1. Before uninstalling ArcSDE, make a copy of any custom files (such as your custom dbtune.sde file) to keep for future use.

2. From the Start button, open the Control Panel. Double-click the Add/Remove Programs icon.

3. Select ArcGIS ArcSDE for DB2 z/OS from the program list, and click the Remove button.

Though this removes the ArcSDE files from disk, the geodatabase system tables, stored procedures, and user data are still in your databases on the DB2 z/OS database subsystem.

Date post:	24-Jul-2018
Category:	Documents
Upload:	tranliem
View:	224 times
Download:	0 times

Installation Guide: ArcSDE for IBM DB2 on...

Documents