BAAN IV. DB2 for OS/390 Installation Guide for BAAN IV

Transcription

1 BAAN IV DB2 for OS/390 Istallatio Guide for BAAN IV

2 A publicatio of: Baa Developmet B.V. P.O.Box AC Bareveld The Netherlads Prited i the Netherlads Baa Developmet B.V All rights reserved. The iformatio i this documet is subject to chage without otice. No part of this documet may be reproduced, stored or trasmitted i ay form or by ay meas, electroic or mechaical, for ay purpose, without the express writte permissio of Baa Developmet B.V. Baa Developmet B.V. assumes o liability for ay damages icurred, directly or idirectly, from ay errors, omissios or discrepacies betwee the software ad the iformatio cotaied i this documet. Documet Iformatio Code: U7158B US Group: User Documetatio Editio: B Date: May, 1999

3 Table of cotets 1 Itroductio 1-1 Itroductio 1-1 Database driver 1-2 The BAAN IV database driver i geeral 1-2 SQL processig 1-2 Database driver features 1-3 Resource file 1-5 Log files 1-5 Database driver trace iformatio 1-5 Error loggig 1-5 Tuig aspects: profilig ad statistics Customizig DB2 for BAAN IV 2-1 DB2 parameters for BAAN IV 2-1 Subsystem parameters 2-1 DSNHDECP DB2 parameters 2-2 CCSID Cofiguratio 2-2 DB2 Attach Cosideratios 2-3 RRS 2-3 CAF 2-3 Preparig the BAAN IV Istallatio 2-3 BIND cosideratios 2-4 Ruig db2_istall6.1 for BAAN IV 2-5 Storage Group Creatio 2-6 Database Creatio 2-6 Tablespace Creatio 2-7 Admiistrative Files Creatio 2-7 Database Admiistratio DB2 database driver iterals ad exterals 3-1 DB2 driver exterals 3-1 Data dictioary mappig 3-1 DB2 table ad idex locatio 3-4 Security 3-8 DB2 error reportig ad tracig 3-11 Error reportig 3-12 DB2 Database driver trace iformatio 3-12 DB2 for OS/390 Istallatio Guide for BAAN IV iii

4 Table of cotets DB2 database driver profilig ad statistics 3-13 Profilig 3-13 Statistics 3-14 DB2 driver iterals 3-14 Iterfaces to DB SQL processig 3-15 DB2 driver lockig strategy DB2 database driver admiistratio tools 4-1 The db2_admi6.1 tool 4-1 The User Admiistratio meu 4-2 The User Iformatio meu 4-4 The db2_mait6.1 tool Appedix A: Cofiguratio ad tuig aspects 5-1 DB2 cofiguratio ad tuig aspects 5-1 Tuig aspects 5-1 DB2 database driver cofiguratio ad tuig aspects 5-2 Cursor maagemet 5-2 Lockig behavior 5-3 Idex optimizatio 5-3 Fetch optimizatio 5-6 Cachig 5-7 Optimistic ad pessimistic referece checks 5-7 Tuig 5-8 OS/390 tuig aspects Appedix B: Settig database driver behavior 6-1 Driver resources 6-1 Eviromet variables 6-2 Server eviromet variables 6-3 Cliet eviromet variables Appedix C: Database driver resources ad eviromet variables 7-1 Summary of DB2 resources ad eviromet variables 7-1 Detailed descriptio of DB2 resources ad eviromet variables 7-3 Geeric driver resources 7-3 DB2 driver specific resources 7-9 DB2 eviromet variables Appedix D: Sample db2_storage file ad Sample JCL 8-1 Sample db2_storage file 8-1 Sample JCL for Buildig Database Objects 8-5 DB2 for OS/390 Istallatio Guide for BAAN IV iv

5 About this documet About this documet This documet describes how to istall ad cofigure BAAN IV with DB2 for OS/390 Versio 5.1. The audiece for this book is all persos performig a istallatio of DB2 as a database maagemet system for the BAAN IVc eviromet o a OS/390 UNIX System Services server. A elemetary kowledge of UNIX ad DB2 is required. The procedure for istallig the BAAN IV software is described i the Istallatio Guide for BAAN IV o OS/390 UNIX System Services. The guide is divided ito four chapters ad four appedices: Chapter 1 describes the BAAN IV database driver architecture. Chapter 2 describes customizig DB2 for BAAN IV. Chapter 3 describes the DB2 database driver iterals ad exterals. Chapter 4 describes the DB2 database driver admiistratio tools. Appedix A supplies iformatio about geeral cofiguratio ad tuig iformatio for both the database ad the operatig system. Appedix B describes how to set database driver behavior. Appedix C describes database driver resources ad eviromet variables. Appedix D cotais the default db2_storage file ad sample JCL. v

6 About this documet DB2 for OS/390 Istallatio Guide for BAAN IV vi

7 1 Itroductio This chapter describes the architecture of the BAAN IV database driver. It supplies backgroud iformatio about the BAAN IV database iterface to the supported relatioal database systems. This chapter also describes where you ca fid the database driver resource ad log files for the BAAN IV server. Itroductio BAAN IV supports a wide rage of databases by implemetig a iterface to each of these databases: the database driver. The DB2 relatioal database maagemet system (RDBMS) is oe of the supported databases. The BAAN IV DB2 database driver is the iterface to DB2. The distributio of BAAN IV tables i differet databases is trasparet to the user. The data from these tables is first refereced by usig BAAN IV SQL. The BAAN IV SQL query is the coverted to DBMS SQL at the driver level ad is passed to the DBMS server. Fially, the database driver performs the joi of rows retured by the RDBMS server as a result of the executio of the DBMS SQL query. A Level-1 driver is a driver with sigle table SQL queries passed to the RDBMS. The driver performs the joi o rows before returig the resultat row to the BAAN IV applicatio. A Level-2 driver is a driver with multiple table jois passed to the RDBMS. The driver relies o the RDBMS to perform table jois. The resultig rows retured by the RDBMS are the retured to the BAAN IV applicatio. This documet addresses the DB2 driver i Level-1 mode. Level-1 mode allows BAAN IV tables to be created ad maipulated i the DB2 database. As all the database drivers have some commo fuctioality, this documet discusses the commo part first ad the describes the DB2 database driver-specific details. Uless otherwise oted, all text files, for example log files, are i EBCDIC format. DB2 for OS/390 Istallatio Guide for BAAN IV 1-1

8 Itroductio Database driver This sectio describes the BAAN IV database driver i geeral, SQL processig, ad database driver features. The BAAN IV database driver i geeral The database driver, part of the BAAN IV Tools cliet/server architecture, acts as a iterface betwee BAAN IV Tools ad the ruig RDBMS. DB2 is the oly RDBMS supported o OS/390. The BAAN database driver performs iteractio with DB2. The driver acts as a server to the applicatio (BAAN IV cliet) ad commuicates with DB2. The cliet (the applicatio beig executed by bshell6.1) seds database requests to the server (the BAAN IV database driver), which i tur trasfers the request to DB2. Data retured by DB2 is set back to the applicatio by the driver. A overview of the architecture is show below usig DB2 RDBMS. Cliet Server RDBMS Bshell DB2 Driver DB2 RDBMS BAAN IV SQL DB2 SQL Figure 1-1, BAAN IVc database driver architecture SQL processig Whe the bshell ecouters a database query i the applicatio executig, it parses the query ad seds a iteral represetatio to the database driver. The driver traslates this query ito oe or more sigle table queries i the SQL dialect that is relevat to DB2. The driver coects to DB2 usig the Coectio Maager compoet of OS/390 UNIX System Services Coectio Scalig ad the queries are the haded over to DB2. The driver collects the rows retured by DB2 as a result of the query ad seds them back to the applicatio. The database driver catches ad hadles the error coditios. DB2 for OS/390 Istallatio Guide for BAAN IV 1-2

9 Itroductio The processig of BAAN IV SQL queries is as follows. The driver receives database idepedet represetatios of queries. These queries are processed further to geerate DB2 compatible queries. The BAAN IV database driver cosists of a DB2 idepedet sectio ad a DB2 depedet sectio. Whe it comes to evaluatig the SQL expressios, DB2 may ot support some operators because the BAAN IV defiitio of the operator is differet from that of DB2. Such expressios are traslated ito a equivalet statemet that is supported by DB2. A SQL expressio is geerated by the database depedet layer withi the driver ad passed to DB2. Database driver features The BAAN IV database driver architecture cotais the followig features. Data dictioary (DD) The characteristics of the BAAN IV cliet DD (colum ames, data types, colum size, ad umber of colums) differ from the server DD. A commo pool of DDs at the server side makes the DD sharable. The server DD cotais the colum-specific iformatio i terms of DB2 format. There is oe table DD at the server side for every table DD at the cliet side. DDs of differet compay umbers ca be shared withi the server, so they eed ot be set agai by the cliet. Security Authorized BAAN IV users are registered i the admiistratio files kept i the $BSE/lib/db2 directory. The $BSE/lib/db2/db2_users file cotais the user ame ad password i ecrypted form. The driver establishes a coectio to the database for the user usig DB2 for OS/390 security autheticatio methods. See DB2 for OS/390 Admiistratio Guide for details. User root or the database admiistrator accout (DBA) admiister these files. The driver establishes a correspodig coectio for every BAAN IV sessio. See Chapter 3, Security for further iformatio. Referetial itegrity The BAAN IV database driver maitais referetial itegrity for update ad delete actios, provided that the refereced tables are i the same database. No extra commuicatio betwee cliet ad server is ivolved. For cascade updates ad deletes, the driver ca geerate a sigle statemet to replace several row-level queries. For example, it is possible to delete all referecig rows at oce. This is much more efficiet tha deletio o a row-by-row basis. 1-3

10 Itroductio Data itegrity Data itegrity is eforced by usig row-level lockig mechaisms. As a result, differet BAAN IV sessios, ad eve packages or tools other tha BAAN IV that also use ormal lockig, are cocurret. Implicit lockig is applied wheever possible. I other cases, the driver will perform explicit lockig. Statemet bufferig Updates, iserts, ad deletes are buffered at the cliet side ad flushed at the time of trasactio commit, or earlier whe ecessary. This reduces the umber of etwork roud trips ad data volumes. Data bufferig, reductio, ad compressio Whe multiple rows are retured from a query, the rows are buffered ad set back to the cliet as oe block. Also, data reductio ad compressio is applied to miimize the amout of data trasferred betwee the bshell ad the driver. Delayed lockig ad updates The driver performs the delayed lockig mechaism. Before a update is doe, the driver checks o a colum-by-colum basis to determie if the related colums are chaged. If the related colums are ot chaged, the update is NOT carried out. No extra etwork commuicatio is required. Call Attach Facility versus Resource Recovery Services Coectio Maager supports two types of local coectio attachmets to DB2. The first, Call Attach Facility (CAF), which provides a direct coect to DB2, uses address space level security, ad does ot allow multiple sigos o the same coectio. With slight modificatios to a authorizatio exit, it is sufficiet for Baa. A ewer coectio mechaism, Resource Recovery Services (RRS) makes use of a OS/390 subsystem to hadle trasactio commits. RRS is capable of task level security so that o chages to DB2 authorizatio exits are required ad ca be used for distributed trasactios. It also allows for retry of trasactios which timeout. See Chapter 2, DB2 Attach Cosideratios ad Chapter 3, Security for further iformatio. DB2 for OS/390 Istallatio Guide for BAAN IV 1-4

11 Itroductio Resource file The database drivers refer to a commo admiistratio file i the Baa Software Eviromet (BSE). The resource variables defied i this file set the behavior of the driver at rutime. You ca specify i the resource file $BSE/lib/defaults/db_resource the variables for the DB2 driver. The driver reads these variables at rutime. Refer to Appedix B for a descriptio o how to set the database driver resources ad to Appedix C for a detailed descriptio of the driver resources. Log files The BAAN IV database driver ca log the followig iformatio: Database driver trace iformatio Error loggig These types of loggig are discussed briefly i the sectios below. Refer to DB2 error reportig ad tracig o page 3-11 for further iformatio. Database driver trace iformatio The database driver provides a optio to log olie iformatio about the driver actios. The resultig log file cotais debuggig iformatio that ca help solve problems. Error loggig The database driver logs its error messages i the file log.db2, which resides i the $BSE/log directory. I most cases, the various log files i the $BSE/log directory, for example, log.bshell6.1 ad log.db2 cotai eough iformatio to determie the ature ad cause of a problem. Therefore, wheever a error is ecoutered, you are advised to check the log file of the driver ($BSE/log/log.db2). 1-5

12 Itroductio Tuig aspects: profilig ad statistics The database driver eables users to log timig aspects ad statistics which are useful for tuig purposes by idetifyig performace bottleecks ad givig iput to the process of tuig. The BAAN IV database drivers provide profilig ad statistics optios. The sectio DB2 Driver Profilig ad Statistics i Chapter 3 describes how the eviromet variables must be set to eable profilig ad statistics. Sice the report is geeric for all databases, some iformatio, such as the specific ROW actios, may ot be appropriate for a particular database driver. The report format is also subject to chage. DB2 for OS/390 Istallatio Guide for BAAN IV 1-6

13 2 Customizig DB2 for BAAN IV This chapter describes how to customize DB2 for BAAN IV. It icludes the followig topics: DB2 parameters for BAAN IV CCSID Cofiguratio Preparig the BAAN IV istallatio BIND cosideratios Ruig db2_istall6.1 for BAAN IV Database Admiistratio To ru the Baa applicatio, the DB2 dataset hlq.sdsnload must be accessible. For example, it ca be added to the LINKLIST or set i the STEPLIB eviromet variable. DB2 parameters for BAAN IV Certai DB2 parameters provide the ability to customize your eviromet. A subset of these parameters are discussed below. Subsystem parameters As a startig poit, we recommed the followig parameters. Moitorig ad tuig may dictate chages to these iitial values. CACHEDYN=YES DSMAX = 3000 EDMPOOL = IRLMRWT=60 MAXKEEPD= CTHREAD = 2000 IDBACK = 2000 LOGLOAD = DB2 for OS/390 Istallatio Guide for BAAN IV 2-1

14 Customizig DB2 for BAAN IV DSNHDECP DB2 parameters For buildig a ASCII database, we recommed the followig parameters. ASCCSID=819 SCCSID=37 ENSCHEME=ASCII DATE=ISO TIME=ISO CCSID Cofiguratio CCSID is a property of each tablespace created i the DB2 subsystem. The CCSID sectio i /etc/cmx/cmx.cof is provided to allow customers the ability to build a ASCII database. Customers ca store BAAN IV data i ASCII, access it from BAAN IV i readable format, ad also access it i readable format from OS/390 with applicatios such as SPUFI. Storig BAAN IV data i ASCII elimiates the eed to covert the data from EBCDIC to ASCII whe ruig the BAAN IV applicatio, the preferred method of operatio. The parameter DB2ccsid i /etc/cmx/cmx.cof provides CCSID support. This parameter must be set to the same code page that was used by DB2 whe creatig the database ad whe loadig the database via bdbpost. If the ccsids are differet, data traslatio may occur, which could cause performace problems or worse, ivalid data. For ASCII, the BAAN IV database(s) should be created with ENSCHEME ASCII. Specify the ASCII ccsid of the codepage you wat i the ASCCSID parameter of DSNHDECP. The, specify the same ccsid i the DB2ccsid parameter of the /etc/cmx/cmx.cof file. The stadard Eglish ASCII ccsid is 819. For EBCDIC, the BAAN IV database(s) should be created with ENSCHEME EBCDIC. Specify the EBCDIC ccsid of the codepage you wat i the SCCSID parameter of DSNHDECP. The, specify the same ccsid i the DB2ccsid parameter of the /etc/cmx/cmx.cof file. The stadard Eglish EBCDIC ccsid is 37. As a performace optio for EBCDIC databases oly, you ca specify a DB2ccsid parameter of 0 i the /etc/cmx/cmx.cof file. This will disable ay ccsid support. The Baa data is still stored i ASCII, but DB2 passes the data through utouched ad utraslated to ay locally attached applicatio. Ay applicatio which expects EBCDIC character data will have to do its ow traslatio. For example, SPUFI, will ot show the data i readable form. DB2 for OS/390 Istallatio Guide for BAAN IV 2-2

15 Customizig DB2 for BAAN IV If the DB2ccsid parameter is ot specified i /etc/cmx/cmx.cof, the default value 819 is used. DB2 Attach Cosideratios Coectio Maager supports two types of local coectio attachmets to DB2. The first, Call Attach Facility (CAF), which provides a direct coect to DB2, uses address space level security, ad does ot allow multiple sigos o the same coectio. With slight modificatios to a authorizatio exit, it is sufficiet for Baa. A ewer coectio mechaism, Resource Recovery Services (RRS) makes use of a OS/390 subsystem to hadle trasactio commits. RRS is capable of task level security so that o chages to DB2 authorizatio exits are required ad ca be used for distributed trasactios. It also allows for retry of trasactios which timeout. Cosider the followig whe decidig the attach type: RRS RRS is the strategic directio for DB2 for OS/390 Requires o chage to DB2 authorizatio exits whe usig the Process Maager compoet of OS/390 UNIX System Services Coectio Scalig Requires OS/390 Logger customizatio Requires RRS separately started OS/390 subsystem Supports retry o lock timeout or deadlock Supports distributed trasactio sematics (curretly ot used by BAAN IV) CAF No special customizatio to istall Requires chage to authorizatio exit whe used with the Process Maager compoet of OS/390 UNIX System Services Coectio Scalig Implicit rollback o all deadlocks or timeouts Preparig the BAAN IV Istallatio After DB2 has bee istalled, you must add OS/390 group accouts ad coect users to groups before completig the istallatio of BAAN IV. You must be logged i as a user with the appropriate System Authorizatio Facility (SAF) authorizatio to take the steps listed below. SAF is the security product istalled o OS/390, such as, RACF, ACF2, or TOP SECRET. 2-3

16 Customizig DB2 for BAAN IV The followig OS/390 group accouts are recommeded. See "Security", Chapter 3 for more iformatio o groups: A OS/390 group must be created for the group(s) defied i $BSE/lib/db2/db2_groups. This group will become the table qualifier or schema for users coected to this group accout. The group must have a OMVS segmet with group id 125. For example, this group is called BAAN. A OS/390 group ca be created to serve as the BAAN IV Software Eviromet Admiistrator group. This group will be grated data base authorities. Users root ad bsp must be coected to this group. Ay other user requirig DBA authorities should be coected to this group. For example, this group is called BSPGRP. A OS/390 group ca be created to serve as the BAAN IV Database Geeral Access group. This group will be grated table privileges. Users requirig access to the BAAN IV applicatio will be coected to this group. For example, this group is called BAANGRP. Both BSPGRP ad BAANGRP groups must be coected to the BAAN group. BIND cosideratios The Coectio Maager must be istalled prior to cotiuig the DB2 customizatio. A sample BIND job is provided as part of the Coectio Maager ad is located i the partitioed dataset SYS1.SAMPLIB(CMXBIND). This sample cotais the required BIND optios. A Coectio Maager pla with DYNAMICRULES(RUN) must be used to hadle dyamic SQL that produces DDL that creates ad deletes objects, for example, the database load process. A Coectio Maager pla with DYNAMICRULES(BIND) is desirable durig ormal operatios sice the EDMPOOL requiremets for the global DB2 cache are reduced. There is oly oe authorizatio id the bider id to match i the cache, so the umber of uique cache etries is derived from that sigle userid s uique SQL. The BAAN IV DB2 database driver uses UNCOMMITTED READ(UR), "dirty read", isolatio level for all read-oly SQL. Therefore the Coectio Maager pla must use the bid optio ISOLATION(UR). DB2 for OS/390 Istallatio Guide for BAAN IV 2-4

17 Customizig DB2 for BAAN IV Ruig db2_istall6.1 for BAAN IV This sectio describes the DB2-specific steps ivolved i the istallatio of the BAAN IV software. It does ot supply a descriptio of the istallatio procedure for BAAN IV itself. For a descriptio of the istallatio procedure, refer to the BAAN IV Istallatio Guide for OS/390. After havig read the BAAN IV software from the distributio medium, you must execute the BAAN IV istallatio script, istall6.1. This script prompts the istaller for the database driver. Choose DB2. You eed approximately 3500 cyliders of space o a IBM 3390 Model 3 to load compay 000 ad the demo compaies. Your VTOCs must be able to hadle at least datasets. The istall6.1 istallatio script will ask you if you wat to ru the DB2 istallatio script. If you aswer Yes, you will get a prompt. Eter the followig commad to start the DB2 driver istallatio script. db2_istall6.1 Before ivokig this script, you must defie a DB2 subsystem ad the Coectio Maager cofiguratio file must be i place. The db2_istall6.1 script must be ru by someoe kowledgeable about DB2 for OS/390 ad familiar with the data base desig for the Baa data base. The db2_istall6.1 script ca be ru multiple times. We recommed that you have the BAAN IV tables, idex data, ad the DB2 system catalogs o separate tablespaces o differet DASD volumes to improve performace. For the best performace, tables for each package ca be stored i a differet tablespace or the tables with the highest growth rate ca be separated from other tables ad placed i a tablespace with a larger extet size. This avoids fragmetatio ad allows for tablespace level backup ad recovery. Durig the executio of the db2_istall6.1 script, you are asked if you wat to perform the followig tasks for the Baa data base o DB2: Create storage group ad grat privileges to use the storage group Create database ad grat privileges to use the database Create tablespaces ad grat privileges to use these tablespaces Create admiistrative files Add iitial group to group file Add users root, bsp, ROOT, ad BSP to group Add etries for tables ad idexes to storage files 2-5

18 Customizig DB2 for BAAN IV As ad alterative, you ca aswer NO to the create storage group, create database ad create tablespace steps ad use the sample JCL ad sample db2_storage file to create these objects. The sample provides the correct space allocatios for compay 000 ad the demo compaies 550 ad 750. If you decide to use the sample db2_storage file, copy $BSE/lib/db2/db2_storage.sample to $BSE/lib/db2/db2_storage. You may wish to edit the object ames i the db2_storage file usig db2_admi6.1 or the commad vi. Refer to Appedix D for details about the samples. Note that these sample files are ot meat to be used for productio data; they are merely there to assist you i settig up a eviromet for demo purposes. The db2_istall6.1 script prompts you to eter the followig iformatio. (Refer to the DB2 for OS/390 Versio 5 SQL Referece maual for specificatio iformatio.) Storage Group Creatio To create the STOGROUPs for the BAAN IV database, type Yes. You are the asked to supply the followig iformatio for each STOGROUP you create: Storage group ame Storage group volumes Storage group VCAT Optioal password After a STOGROUP is successfully created, you are give the opportuity to grat privileges to use the storage group. Database Creatio To create the database for BAAN IV, type Yes. You are the asked to supply the followig iformatio: Database ame Storage group ame Bufferpool CCSID - Specifies the default ecodig scheme for data stored i the database. It is recommeded that the data be stored i ASCII format. CCSID ca be specified at the subsystem level, database level, or tablespace level. After a database is successfully created, you are give the opportuity to grat privileges to use the database. DB2 for OS/390 Istallatio Guide for BAAN IV 2-6

19 Customizig DB2 for BAAN IV Tablespace Creatio To create the tablespaces for BAAN IV, type Yes. You are asked to supply the followig iformatio: Tablespace ame Database ame usig-block data free-block data gbpache-block data whether tablespace is to be segmeted BUFFERPOOL LOCKSIZE LOCKMAX CLOSE PASSWORD COMPRESS CCSID MAXROWS After a tablespace is successfully created, you are give the opportuity to grat privileges to use the tablespace. You caot create a partitioed tablespace usig the db2_istall6.1 script. Admiistrative Files Creatio The last step i the executio sequece of the db2_istall6.1 script is the creatio of the admiistrative files required by the DB2 driver i the directory $BSE/lib/db2. You are asked if you wat to create the followig files. Type Yes to create them. db2_groups This file cotais the group logo ame. The group logo ame, supplied by you, becomes the qualifier for all BAAN IV tables that are ot privately owed, that is, the db2_storage file specifies :group:. Refer to Chapter 3 for specifics o the db2_storage file. db2_users This file cotais the DB2 user ame. You are give the opportuity to add the iitial BAAN IV users that are authorized to access the database; amely users root, bsp, ROOT, ad BSP. You ca also add other users at this time or durig aother executio of the db2_istall6.1 script. 2-7

20 Customizig DB2 for BAAN IV db2_storage The db2_storage file provides the parameters eeded whe creatig table ad idex objects, such as, database/tablespace ad space allocatio iformatio. You have the flexibility to put all tables from all compaies i oe database/tablespace or each table i its ow database/tablespace. The best solutio is likely somewhere i the middle. We recommed that you distribute this data for performace reasos. Use the databases ad tablespaces to distribute the tables ad STOGROUPs to distribute the idex data. Refer to Chapter 3 for details o the db2_storage file. Refer to Appedix D to see a sample of the db2_storage file ad a explaatio of how it effects the database layout. For more iformatio about the admiistratio files, refer to the sectios DB2 Table ad Idex Locatio ad Security i Chapter 3. After the admiistratio files are created by the db2_istall6.1 script, the message "db2_istall6.1 completed." ad prompt are displayed. If you etered db2_istall6.1 script from the istall6.1 script, you ca type exit to retur to the istall6.1 istallatio script ad cotiue the istallatio of BAAN IV. Database Admiistratio Oce the database is loaded, the database admiistrator should perform ormal database admiistratio tasks, icludig ruig RUNSTATS for all the tablespaces/idexes ad esurig a recovery pla is i place. Refer to DB2 for OS/390 Admiistratio Guide. DB2 for OS/390 Istallatio Guide for BAAN IV 2-8

21 3 DB2 database driver iterals ad exterals This chapter describes both the exteral aspects of the DB2 database driver s commuicatio with BAAN IV ad the iteral features of the DB2 database driver. DB2 driver exterals This sectio describes the characteristics of BAAN IV tables created i DB2 through the DB2 database driver i Level-1 mode, where BAAN IV SQL queries are processed by the DB2 database driver o a sigle table or sigle row basis. Data dictioary mappig The DB2 database driver caot use the data dictioary (DD) of BAAN IV directly to create DB2 tables. To create valid DB2 tables, the DB2 database driver performs some mappig or traslatio. The followig covetios are importat: Geeral ame covetio All ames geerated by the DB2 database driver are i lowercase characters ad ot eclosed withi double quotatio marks. DB2 coverts these ames to uppercase whe storig them i the system catalogs. Table ame covetio BAAN IV table ames i DB2 have the followig format. t<package><dd table ame><compay Number (3 digit)> For example, the BAAN IV table ttiitm999 with compay umber 505 is created i DB2 as TTIITM Colum ame covetio Each colum i the BAAN IV DD correspods to oe or more colums i the DB2 table. DB2 for OS/390 Istallatio Guide for BAAN IV 3-1

22 DB2 database driver iterals ad exterals The followig rules must be adhered to: Geeral Colum ames are preceded by the t_ strig. For example, a BAAN IV colum amed, cpac, is created i DB2 as t_cpac. This is doe to avoid reserved words. For example, a colum ame such as order should ot be used i DB2 as the order colum ame, because it is a reserved SQL word. Also, whe colum ames cotai a period, the period is replaced by the uderscore character. Log strig colums Colums of type, strig i BAAN IV ca exceed the maximum legth of 254 character colums i DB2. Whe the BAAN IV strig colum exceeds this limit, the colum is split ito parts of 254 characters. For the first part of the colum, the colum ame is exteded with _1, the secod part with _2, ad so o. For example, a BAAN IV strig colum, called desc with a size of 300 characters, will result i two DB2 colums: t_desc_1: size 254 t_desc_2: size 46 Array colums I BAAN IV, array colums which are colums with iteral multiple elemets, ca be defied. The umber of elemets is called the depth. For example, a colum such as date ca be defied as a array of three elemets. I DB2, each elemet refers to oe or more colums that have the elemet umber added as a suffix to the colum ame. For example, <col_ame>_<array elemet umber>, as i: t_date_1: elemet 1 t_date_2: elemet 2 t_date_3: elemet 3 Note that if the elemet is of type strig ad oe elemet type exceeds 254, it is split, as i: t_str_1_1: elemet 1, part 1 t_str_1_2: elemet 1, part 2 DB2 for OS/390 Istallatio Guide for BAAN IV 3-2

23 DB2 database driver iterals ad exterals Array compressio Whe the umber of DB2 colums exceeds the maximum umber of DB2 colums (750 for DB2 for OS/390), the DB2 database driver will try to compress (joi) array colums to reduce the umber of colums. All array elemets of oe array colum are stored as oe RAW (bit data) colum i the DB2 database. The raw value cotais all the elemets cocateated i biary format. The DB2 database driver starts compressig the array colum which will yield the highest umber of colums. It cotiues compressig array colums util the umber of colums is less tha the DB2 maximum. The ame of the colum i DB2 will be the same as ormal colums, as i: t_array: raw cotais all elemets. Whe a compressed array colum exceeds 254 characters, it will be split i parts of 254 characters or less. Idex ame covetio BAAN IV idexes are idetified by a sequece umber, startig from 1 for each table. Each table has at least 1 idex, the primary idex. Because the idex ames i DB2 are uique to the user, the table ame, idex umber, ad the idex type (the order that is ascedig or descedig) are icluded i the idex ame. The example below shows the geeral format ad the format of the idex ame created for BAAN IV table ttadv999, idex umber 1 (compay umber 505) i ascedig order: I<table_ame>_<idx_o><idx_type> Ittadv999505_1a (idex 1 of ttadv999 i ascedig order) The first letter of the idex type (ascedig or descedig) is appeded to the idex ame. Data types The DB2 database driver uses the CHAR data type which coforms to ANSI stadards. This is used because BAAN IV strig data type has characteristics that coform to the ANSI specificatios. Operatios such as compariso ad cocateatio ca be doe i a ANSI-compliat way whe the CHAR data type is used. The table below shows the mappig betwee BAAN IV ad DB2 data types. 3-3

24 DB2 database driver iterals ad exterals The mappig betwee BAAN IV ad DB2 data types BAAN IV Data Type DB2 Data Type CHAR CHAR(1) for bit data ENUM CHAR(1) for bit data INT SMALLINT LONG INTEGER MAIL INTEGER TIME INTEGER TEXT INTEGER BITSET INTEGER FLOAT DOUBLE DOUBLE DOUBLE STRING CHAR() DATE DATE NOTE Sice BAAN IV SQL uses ANSI-compliat strig compariso sematics, the CHAR data type is used, istead of VARCHAR. Costraits All the colums created by the DB2 driver have the NOT NULL costrait. BAAN IV does ot support NULLS. If a BAAN IV idex is defied as a uique idex, the DB2 idex is also created with the UNIQUE clause. Otherwise duplicate idexes are ot defied with the UNIQUE clause. The bshell rage of dates are the same as i DB2, with the followig exceptio. The bshell date 0 is mapped to date 1 i DB2. The bshell date 1 is marked as a ivalid date. DB2 table ad idex locatio DB2 provides a way to specify the distributio of table ad idex data i differet tablespaces. You ca specify the storage parameters i the $BSE/lib/db2/db2_storage file. The DB2 driver uses the storage parameters whe DDL statemets are executed (for example, CREATE TABLE ad CREATE INDEX). See Appedix D for a sample db2_storage file. DB2 for OS/390 Istallatio Guide for BAAN IV 3-4

25 DB2 database driver iterals ad exterals Storage file format The storage file cosists of oe or more etries, each cosistig of several fields separated by colos. The format of a etry i the storage file is: [{<user list>}]<table/module specificatio>:<compay umber>:<object type>: <private group>:<table/idex optimizatio>:<refresh time>:<storage parameters> The followig describes each of the fields i a etry i the storage file. user list Descriptio Example This field cosists of a list of comma-separated user ames to which this etry applies. Whe o list is specified, the etry applies to all users. {maria,joh} table/module specificatio Descriptio This field cosists of a list of comma-separated table ames or a module ame to which the etry applies. A asterisk (*) idicates all tables. Example ttadv000,ttadv999 two specific tables Ttadv all tables i module tt ad package adv Tt all tables i module tt * all tables compay umber Descriptio This field cosists of a list of compay umbers to which the etry applies. A asterisk (*) idicates all compay umbers. Example 000,999 compaies 000 ad 999 * all compaies 3-5

26 DB2 database driver iterals ad exterals object type Descriptio This field cosists of a list of object (table or idex) idetificatios to which the etry applies. The followig optios ca be specified: T table oly I all idexes I <idex umber> oly specified idex * both table ad idexes Example I1,I2 oly idex 1 ad 2 T oly for table private group Descriptio This field idetifies the ower of the table. Either private or group should be specified. table/idex optimizatio Descriptio This field specifies the flags related to idexes ad tables. Whe specified o a T object etry, it defies the default for all idexes. The followig octal values ca be used to set the flags for a specific idex or table: 0000 o optimizatio (ot supported) 0001 optimizatio usig both ascedig ad descedig idexes 0010 Idex order ascedig oly 0020 Idex order descedig oly 0100 Key oly optimizatio (ot supported) Default values ca be defied for each table etry. Example 0001 or 01 refresh time Descriptio Example 5 This field specifies the amout of time (i secods) that a retrieved dataset is cosidered valid. No fetch from the database will be made if the same request is made withi this time. DB2 for OS/390 Istallatio Guide for BAAN IV 3-6

27 DB2 database driver iterals ad exterals storage parameters Descriptio Example These are defied by the specific database driver implemetatios ad ofte map to table ad idex creatio optios available i DB2. Refer to the DB2 for OS/390 SQL Referece for sytax. The followig DB2 storage parameters are defied: T_SPACE Set the tablespace i which the table is to reside. Oly valid whe object type is equal to T. If a T_SPACE parameter is ot specified, data is created i a default tablespace which will be called tableame i the DB2 default database, DBNDB04. Each idex creatio always creates a ew ad separate idex space, ad its locatio is cotrolled by the STOGROUP parameter. DB2 STOGROUPs idetify a set of disk volumes by ame, or ca idetify ad SMS (System Maaged Storage) group ame. OPTIMIZE Whe this parameter is specified, SELECT statemets for this table will iclude the OPTIMIZE clause. Oly valid whe object type is equal to T. STOGROUP Defies the STOGROUP to be used for idex creatio i the CREATE INDEX statemet. Oly valid whe object type is equal to I. PRIQTY Defies the primary space allocatio parameters i Kbytes for idex creatio i the CREATE INDEX statemet. Oly valid whe object type is equal to I. SECQTY Defies the secodary space allocatio parameters i Kbytes for idex creatio i the CREATE INDEX statemet. Oly valid whe object type is equal to I. BUFFERPOOL Sets the BUFFERPOOL to be used by the idex. Oly valid whe object type is equal to I. DEFER Idicates whether the idex is built durig the executio of the CREATE INDEX statemet. FREEPAGE Specifies how ofte to leave a page of free space whe creatig a idex for a table with existig rows. PCTFREE Determies the percetage of free space to leave. BUFFERPOOL BP2 T_SPACE baadb.baats 3-7

28 DB2 database driver iterals ad exterals NOTE The storage file is scaed from the begiig wheever a create table or create idex is performed. The first etry that matches the table or idex is take, so the order i which the etries are specified is importat. For example: {mary,joh}ttadv999,ttadv000:000:t:private: 01:5: OPT_ROWS 5 T_SPACE userspace1 {mary,joh}ttadv999,ttadv000:000:i::01:5: STOGROUP baagrp tdsfc:505:t:group:01:5: *:*:T:group:01:5: OPT_ROWS 5 T_SPACE dataspace1 *:*:I:group:01:: I the example above, the users mary ad joh will create tables ttadv999 ad ttadv000 of compay 000 i tablespace userspace1. The associated idexes will be created i STOGROUP baagrp. All users creatig tables i module tdsfc will create tables ad idexes i the default tablespace. Other users create tables i tablespaces dataspace1. NOTE: Security The followig security aspects ca be distiguished: Coectio autheticatio BAAN IV users establish what is kow as a local coectio to DB2. Sice, i this case, the user is already logged o to OS/390, it is optioal as to whether further coectio or sig-o authorizatio is doe. If desired, this ca be established by defiig the DSNR resource class ad appropriate db2_ssid.batch ad db2_ssid.rrsaf profiles i the SAF. Baa users are the grated access to these profiles for access to a particular DB2 subsystem. Baa o OS/390 supports both Call Attach Facility (CAF) ad Resource Recoverable Services (RRSAF) coectios. CAF uses oly the coectio autheticatio. RRSAF uses both coectio ad sig-o autheticatio. See Chapter 2, DB2 Attach Cosideratios for DB2 attach cosideratios. For Baa, sig-o autheticatio is redudat sice the Baa user idetity ever chages for the life of the Baa user logo. Full details o coectio authorizatio ca be foud i the DB2 for OS/390 Admiistratio Guide, SC I summary, coectio authorizatio for Baa is ot required because password verificatio has bee doe at logo time, ad idividual DB2 object (TABLES, PLAN NAMES, etc) security is still required. DB2 object security is detailed below. For compatibility with DB2 UDB versio V, the user ame ad password of each BAAN IV userid which coects to DB2 is maitaied i the $BSE/lib/db2/db2_users file. DB2 for OS/390 Istallatio Guide for BAAN IV 3-8

29 DB2 database driver iterals ad exterals NOTE Object security I DB2, whe a user creates a object (for example, a table): The user becomes the ower of the object Oly the ower ca access the object Other users ca access the table if they have bee grated privileges I a BAAN IV eviromet where may users access the same tables i the DB2 database, a mechaism exists which allows users to share these tables. The group cocept To allow differet users the ability to share the same table, Baa for OS/390 uses the group cocept alog with the System Authoriztio Facility (SAF) of OS/390. The SAF is the security product istalled o OS/390, such as RACF, ACF2, or TOP SECRET. Secodary authorizatio id support should be eabled i the DB2 provided authorizatio exits, DSN3SATH ad DSN3SSGN, durig DB2 istallatio. A sample job, DSNTIJEX, is provided i the sample library, "hlq".sdsnsamp, for this purpose. Process Maager cosideratios Durig coectio (CAF, RRSAF) ad sig-o (RRSAF oly) the list of primary ad secodary ids are established. With CAF, it is importat to ote that the primary authorizatio id is that of the address space as a whole. Whe ruig with the Process Maager compoet of OS/390 UNIX System Services Coectio Scalig, the primary id will be the userid used to start the Process Maager daemo. As this is probably ot the itet, it may be ecessary to alter the DSN3SATH routie to use the security eviromet of the coectig TCB (db driver process). To do this, modify the coectio exit that follows at label SATH024 i member DSN3SATH of hlq.sdsnsamp. Modify the code to look for a ACEE i the TCB before lookig i the ASXB (address space extesio). L R15,PSATOLD-PSA GET CURRENT TCB ADDRESS USING TCB,R15 TELL THE ASSEMBLER ICM R6,B 1111,TCBSENV GET A(ACEE) IF ANY BZ SSGN043 NONE, CHECK THE ASXB DROP R15 DON T NEED THIS ANYMORE CLC ACEEACEE,EYEACEE DOES IT LOOK LIKE AN ACEE? This example is based o a RACF secodary authorizatio exit, but should be geerally applicable. A table ca be created with a group schema or with a private schema. Whe a table is idetified as a private table, the user becomes the ower, ad o privileges are give to other users. Whe a table is idetified as a group table, the table is created uder the group schema. The group ame must be a SAF defied group. Users coected to that group iherit the privileges of a table creator. 3-9

30 DB2 database driver iterals ad exterals Other SAF groups must be grated the appropriate access to the ew table. Whether a table is private table or a group table is defied i $BSE/lib/db2/db2_storage file. Oce the correct security eviromet is propagated at coect time, SAF defied groups ca the be used as secodary ids for authorizatio to DB2 objects. Multiple groups for a user are allowed oly if the list of groups optio is eabled i the SAF product. Otherwise, oly the default SAF group of the OS/390 user ca be used for DB2 object authorizatio. The members of the group ca perform the operatios grated to a group. Users are assiged to a particular group ad as a result they iherit the privileges grated to the group. The advatage of havig a group table is that the members of the group ca share ad operate o the table data. For example, users peter ad joh ca both be assiged to group baa. As a result users peter ad joh iherit the privileges o the group tables allowig them to access ad maipulate group table data. If a table is idetified as a private table, the DDL statemets geerated by the driver do ot specify to which schema a object is goig to belog (that is, o <user>.<object> statemet is geerated>). The user s userid becomes the shema for the table. For group tables, the group ame is used for the shema. A SAF group must be defied with the ame of the group ame. Idividual Baa users could be coected to this group. Graularity ca be effected by usig multiple groups with differet access. Autheticatio exterals All BAAN IV users ad their correspodig DB2 logo ame ad password ad the ame of the group they are assiged to are defied i the file $BSE/lib/db2/db2_users. The format of each etry i this file is: <BAAN IV user>:<db2 user>:<ecrypted UNIX password>:<group ame> This file is left oly for compatibility with the DB2 UDB driver supplied by Baa for the RS/6000, NT servers, ad other platforms. A <DB2 user> is ot required but the delimitig colos must exist for proper sytax. The ecrypted password ca be aythig (but must exist), as it is igored durig coectio processig. The group logo procedure also icludes a password, which is defied i the file $BSE/lib/db2/db2_groups. The format is: <Group ame>:<ecrypted Group password> DB2 for OS/390 Istallatio Guide for BAAN IV 3-10

31 DB2 database driver iterals ad exterals The group ame must be a SAF defied group. This file is also left oly for compatibility with the DB2 UDB driver supplied by Baa for the RS/6000, NT servers, ad other platforms. The ecrypted password ca be aythig (but must exist), as it is igored durig coectio processig. The group ame will be the table qualifier or schema whe a table is defied as a group table i $BSE/lib/db2/db2_storage. Object security exterals Regardless of the settig i file $BSE/lib/db2/db2_storage, tables i DB2 for OS/390 are owed by the creator. Secodary userid authorizatio ca iclude SAF group ids, which ca be grated appropriate access. Users are coected to these groups i the SAF of OS/390. Security iterals Iterally the DB2 driver uses the SAF group ame to implemet the group cocept. The members of the group automatically iherit the privileges grated by the table ower or system admiistrator to the group. Users will eed to idividually perform SELECT, INSERT, DELETE, ad UPDATE operatios o the group tables. Whe a ew user is added to the group, the user iherits the group privileges, ad there is o eed to explicitly grat privileges o every existig table withi that group. Also, whe a user is dropped from the group, their privileges are revoked. As a result, they ca o loger access the tables owed by that group. If the privileges to operate o the tables were explicitly grated to the user, the they have to be explicitly revoked whe the user is dropped from the group. This overhead is avoided by gratig privileges to the group user providig flexibility ad easy maiteace. DB2 error reportig ad tracig Whe the DB2 driver ecouters a error, a error message is logged i two files i $BSE/log directory, log.db2 ad log.db2.mesg. The error message cotais the DB2 error sqlcode, sqlstate, ad the evet that caused the error. A separate log file, with messages from the Coectio Maager compoet of OS/390 UNIX System Services Coectio Scalig, is available i path $CMX_ERROR_LOG or the default, /tmp/cmx.log. Refer to the OS/390 UNIX System Services Coectio Scalig Referece for iformatio pertaiig to the error log. Sice this file is produced by OS/390, its cotets are EBCDIC. All Baa geerated log files i $BSE/log are also i EBCDIC. 3-11

32 DB2 database driver iterals ad exterals Error reportig The followig iformatio ca be retrieved from this log file. Geeral iformatio (user ame, date, time, source ad lie, ad so o) The error code retured by the database Database error descriptio The BDB error code retured to the applicatio I may cases, a referece to the failig SQL statemet is also logged If a database-specific error occurs, it is mapped to the BDB error code by addig 1000 to it (that is, abs(error_code) ). So, whe a error 818 occurs, BDB error 1818 is retured to the applicatio. For more iformatio o databasespecific errors, you ca check the DB2 for OS/390 Messages ad Codes. I most cases, the various log files i the $BSE/log directory, (for example, log.bshell6.1 ad log.db2), cotai eough iformatio to determie the ature ad cause of a problem. Therefore, wheever a error is ecoutered, you are advised to check the log file of the driver ($BSE/log/log.db2). DB2 Database driver trace iformatio Trace iformatio stored i the log files icludes: Table ad idex iformatio (data dictioary) The SQL statemets beig executed Values of the iput ad output bid variables Other fuctio-level debug statemets Several tracig categories are defied, that tracig ca be eabled for oly those categories that are of iterest. Tracig ca be eabled usig the eviromet variable DBSLOG. Debuggig iformatio will be appeded to the dbs.log file i the curret directory. This file is a EBCDIC file. If this file does ot exist, it will be created. For example, tracig ca be eabled by eterig the followig commad: DBSLOG=0560 The iformatio i the log file is techical ad may be subject to chage. To see what optios are available, refer to Appedix C. DB2 for OS/390 Istallatio Guide for BAAN IV 3-12

33 DB2 database driver iterals ad exterals DB2 database driver profilig ad statistics This sectio describes profilig ad statistics as implemeted i the DB2 database driver. Profilig The profilig optio of the driver provides you with a way to gather timigs of SQL statemets that are beig executed. Loggig all statemets with their timigs, however, will result i a log file that is so big that it caot be properly aalyzed. Therefore, it is possible to defie a loggig threshold. Oly statemets that take loger tha a predefied umber of secods will be logged. Profilig ca be eabled by meas of a eviromet variable. The profilig output will be logged to a file i the curret directory. Suppose the profilig eviromet variable is set to 5 secods; the each statemet that takes loger tha 5.0 secods (real time) will be logged to the log file. The iformatio that is logged i the file is the SQL statemet with the elapsed time ad user, date or time. The maximum precisio that ca be specified with the eviromet variable is 0.01 secods. The value 0.00 meas that all actios are writte to the file. Note that the followig two statemet types are timed ad ca appear i the log file: The execute evet (the amout of time DB2 took to execute a SQL statemet). The fetch evet (the amout of time data is retrieved from the buffer). To activate the profilig of the DB2 driver, the DB2PROF eviromet variable eeds to be defied ad exported. For example: export DB2PROF=5.0 The result of this commad is that each statemet that takes loger tha 5.0 secods (real time) will be logged to the log file. You ca also view the executio times per table by specifyig the DB2PROF eviromet variable i the $BSE/lib/tabledef6.1 file. For example: tccom010:812:db2(db2prof=0.4) I this example, all the queries which require more tha 0.4 secods are logged i the db2prof file. Note that a separate driver is started for this table, because the table is cosidered to have a differet database defiitio. 3-13

34 DB2 database driver iterals ad exterals The profilig report will be logged i the db2prof file i the curret directory. Refer to the sectio Tuig i Appedix A for the profilig report. Statistics The driver also provides a optio to gather driver-wide statistics of actios beig performed, such as the umber of: Cursors (opeed, closed, curret ope) Parses, bids, executes, fetches Logos (sessios) Iserts, updates, deletes Commits, rollbacks For each actio, the cumulative real time spet by the actio ad average time are also logged. The statistics ca be eabled with a eviromet variable. Whe the variable is set to 0, a statistics report is geerated whe the driver termiates (exit from BAAN IV Tools or sessio). Whe a value greater tha 0 is specified, the driver logs a icremetal report each [] secods (driver must be active). The statistics report is writte to a file i the curret directory. To activate the statistics of the DB2 driver, the DB2STAT eviromet variable must be defied ad exported. For example: export export DB2STAT=0 (logs fial report oly) DB2STAT=30 (logs a report each 30 secods) You ca also activate the statistics of the DB2 driver by specifyig the DB2STAT eviromet variable i the $BSE/lib/tabledef6.1 file. For example: tccom010:812:db2(db2stat=0) I this example, ote that a separate driver is started for this table, because the table is cosidered to have a differet database defiitio. The statistics report is logged i the file db2stat i the curret directory. Refer to the sectio Tuig i Appedix A for the statistics report. DB2 driver iterals I this sectio the followig DB2 driver iteral issues are discussed: Iterfaces to DB2 SQL processig DB2 driver lockig strategy DB2 for OS/390 Istallatio Guide for BAAN IV 3-14