IBM DB2 Connect Personal Edition IBM Quick Beginnings Version 6 GC09-2830-00
IBM DB2 Connect Personal Edition IBM Quick Beginnings Version 6 GC09-2830-00
Before using this information and the product it supports, be sure to read the general information under “Appendix H. Notices” on page 173. This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such.
Contents Welcome to DB2 Connect! . How This Book is Structured. Conventions . . . . . . . . . . . . . . . . . . . vii . vii . viii Part 1. Introduction to DB2 Connect . . . . . . . . . . . . Chapter 1. About DB2 Connect . . . . Working with DB2 Data . . . . . . . Accessing Host or AS/400 DB2 Data Using DB2 Connect Personal Edition Connections via Communications Gateway . . . . . . . . . . . Accessing Host or AS/400 DB2 Data from the Desktop Using DB2 Connect Enterprise Edition . . . . . . . .
Step 2. Update the APPC Profiles on the DB2 Connect Workstation . . . . . . . Configuring IBM eNetwork Communications Server for Windows NT Configuring IBM eNetwork Communications Server for Windows NT SNA API Client . . . . . . . . . Configuring Microsoft SNA Server for Windows NT . . . . . . . . . . Configuring Microsoft SNA Client . . . Step 3. Catalog the APPC or APPN Node Step 4. Catalog the Database as a Database Connection Service (DCS) Database . . . Step 5. Catalog the Database . . . . . . Step 6.
Code Page and Language Support Conversion of Character Data . Bidirectional CCSID Support . . Bidirectional-specific CCSIDs . . . . . . . . . . . . . . . . . 159 160 162 163 Appendix F. Naming Rules . . . . . . General Naming Rules . . . . . . . . Database, Database Alias, and Catalog Node Name Rules . . . . . . . . . . . Object Name Rules . . . . . . . . . Username, User ID, Group Name, and Instance Name Rules . . . . . . . . Workstation Name (nname) Rules . . . . DB2SYSTEM Naming Rules . . . . . .
vi Quick Beginnings
Welcome to DB2 Connect! The DB2 Connect Quick Beginnings books provide a focused introduction to the installation and configuration of DB2 Connect products. DB2 Universal Database This Quick Beginnings book will guide you through the planning, installation, migration (if necessary), and setup of a DB2 Connect workstation.
connections. For DB2 Connect installation instructions, see “Part 2. DB2 Connect: Planning and Installation” on page 21. Step 5. After installation, you will establish the connection between DB2 Connect and your host or AS/400 database system. DB2 Connect can locate and configure all TCP/IP and most SNA connections for you. If you are using a supported SNA product that DB2 Connect does not automatically configure, see the chapter in “Part 4.
This icon marks a fast path. A fast path guides you to information specific to your configuration where multiple options are available. This icon marks a tip. It provides additional information that can help you complete a task. For a complete description of the DB2 library, see “Appendix D. How the DB2 Library Is Structured” on page 143.
x Quick Beginnings
Part 1. Introduction to DB2 Connect © Copyright IBM Corp.
2 Quick Beginnings
Chapter 1. About DB2 Connect DB2 Connect Enterprise Edition DB2 Connect Enterprise Edition is a connectivity server that concentrates and manages connections from multiple desktop clients and web applications to DB2 database servers running on host or AS/400 systems. IBM’s DB2 for AS/400, DB2 for OS/390, and DB2 for VSE & VM databases continue to be the systems of choice for managing most critical data for the world’s largest organizations.
Working with DB2 Data As well as providing a relational database to store your data, DB2 lets you issue requests to administer, query, update, insert, or delete data using local or remote client applications. Accessing Host or AS/400 DB2 Data Using DB2 Connect Personal Edition Direct connection without intermediate servers is a very convenient and desirable configuration.
DB2 for MVS DB2 for VSE DB2 for AS/400 DB2 for VM S/390, S/370 AS/400 OS/390 APPC TCP/IP*** MPTN Coax* Ethernet Asynch Twinax** SDLC Token-ring X.25 JDBC SQLJ Emb SQL Application n Application 3 DB2 CLI Application 4 ADO Application 2 ODBC Application 1 DB2 Connect Personal Edition ... Not all protocols are supported for all platforms. * For Host connections only ** For AS/400 *** TCP/IP connectivity requires DB2 for OS/390 V5R1, DB2 for AS/400 V4R2, or DB2 for VM V6.1 Figure 1.
Connections via Communications Gateway Some organizations prefer to concentrate access to SNA networks through dedicated SNA Gateways, such as IBM eNetwork Communications Server, Microsoft SNA Server, or Novell Netware for SAA. DB2 Connect products support connections through gateways, so this can be a good choice if you need terminal emulation and other SNA services not provided by DB2 Connect. Figure 2 on page 7 illustrates such a situation.
DB2 for MVS DB2 for VSE DB2 for AS/400 DB2 for VM S/390, S/370 OS/390 AS/400 APPC TCP/IP*** MPTN Coax* Ethernet Asynch Twinax** SDLC Token-ring X.25 ESCON SNA Gateway (eg.
same machine as IBM eNetwork Communications Server or Microsoft SNA Server, and in many cases it can provide a less expensive and better-performing solution. Contact your authorized IBM reseller for additional information about DB2 Connect Enterprise Edition. Accessing Host or AS/400 DB2 Data from the Desktop Using DB2 Connect Enterprise Edition A DB2 Connect server enables DB2 clients on a LAN access to data that is stored on host or AS/400 systems.
Java applets. In addition, you can use a wide range of off-the-shelf or custom-developed database applications with DB2 Connect and its associated tools. For example, you can use DB2 Connect products with: v Spreadsheets, such as Lotus 1-2-3 and Microsoft Excel, to analyze real-time data without having the cost and complexity of data extract and import procedures. v Decision support tools, such as Business Objects, Brio and Cognos, and Crystal Reports, to provide real-time information.
DB2 for MVS DB2 for VSE DB2 for AS/400 DB2 for VM S/390, S/370 OS/390 AS/400 APPC TCP/IP*** MPTN Coax* Ethernet Asynch Twinax** SDLC Token-ring X.25 ESCON DB2 Run-Time Client ... Application n APPC, Named Pipes, NetBIOS, IPX/SPX, TCP/IP Application 2 Communication Support Application 1 DB2 Connect Enterprise Edition DB2 Administration Client Not all protocols are supported for all platforms.
DB2 for MVS DB2 for VSE DB2 for AS/400 DB2 for VM S/390, S/370 OS/390 AS/400 APPC TCP/IP*** MPTN Coax* Ethernet Asynch Twinax** SDLC Token-ring X.25 ESCON ... Application n Application Business Logic Application 2 TP Monitor (eg. CICS, ENCINA, MTS) Application 1 DB2 Connect Enterprise Edition TP Monitor Client Not all protocols are supported for all platforms.
DB2 for MVS DB2 for VSE DB2 for AS/400 DB2 for VM S/390, S/370 OS/390 AS/400 APPC TCP/IP*** MPTN Coax* Ethernet Asynch Twinax** SDLC Token-ring X.25 ESCON ... Application n Java Servlets, JSP, Enterprise Java Beans Application 2 WebSphere Web Server Application 1 DB2 Connect Enterprise Edition Web Browser Not all protocols are supported for all platforms. * For Host connections only ** For AS/400 *** TCP/IP connectivity requires DB2 for OS/390 V5R1, DB2 for AS/400 V4R2, or DB2 for VM V6.
DB2 for MVS DB2 for VSE DB2 for AS/400 DB2 for VM S/390, S/370 OS/390 AS/400 APPC TCP/IP*** MPTN Coax* Ethernet Asynch Twinax** SDLC Token-ring X.25 ESCON ... Application n ASPs, COM Objects Application 2 ADO IIS & MTS Application 1 DB2 Connect Enterprise Edition Windows NT Server 4.0 with Option Pack 2 Web Browser Not all protocols are supported for all platforms.
Accessing DB2 Data from the Web Using Java Java Database Connectivity (JDBC) and Embedded SQL for Java (SQLJ) are provided with DB2 to allow you to create applications that access data in DB2 databases from the Web. Programming languages containing embedded SQL are called host languages.
DB2 for MVS DB2 for VSE DB2 for AS/400 DB2 for VM S/390, S/370 AS/400 OS/390 APPC TCP/IP*** MPTN Coax* Ethernet Asynch Twinax** SDLC Token-ring X.25 ESCON DB2 JDBC Applet Server ... Application n JDBC driver Application 2 Web Server Application 1 DB2 Connect Enterprise Edition Java-enabled Web Browser Not all protocols are supported for all platforms. * For Host connections only ** For AS/400 *** TCP/IP connectivity requires DB2 for OS/390 V5R1, DB2 for AS/400 V4R2, or DB2 for VM V6.
For more information on Java enablement, refer to the DB2 Java Enablement web page at http://www.software.ibm.com/data/db2/java/. For more information on the JDBC API, point your browser to http://splash.javasoft.com/. Accessing DB2 Data from the Web Using Net.Data Net.Data is provided with DB2 to allow you to create applications that access data in DB2 databases from the Web. Use Net.Data to create applications that are stored on a Web server and viewable from any Web browser.
DB2 for MVS DB2 for VSE DB2 for AS/400 DB2 for VM S/390, S/370 OS/390 AS/400 APPC TCP/IP*** MPTN Coax* Ethernet Asynch Twinax** SDLC Token-ring X.25 ESCON Net.Data Templates ... Application n Net.Data Application 2 Web Server Application 1 DB2 Connect Enterprise Edition Web Browser Not all protocols are supported for all platforms. * For Host connections only ** For AS/400 *** TCP/IP connectivity requires DB2 for OS/390 V5R1, DB2 for AS/400 V4R2, or DB2 for VM V6.1 Figure 8. Net.
Managing Connections to Databases Using the Client Configuration Assistant The Client Configuration Assistant (CCA) helps you manage your database connections to remote servers. The CCA is available on OS/2 and Windows 32-bit operating systems. This is the preferred method to set up any OS/2, Windows 9x, or Windows NT client to communicate with a server. You can use the command line processor to set up DB2 clients on any platform. For more information, refer to the Installation and Configuration Supplement.
Through a DB2 client, these applications can access all servers and, by using the DB2 Connect product (or the DB2 Connect functionality supplied with DB2 Enterprise - Extended or DB2 Enterprise Edition), they can also access DB2 Universal Database for AS/400, DB2 Universal Database for OS/390, and DB2 for VSE & VM database servers.
v Net.Data macros containing HTML and SQL. The DB2 CLI/ODBC driver is an optional component during a DB2 client install. It is required to run CLI, ODBC, JDBC, and some SQLJ applications. For more information on running your own applications, refer to the Installation and Configuration Supplement.
Part 2. DB2 Connect: Planning and Installation © Copyright IBM Corp.
22 Quick Beginnings
Chapter 2. Planning for Installation If you know that your system meets all the hardware and software requirements, and you want to begin installing your DB2 product right away, go to “Chapter 4. Installing DB2 Connect on Windows 9x or Windows NT” on page 31 or “Chapter 3. Installing DB2 Connect on OS/2” on page 27. For information on the DB2 family of products, see “Chapter 1. About DB2 Connect” on page 3. There are many components that you might want to use in your environment.
For information about space requirements for data, refer to the Administration Guide. Estimating Fixed Disk Requirements To estimate the disk requirements for a particular configuration, add the recommended minimum disk sizes for the products and components that you want to install. Include an allowance for your application data. Components Use Table 1 to estimate the amount of disk space you need to install DB2 and associated components on your operating system. Table 1.
v Whether you will be using a direct connection (see “Accessing Host or AS/400 DB2 Data Using DB2 Connect Personal Edition” on page 4), or connections via an SNA gateway (see “Connections via Communications Gateway” on page 6). Product Requirements Table 2 lists the operating system and communications software required for DB2 Connect. Table 2.
Table 2. Software Requirements (continued) Product Hardware/Software Requirements Communications Windows 32-bit Operating Systems v DB2 Connect Personal Edition v Windows 95 Version 4.00.950 or later APPC, TCP/IP, and MPTN (APPC over TCP/IP) v Windows 98 v The Windows NT base operating system provides NetBIOS, IPX/SPX, Named Pipes, and TCP/IP connectivity. v Windows NT Version 4.
Chapter 3. Installing DB2 Connect on OS/2 This section describes how to install DB2 Connect Personal Edition on an OS/2 workstation. For information on how to deploy this product using a distributed installation, refer to the Installation and Configuration Supplement. Before You Begin Before you begin the installation, be sure that you have the following items and information: __ 1. Ensure that your system meets all of the memory, hardware, and software requirements to install your DB2 product.
Step 1. Log on to the system with the user ID that you created to perform the installation. Step 2. Insert the CD-ROM in the drive. Step 3. Open an OS/2 command window and set the directory to your CD-ROM drive by entering the following command: cd x: where x: represents your CD-ROM drive. Step 4. Enter the following command: x:\install where x: represents your CD-ROM drive.
For information on errors encountered during installation, see the l1.log and l2.log files. These files store general information and error messages resulting from installation and uninstall activities. By default, these files are located in the x:\db2log directory; where x: represents the drive on which your operating system is installed. For more information, refer to the Troubleshooting Guide. To set up connections to host or AS/400 database servers, go to one of the following sections: v “Chapter 6.
Upgrading from a Try-and-Buy License To upgrade from a Try-and-Buy license, perform the following steps: Step 1. Start the Control Center. For more information, see “Starting the Control Center” on page 134. Step 2. Click on the License Center icon from the Control Center toolbar. The License Center opens. Step 3. Complete the steps to upgrade your DB2 license. For more information, refer to the License Center’s online help by pressing the F1 key.
Chapter 4. Installing DB2 Connect on Windows 9x or Windows NT This section describes how to install DB2 Connect Personal Edition on Windows 32-bit operating systems. For information on how to deploy this product using a distributed installation or set up a Thin Connect workstation, refer to the Installation and Configuration Supplement. Before You Begin Before you begin the installation, ensure that you have the following items and information: __ 1.
__ 3. For Windows NT, any user account that does not belong to the guests group. This user account will be used to perform the installation. Performing the Installation To install your DB2 product, perform the following steps: Step 1. Log on to the system with the user account that you created to perform the installation. Step 2. Shut down any other programs so that the setup program can update files as required. Step 3. Insert the CD-ROM into the drive.
Step 4. The Welcome window opens. Step 5. Respond to the setup program’s prompts. Online help is available to guide you through the remaining steps. Invoke the online help by clicking on the Help push button or pressing the F1 key at any time. You can click on the Cancel push button at any time to end the installation. For information on errors encountered during installation, see the db2.log file. The db2.
To set up connections to host or AS/400 database servers, go to one of the following sections: v “Chapter 6. Configuring DB2 Connect to Host or AS/400 Communications Using the CCA” on page 57 v “Chapter 7. Configuring APPC Communications on the DB2 Connect Workstation” on page 67 Software Registration The Software Registration tool is used to register IBM Software with IBM and update IBM’s Software Customer Profiles.
Upgrading from a Try-and-Buy License To upgrade from a Try-and-Buy license, perform the following steps: Step 1. Start the Control Center. For more information, see “Starting the Control Center” on page 134. Step 2. Click on the License Center icon from the Control Center toolbar. The License Center opens. Step 3. Complete the steps to upgrade your DB2 license. For more information, refer to the License Center’s online help by pressing the F1 key.
36 Quick Beginnings
Part 3. Preparing Host and AS/400 Databases for DB2 Connect Communications © Copyright IBM Corp.
38 Quick Beginnings
Chapter 5. Configuring Host and AS/400 Databases for DB2 Connect This section describes the steps required to configure host and AS/400 database servers to accept connections from DB2 Connect workstations. These steps must be performed by users who have the necessary system privileges and special expertise, such as your network or system administrator and your DB2 administrator.
Many details of these steps have changed with the introduction of DB2 Universal Database for OS/390 Version 5.1. Most of these steps apply to SNA users, but some also apply to users who will connect to DB2 Universal Database for OS/390 via TCP/IP. For a summary of the example VTAM names used throughout this book, see “Sample Network Element Names (VTAM)” on page 41. For TCP/IP names, see “Configuring TCP/IP for DB2 Universal Database for OS/390” on page 47.
Sample Network Element Names (VTAM) Figure 9 shows the sample VTAM definitions used to configure a host database server. DB2 Connect Server: - Network ID - Local Node Name - Local Node ID - LU Name HOST: : SPIFNET : NYX1 : 05D27509 (PU name) - LU Alias : SPIFNET.NYX1GW01 (the same LU is used for DB2 Connect, for DB2 Universal Database, and for the SPM) : NYX1GW01 - Network ID - Node Name : SPIFNET : NYX - LU Name : SPIFNET.
----+----1----+----2----+----3----+----4----+----5----+----6----+----7-DB2APPLS VBUILD TYPE=APPL NYM2DB2 APPL APPC=YES, AUTH=(ACQ), AUTOSES=1, DLOGMOD=IBMRDB, DMINWNL=512, DMINWNR=512, DSESSLIM=2048, EAS=6000, MODETAB=RDBMODES, PARSESS=YES, PRTCT=SFLU, MODETAB=RDBMODES, SECACPT=ALREADYV, SRBEXIT=YES, VERIFY=NONE, VPACING=8 X X X X X X X X X X X X X X X Figure 10.
----+----1----+----2----+----3----+----4----+----5----+----6----+----7-SWITCHED MAJOR NODE DEFINITION FOR PU NYX1 and INDEPENDENT LU NYX1GW01 LOC300 NYX1 VBUILD TYPE=LOCAL ADDR=01,IDBLK=071,IDNUM=27509,ANS=CONT,DISCNT=NO, IRETRY=YES,ISTATUS=ACTIVE,MAXDATA=4302,MAXOUT=7, MAXPATH=1,PUTYPE=2,SECNET=NO,MODETAB=RDBMODES SSCPFM=USSSCS,PACING=0,VPACING=2 NYX1GW01 LOCADDR=000,MODETAB=RDBMODES,DLOGMODE=IBMRDB OTHERLU LOCADDR=002 X X X Figure 11.
----+----1----+----2----+----3----+----4----+----5----+----6----+----7--RDBMODES MODTAB IBMRDB MODEENT LOGMODE=IBMRDB, DRDA DEFAULT MODE TYPE=0, NEGOTIABLE BIND PSNDPAC=X'01', PRIMARY SEND PACING COUNT SSNDPAC=X'01', SECONDARY SEND PACING COUNT SRCVPAC=X'00', SECONDARY RECEIVE PACING COUNT RUSIZES=X'8989', RUSIZES IN-4K OUT-4K FMPROF=X'13', LU6.2 FM PROFILE TSPROF=X'07', LU6.2 TS PROFILE PRIPROT=X'B0', LU6.2 PRIMARY PROTOCOLS SECPROT=X'B0', LU6.2 SECONDARY PROTOCOLS COMPROT=X'D0B1', LU6.
The sections that follow contain examples of commands to update these tables for DB2 Universal Database for OS/390. Work with your DB2 Administrator to determine the updates required for your DB2 Universal Database for OS/390 system. For more information on the DB2 Universal Database for OS/390 Communications Database tables, refer to the DB2 Universal Database for OS/390 SQL Reference. Updating SYSIBM.
The sections that follow contain examples of commands to update these tables. Work with your DB2 Administrator to determine the options required for your DB2 for MVS/ESA system. Updating SYSIBM.SYSUSERNAMES If you want to use secondary authorization IDs, you can use the following SQL command to update this table: INSERT INTO SYSIBM.
where: v NYX1 represents the PU name of server involved v IBMRDB represents the name of VTAM logon mode v 150 represents the maximum number of conversations v Y represents the number of sessions preallocated at startup. This can also be left as N, or blank (the default) for deferred at startup. Configuring TCP/IP for DB2 Universal Database for OS/390 This section describes how to configure TCP/IP communications between your DB2 Connect workstation and DB2 Universal Database for OS/390 Version 5.1 or later.
Collecting Information Before you can use DB2 Connect over a TCP/IP connection, you must collect information about both the host database server and the DB2 Connect workstation. For each host server that you are connecting to via TCP/IP, you must have the following information: v The location of the TCP/IP services file at the DB2 Connect workstation: – On a UNIX system, the location of this file is usually /etc/services.
Example Worksheet: Table 3. Example Worksheet for Planning TCP/IP Connections to DB2 Universal Database for OS/390 Ref. Description Sample Value Your Value User Information TCP-1 User Name A.D.B.User TCP-2 Contact Info (123)-456-7890 TCP-5 User ID ADBUSER TCP-6 Database Type db2390 TCP-7 Connection type (must be TCPIP). TCPIP TCPIP Network Elements at the Host TCP-8 Host name MVSHOST TCP-9 Host IP address 9.21.152.
Configuring the TCP/IP Connection Use the manual steps in this section to complete the configuration and make the connection. Complete the Worksheet: Complete a copy of the example worksheet for each TCP/IP host: 1. Fill in the values to be used for the TCP/IP address and hostname of the DB2 Universal Database for OS/390 host (items 8 and 9). 2. Fill in the values to be used for the TCP/IP address and hostname of the DB2 Connect workstation (items 18 and 19). 3.
v 1ST_CONN, the first database that a connection is established to will be used as the Transaction Manager database for transactions. If this option is used, then the first database connected to must be either a DB2 Universal Database Version 5 or later database, or a DB2 Universal Database for OS/390 Version 5.1 or later database. This is the recommended setting, and it is the default value for TM_DATABASE. v database_name, the named database that is connected to will be used.
CONNECT and BIND: Finally, connect to the target host server and bind the utilities and applications to the server using commands similar to the following in the command line processor: connect to MVSIPDB1 user USERID using PASSWORD bind path/bnd/@ddcsmvs.lst blocking all sqlerror continue blocking all grant public disconnect all where path corresponds to the DB2PATH registry value. These commands are described in detail in the Command Reference.
Display Relational Database Directory Entries Position to . . . . . . Type options, press Enter. 5=Display details 6=Print details Relational Option Database _ __________________ _ DLHX _ JORMT2FA _ JORMT4FD _ JOSNAR7B _ RCHASR7B _ RCHASR7C _ R7BDH3SNA _ RCHASDH3 Remote Location Text RCHAS2FA JORMT2FA JORMT4FD RCHASR7B *LOCAL RCHASR7C RCH2PDH3 RCHASDH3 When you have obtained these parameters from OS/400, enter your values into the worksheet that follows: Table 4.
54 Quick Beginnings
Part 4. Configuring DB2 Connect to Communicate with Host and AS/400 Databases © Copyright IBM Corp.
56 Quick Beginnings
Chapter 6. Configuring DB2 Connect to Host or AS/400 Communications Using the CCA This section describes how to use the Client Configuration Assistant (CCA) to configure your DB2 Connect workstation to access host or AS/400 DB2 databases. The configuration steps described in this section apply if you are connecting to the host or AS/400 system using TCP/IP or SNA (APPC).
v Change your server password. The CCA provides three methods to set up a database connection to a server: v Using a profile. v Searching the network for databases. v Manually entering database and communication protocol information for a server. When you add a database using this configuration method, the Client Configuration Assistant will generate a default node name for the server where the database resides.
Adding a Database Using a Profile A profile contains information about instances and databases on a system, and databases within each instance. For information on profiles, see “Creating and Using Profiles” on page 112. If your administrator provided you with a profile, perform the following steps: Step 1. Select the Use an access profile radio button and click on the Next push button. Step 2. Click on the ... push button and select a profile. Step 3.
c. If you would like to create an ODBC data source file to share database access, select the Create a file data source check box and enter the path and filename for this file in the File data source name field. d. Click on the Optimize for application drop down box and select the application for which you want to tune the ODBC settings. e. Click on the Done push button to add the database that you selected. The Confirmation window opens. Step 8.
The Client Configuration Assistant may be unable to detect a remote system if: v The Administration Server is not running on the remote system. v The Discovery function times out. By default, the Discovery function will search the network for 40 seconds; this may not be long enough to detect the remote system. You can set the DB2DISCOVERYTIME registry variable to specify a longer period of time.
Step 8. Register this database as an ODBC data source. If you are not planning to use ODBC, click on the Done push button and go to the next step. a. Ensure that the Register this database for ODBC check box is selected. b. Select the radio button that describes how you would like to register this database: v If you would like all users on your system to have access to this data source, select the As a system data source radio button.
Step 1. Select the Manually configure a connection to a DB2 database radio button and click on the Next push button. If you are not using Lightweight Directory Access Protocol (LDAP), this tab will not be shown, skip this step and go to Step 3. Step 2. Select the radio button that corresponds to the location where you would like your DB2 directories to be maintained.
v If you would like all users on your system to have access to this data source, select the As a system data source radio button. v If you would like only the current user to have access to this data source, select the As a user data source radio button. c. If you would like to create an ODBC data source file to share database access, select the Create a file data source check box and enter the path and filename for this file in the File data source name field. d.
Step 3. Select the database that you want to bind the utilities and packages against. Step 4. Click on the Bind push button. Step 5. Select the type of bind that you want to perform: v Select the Bind DB2 utilities radio button if you want to bind utilities against the database v Select the Bind applications radio button if you want to bind applications against the database Step 6. Click on the Continue push button. Step 7. Enter a user ID and password to connect to the database. Step 8.
66 Quick Beginnings
Chapter 7. Configuring APPC Communications on the DB2 Connect Workstation This section describes how to configure a DB2 Connect workstation to communicate with a host or AS/400 database server using the APPC communication protocol. The instructions that follow assume that APPC is supported on the DB2 Connect and host or AS/400 machines. You will only need to refer to the instructions in this section if you wish to configure your APPC connection to a host or AS/400 database by hand.
Note: The worksheet and configuration instructions supply suggested or sample values for required configuration parameters. For other parameters, use the communications program’s default values. If your network configuration is different from that used in the instructions, consult your Network Administrator for values that are appropriate to your network. In the configuration instructions, the * symbol denotes entries that need to be changed but do not have a representation on the worksheet. Table 5.
Table 5. Worksheet for Planning Host and AS/400 Server Connections (continued) Ref.
4. For database name (5 ), determine the name of the host database. This is the LOCATION NAME for OS/390 or MVS, the RDB_NAME for VM or VSE, or a relational database name for AS/400. 5. For mode name (6 and 15 ), usually the default IBMDRB is sufficient. 6. For remote network address (8 ), determine the controller address or local adapter address of the target host or AS/400 system. 7. Determine the local control point name (10 ) of the DB2 Connect workstation.
__ 1. It is Version 5.0 or higher if you are planning to update multiple databases within the same transaction; if you are planning to use 2-phase commit then Version 5.01 of CS/NT is required __ 2. The IBM Communications Server IEEE 802.2 LAN interface was installed (this is an installation option for Communications Server) __ 3. The APAR fixes JR11529 and J$11170 were applied. These fixes are required to enable cancelling of queries in progress by using Ctrl-BREAK or issuing the SQLCancel ODBC/CLI call.
window. To configure IBM eNetwork Personal Server for APPC communications, complete the perform the following steps: Step 1. Configure Node a. In the Configuration options field, select Configure Node, then click on the New push button. The Define the Node window appears. b. In the Fully qualified CP name fields, type in the network name (9 ) and the local control point name (10 ) (SPIFNET.NYX1). c. Optionally, in the CP alias field, type in a CP alias.
f. Click on OK. Step 2. Configure Devices a. In the Configuration options field, select Configure devices. b. Ensure that in the DLCs field, the appropriate DLC is highlighted. For example, LAN. c. Click on the New push button. The appropriate window appears with default values displayed. For example, the Define a LAN device window. d. Click on OK to accept the default values. Step 3. Configure the Gateway a.
c. In the Partner LU alias field, type in the partner LU name (2 ) from the worksheet (NYM2DB2). d. If you are configuring Communications Server for SNA Clients, in the Fully-qualified CP name fields, type in the network ID (3 ) and the adjacent control point SSCP name (4 ) (SPIFNET.NYX). Leave the other fields blank. e. Click on OK. Step 6. Configure Modes a. In the Configuration options field, select Configure modes, then click on the New button. The Define a mode window appears. b.
v To specify a service TP, in the TP name field, type in the name of the service TP, for example 076DB, and ensure that there is a check mark in the Service TP check box. Accept the defaults for the other fields. f. Click on OK. Step 9. Save the Configuration a. Select File->Save as from the menu bar. The Save As window appears. b. Type in a file name, for example ny3.acg c. Click on OK. d. In the window that opens you are asked if you want this configuration to be the default. Click on the Yes push button.
To automatically start Communications Server when the machine is booted, you can register it as a Windows NT Service. To register Communications Server as an NT service execute one of the following commands: csstart -a to register Communications Server with the default configuration, or: csstart -a c:\ibmcs\private\your.acg where c:\ibmcs\private\your.acg represents the fully qualified name of the non-default Communications Server configuration file you want to use.
To configure the Windows NT SNA API client for APPC communications, complete the following steps: Step 1. Create a user account for the SNA API client on the Communications Server for Windows NT server a. Click on the Start button and select Programs->Administrative Tools (Common)->User Manager. The User Manager window opens. b. Select Users->New User from the menu bar. The New User window opens. c. Fill in the fields for the new SNA client user accout.
SNA Client Configuration window opens. Step 3. Configure Global Data a. In the Configuration options box, select the Configure Global Data option and click on the New push button. The Define Global Data window opens. b. Enter the user name for the SNA API client in the User name field. This is the user name that was defined in Step 1. c. Enter the password for the user account in the Password and Confirm Password fields. d. Click on OK. Step 4. Configure APPC Server List a.
b. Type in the IP address of the server (for example, 123.123.123.123). c. Click on OK. Step 5. Configure CPI-C Side Information a. In the Configuration options box, select the Configure CPI-C side information option and click on the New push button. The Define CPI-C side information window opens. b. Enter the symbolic destination name (16 ) in the Symbolic destination name field. c. Enter your Local LU alias (12 ) in the Local LU alias field. d. Enter the mode name (15 ) in the Mode name field. e.
similar to that of the Windows NT Explorer. The following illustration shows the interface. There are two panes in the main window of the Server Manager. All the configuration options we will be using can be accessed by right-clicking on objects in the left-hand pane of the window. Every object has a context menu that you can access by right-clicking on the object. To configure APPC communications for use by DB2 Connect using Microsoft SNA Server Manager, perform the following steps: Step 1.
a. Right-click on the SNA Service icon and select the Insert->Link Service option. The Insert Link Service window opens. b. Select DLC 802.2 Link Service. c. Click on the Add push button. d. Click on the Finish push button. Step 4. Define the connection properties Chapter 7.
a. Right-click on SNA Service and select the Insert->Connection>802.2 option. The Connection Properties window opens. b. Enter a connection name (7 ) in the Name field. c. Click on the Link Service drop-down box and select the SnaDlc1 option. d. Select the Remote End radio button from the Host System box. e. Select the Both Directions radio button from the Allowed Directions box. f. Select the On Server Startup radio button from the Activation box.
g. Select the Address tab. h. Fill in the Remote Network Address field (8 ). Accept the default numbers in the other fields. i. Select the System Identification tab. j. Enter the following information: 1) For the Local Node Name, add the Network ID (9 ), the Local PU Name (10 ), and the Local Node ID (1 plus 14 ). Accept the XID Type default. 2) For the Remote Node Name, add the NETID (1 ) and the Control Point Name (4 ). Accept the other defaults k. Click on OK. Step 5. Define a local LU a.
window opens. b. Enter the following information: v The LU Alias (12 ). v The NETID (9 ). v The LU Name (11 ). c. Select the Advanced tab. d. Select the Member of Default Outgoing Local APPC LU Pool option. Accept the other defaults. e. Click on OK. Step 6. Define a remote LU a. Right-click on SNA Services icon and select the Insert->APPC->Remote LU option. The Remote APPC Lu Properties window opens. b. Click on the Connection drop down box and select the appropriate connection name (7 ). c.
Step 7. Define a mode a. Right-click on APPC Modes folder and select the Insert->APPC->Mode Definition option. The APPC Mode Properties window opens. b. Enter the Mode Name 6 in the Mode Name field. c. Select the Limits tab. Chapter 7.
d. Enter appropriate numbers for the Parallel Session Limit and Minimum Contention Winner Limit fields. Your Host-Side or LAN administrator should be able to supply you with the numbers if you do not know the limits you should place here. e. Accept the other defaults, and click on OK. Step 8. Define the CPIC name properties a. Right-click on CPIC Symbolic Name folder icon and select the Insert->APPC->CPIC Symbolic Name option. The CPIC Name Properties window opens. b.
d. Select the Partner Information tab. e. In Partner TP Name box, select the SNA Service TP (in hex) radio button and enter the Service TP name (17 ), or select the Application TP radio button and enter the Application TP name (17 ). f. In the Partner LU Name box, select the Fully Qualified radio button. g. Enter the fully-qualified Partner LU Name (1 and 2 ) or alias. h. Click on OK. i. Save the configuration 1) Select File->Save from the menu bar of the Server Manager window.
Configuring Microsoft SNA Client Read this section if you have a Windows NT workstation that has DB2 Connect installed. This section provides step-by-step instructions for setting up the communications between your DB2 Connect workstation and a Windows NT workstation that has Microsoft SNA Server V4.0 (or later) installed. For instructions on how to configure Microsoft SNA Server Version 4.0 for Windows NT, go to “Configuring Microsoft SNA Server for Windows NT” on page 79.
DB2 for MVS DB2 for VSE DB2 for AS/400 DB2 for VM S/390, S/370 OS/390 AS/400 APPC TCP/IP*** MPTN Coax* Ethernet Asynch Twinax** SDLC Token-ring X.25 ESCON SNA Gateway (eg. IBM eNetwork Communications Server, Microsoft SNA Server) IPX/SPX, NetBIOS TCP/IP DB2 Connect Enterprise Edition with SNA Gateway client software * For Host connections only ** For AS/400 *** TCP/IP connectivity requires DB2 for OS/390 V5R1, DB2 for AS/400 V4R2, or DB2 for VM V6.1 Figure 13.
2. Microsoft SNA Client Version 2.11 is not already installed on your DB2 Connect workstation. To configure the Microsoft SNA client perform the following steps: Step 1. Obtain Required Information For your Microsoft SNA client software to function properly you must have access to a properly configured Microsoft SNA Server. Request that your SNA Server administrator: Step 1. Obtain the proper license for you to use Microsoft SNA Client on your workstation. Step 2.
__ a. The Symbolic destination name (16 ) defined at the Microsoft SNA Server for the Partner LU (2 ) of the target host or AS/400 database server. __ b. The real database name (5 ). You now need to update the DB2 directories, bind utilities and applications to the server, and test the connection. The easiest way to do this is to use the Client Configuration Assistant (CCA). For more information on using the CCA, go to “Chapter 6.
program name (17 ), the mode (15 ), and the security type. Enter the following commands substituting your values from the worksheet in Table 5 on page 68: catalog "appn node db2node network SPIFNET remote NYM2DB2 tpname QCNTEDDM mode IBMRDB security PROGRAM" terminate Note: To connect to DB2 for MVS, it is recommended that you use security PROGRAM. If you need to change values that were set with the catalog node command, perform the following steps: Step 1.
database name (database_name). The information in the database directory, along with the information in the node directory, is used on the DB2 Connect workstation to establish a connection to the remote database. To catalog a database on the DB2 Connect Workstation, perform the following steps. Step 1. Log on to the system as a user with System Administrative (SYSADM) or System Controller (SYSCTRL) authority. Step 2. Fill in the Your Value column in the following worksheet. Table 6.
If you need to change values that were set with the catalog database command, perform the following steps: Step a. Run the uncatalog database command: uncatalog database database_alias Step b. Recatalog the database with the value that you want to use. Step 6. Bind Utilities and Applications to the Database Server The steps you have just completed set up the DB2 Connect workstation to communicate with the host or AS/400 system.
The userid and password values required are those defined at the host or AS/400 system, and must be provided to you by your DB2 Administrator. For more information, refer to the DB2 Connect User’s Guide. If the connection is successful, you will get a message showing the name of the database to which you have connected. You are now able to retrieve data from that database.
96 Quick Beginnings
Chapter 8. Enabling Multisite Updates (Two-Phase Commit) This chapter provides an overview of the multisite update function as it applies to scenarios that involve host and AS/400 database servers. It describes products and components needed to implement PC, UNIX and web applications that update multiple DB2 databases in the same transaction.
TP Monitor multisite update can coordinate a transaction that accesses both DB2 and non-DB2 resource managers such as Oracle, Informix, SQLServer, etc. Native SQL multisite update is used with DB2 servers only. For a multisite update transaction to work, each of the databases participating in a distributed transaction must be capable of supporting Distributed Unit of Work.
Host and AS/400 multisite update scenarios that require SPM. Yes TCP/IP Yes v DB2 Connect v DB2 for OS/390 V5.1 Enterprise Edition v DB2 Universal v DB2 Database for Universal OS/390 V6.1 Database Enterprise Edition v DB2 Universal Database EnterpriseExtended Edition Yes SNA Yes v DB2 Connect v DB2 for MVS/ESA Enterprise V3.1 and 4.1 Edition* v DB2 Universal Database Enterprise Edition* v DB2 Universal Database EnterpriseExtended Edition* Note: *AIX, OS/2 and Windows NT platforms only.
Host and AS/400 multisite update scenarios that require SPM. No TCP/IP No v DB2 Connect v DB2 for OS/390 V5.1 Personal Edition v DB2 Universal v DB2 Connect Database for Enterprise OS/390 V6.1 Edition v DB2 Universal Database Enterprise Edition v DB2 Universal Database EnterpriseExtended Edition No SNA Yes v DB2 Connect v DB2 for MVS/ESA Enterprise V3.1 and 4.
1. Set your Web browser to the following URL: http://www.software.ibm.com/data/db2/library/ 2. Select ″DB2 Universal Database″. 3. Search for ″Technotes″ using the search keywords ″DDCS″, ″SPM″, ″MTS″, ″CICS″, and ″ENCINA″. Enabling Multisite Updates Using the Control Center As of Version 6, you can use the Control Center to provide multisite update. The procedure is very simple, and is outlined below.
Step 2. Select the databases you wish to test from the available databases in the left sub-window. You can use the arrow buttons in the middle to move selections to and from the Selected Databases sub-window. Step 3. When you have finished your selection, press the Test... button at the bottom of the window. The Multi-Site Update Test Result window opens. Step 4. The Multi-Site Update Test Result window shows which of the databases you selected succeeded or failed the update test.
Part 5. Configuring DB2 Clients to Use DB2 Connect © Copyright IBM Corp.
104 Quick Beginnings
Chapter 9. Configuring Client-to-Server Communications Using the Client Configuration Assistant To configure communications from a DB2 client to a server, the remote server must be configured to accept inbound client requests. By default, the server installation program automatically detects and configures most protocols on the server for inbound client connections.
When you add a database using this configuration method, the Client Configuration Assistant will generate a default node name for the server where the database resides. Configuration Steps To configure your workstation to access a database on a remote server, perform the following steps: Step 1. Log on to the system with a valid DB2 user ID. For more information, see “Appendix F. Naming Rules” on page 165.
Step 2. Click on the ... push button and select a profile. Step 3. Enter a local database alias name in the Database alias field and add a comment that describes this database in the Comment field. Click on the Next push button. If you do not specify a database alias name, the default will be the same as the remote database alias name. Step 4. Register this database as an ODBC data source. If you are not planning to use ODBC, click on the Done push button and go to the next step. a.
Adding a Database Using Discovery This option cannot return information about pre-Version 5 DB2 systems or any systems where an Administration Server is not running. For more information, refer to the Administration Guide. You can use the Discovery feature to search the network for databases. To add a database to your system using Discovery, perform the following steps: Step 1. Select the Search the network radio button and click on the Next push button. Step 2.
b. Enter the required communication protocol parameters for the remote Administration Server and click on OK. A new system is added. For more information, click on the Help push button. c. Select the database that you want to add and click on the Next push button. Step 4. Enter a local database alias name in the Database alias field and add a comment that describes this database in the Comment field. Click on the Next push button.
Step 8. You are now able to use this database. To finish using the Add Database SmartGuide, click on the Close push button; you can then add more databases by clicking on the Add push button or exit the CCA. Adding a Database Manually If you have the protocol information for the server that you want to connect to, you can manually enter all of the configuration information.
OS/390 or MVS Location name AS/400 RDB name VM or VSE DBNAME When a database is created on the remote server, if a database alias is not specified during database creation, the database is created with a database alias=database_name; otherwise, the database alias is the name that was specified when the database was created. Step 6. Register this database as an ODBC data source. a. Ensure that the Register this database for ODBC check box is selected. b.
have incorrectly specified or click on the Help push button for more information. For even more detailed information, refer to the Troubleshooting Guide. Step 8. Enter your user ID and password and click on OK. If the connection is successful, a message confirming the connection appears. Step 9. You are now able to use this database. To finish using the Add Database SmartGuide, click on the Close push button; you can then add more databases by clicking on the Add push button or exit the CCA.
have the discover_inst database manager configuration parameter and databases with the discover_db database configuration parameter set to ENABLE. The discover parameter in the Administration Server’s configuration file must be set to either SEARCH or KNOWN to generate a profile for a server system. The default settings for these configuration parameters enable you to discover all instances and databases on your network.
A Client Profile is generated from a client using the Export function of the CCA. The information contained in a Client Profile is determined during the export process. Depending on the settings chosen, it can contain the existing client’s: v Database connection information (including CLI or ODBC settings). v Client settings (including database manager configuration parameters, DB2 registry variables). v CLI or ODBC common parameters.
Step 6. Click on OK. The Export Client Profile window opens. Step 7. Enter a path and file name for this Client Profile and click on OK. The DB2 Message window opens. Step 8. Click on OK. To import a Client Profile, perform the following steps: Step 1. Start the CCA. For more information, see “Starting the Client Configuration Assistant” on page 133. Step 2. Click on the Import push button. The Select Profile window opens. Step 3. Select a Client Profile to import and click on OK.
v If you would like all users on your system to have access to this data source, select the As a system data source radio button. v If you would like only the current user to have access to this data source, select the As a user data source radio button. c. If you would like to create an ODBC data source file to share database access, select the Create a file data source check box and enter the path and filename for this file in the File data source name field. d.
Part 6. Using DB2 Connect © Copyright IBM Corp.
118 Quick Beginnings
Chapter 10. Running Your Own Applications Various types of applications can access DB2 databases: v Applications developed using the DB2 Software Developer’s Kit that include embedded SQL, APIs, stored procedures, user-defined functions or calls to the DB2 CLI. v ODBC applications such as Lotus Approach. v JDBC applications and applets. v Net.Data macros containing HTML and SQL. An application on a DB2 client can access a remote database without knowing its physical location.
The bind files are grouped together in different .lst files in the bnd directory, under the installation directory (typically sqllib\win on Windows 3.x systems and sqllib for OS/2, and Windows 32-bit operating systems). Each file is specific to a server. Binding to Host Databases To bind the utilities and applications to the DRDA server, connect to the DRDA server and use commands similar to the following: connect to dbalias user userid using password bind path/bnd/@ddcsmvs.
"bind @db2ubind.lst messages bind.msg grant public" "bind @db2cli.lst messages clibind.msg grant public" In this example, bind.msg and clibind.msg are the output message files, and EXECUTE and BINDADD privileges are granted to public. Step 4. Reset the connection to the database by entering the following command: connect reset For more information on the bind command, refer to the Command Reference. Notes: 1. The db2ubind.lst file contains the list of bind (.
The following general steps are required on the client system to give DB2 CLI and ODBC applications access to DB2 databases. These instructions assume that you have successfully connected to DB2 using a valid user ID and password. Depending on the platform many of these steps are automatic. For complete details, see the section that deals specifically with your platform. Step 1.
Platform Specific Details for CLI/ODBC Access The platform specific details on how to give DB2 CLI and ODBC applications access to DB2 are divided into the following categories: v “Windows 32-bit operating systems Client Access to DB2 using CLI/ODBC” v “OS/2 Client Access to DB2 using CLI/ODBC” on page 125 Windows 32-bit operating systems Client Access to DB2 using CLI/ODBC Before DB2 CLI and ODBC applications can successfully access a DB2 database from a Windows client, perform the following steps on the
d. On Windows 32-bit operating systems you can use the radio buttons to add the data source as either a user or system data source. v Using the Microsoft 32-bit ODBC Administration tool, which you can access from the icon in the Control Panel or by running odbcad32.exe from the command line: a. On Windows 32-bit operating systems the list of user data sources appears by default. If you want to add a system data source click on the System DSN button, or the System DSN tab (depending on the platform). b.
OS/2 Client Access to DB2 using CLI/ODBC Before DB2 CLI and ODBC applications can successfully access a DB2 database from an OS/2 client, perform the following steps on the client system: 1. The DB2 database (and node if the database is remote) must be cataloged. To do so, use the CCA (or the command line processor). For more information see the on-line help in the CCA 2. If you are using ODBC applications to access DB2 data, perform the following steps.
2) Click on the Add push button from the Data Sources window. The Add Data Source Window opens. 3) Double-click on the IBM DB2 ODBC DRIVER in the list. 4) Select the DB2 database to add and click on OK. 3. Configure the DB2 CLI/ODBC driver using the CCA: (Optional) a. Select the DB2 database alias you want to configure. b. Click on the Properties push button. The Database Properties window opens. c. Click on the Settings push button. The CLI/ODBC Settings window opens. d. Click on the Advanced push button.
Running Java Programs You can develop Java programs to access DB2 databases with the appropriate Java Development Kit (JDK) on AIX, HP-UX, Linux, OS/2, Silicon Graphics IRIX, Solaris, or Windows 32-bit operating systems. The JDK includes Java Database Connectivity (JDBC), a dynamic SQL API for Java. For DB2 JDBC support, you must include the DB2 Java Enablement component when you install the DB2 client. With DB2 JDBC support you can build and run JDBC applications and applets.
Configuring the Environment To build and run DB2 Java programs, you need to install and configure the appropriate version of the Java Development Kit (JDK) on your development machine: AIX: The Java Development Kit (JDK) Version 1.1.2 for AIX from IBM. HP-UX: The HP-UX Developer’s Kit for Java Release 1.1.3 or later from Hewlett-Packard. Linux: The Java Development Kit (JDK) 1.1.7, Version 1a or later for Linux from the Blackdown Organization. OS/2: The Java Development Kit (JDK) Version 1.1.
You may want to pipe the output to a file for easier viewing. The JDK11_PATH field appears near the beginning of the output. For more information on these commands, refer to the Command Reference. On Solaris, some Java Virtual Machine implementations do not work well in programs that run in a ″setuid″ environment. The shared library that contains the Java interpreter, libjava.so, may fail to load.
java prog_name where prog_name is the name of the program. The DB2 JDBC driver handles the JDBC API calls from your application and uses the DB2 CAE to communicate the requests to the server and receive the results. An SQLJ application must be bound to the database before it is run. Java Applets Because Java applets are delivered over the web, a web server must be installed on your DB2 machine (server or client). To run your applet, make sure your .html file is properly configured.
Part 7. Appendixes © Copyright IBM Corp.
132 Quick Beginnings
Appendix A. Basic Task Knowledge This section describes the basic tasks that you will need to know to use this product effectively. Go to the task that you want to perform: v “Starting the Software Registration Tool”. v “Starting the Client Configuration Assistant”. v “Starting the Control Center” on page 134. v “Entering Commands Using the Command Center” on page 134. v “Entering Commands Using the Command Line Processor” on page 136. v “Working with the System Administrative Group” on page 138.
Starting the Control Center Start the Control Center in one of the following ways: On OS/2 v Enter the db2cc command at a command prompt. or v Click on the OS/2 Warp button and select DB2 for OS/2–>Control Center. Note: You must have the prerequisite Java Runtime Environment (JRE) level to launch the Control Center using this command. For more information, refer to the Control Center readme, which can be found in the x:\sqllib\cc\prime directory, where x: is drive where you installed your DB2 product.
v Display all the command scripts known to the system through the Script Center, with summary information listed for each. Start the Command Center in one of the follows ways: v Click on the Command Center icon in the Control Center. v Enter the db2cctr command. v Launch the Command Center from the toolbar as follows: On Windows 9x or Windows NT – Click on the Start button and select Programs->DB2 for Windows->Command Center. On OS/2 – Click on the OS/2 Warp button and select DB2 for OS/2 –>Command Center.
To save commands as scripts, select Script->Save as from the menu bar. For more information, click on the Help push button or press the F1 key. If you want to store commonly used SQL statements or DB2 commands as scripts, click on the Script Center icon from the main tool bar. For more information, click on the Help push button or press the F1 key. Entering Commands Using the Command Line Processor You can use the command line processor to enter DB2 commands, SQL statements, and operating system commands.
If the DB2 command contains characters that have special meaning on the operating system you are using, you will need to enter the command in quotation marks to ensure that it is run properly. For example, the following command would retrieve all the information from the employee table, even if the * character has a special meaning on the operating system: db2 "select * from employee" If you need to enter a long command that does not fit on one line, use the line continuation character, \.
db2 => select empno, function, firstname, lastname, birthdate, from \ db2 (cont.) => employee where function='service' and \ db2 (cont.) => firstname='Lily' order by empno desc To end interactive input mode, enter the quit command. For more information on advanced topics using the CLP, refer to the Command Reference.
Appendix B. Using the Control Center to Administer DB2 for OS/390 and DB2 Connect Enterprise Edition servers DB2 Control Center is an easy to use application provided as part of the DB2 Administration Client. The Control Center gives database administrators a powerful tool for managing DB2 Family databases. In Version 6, the Control Center has been greatly enhanced to deliver new management functions to database administrators who need to manage DB2 for OS/390 V5.1 and V6.1 database servers.
Preparing DB2 for OS/390 Servers for the Control Center The DB2 Control Center uses stored procedures to deliver many of its management functions. Therefore, for the control center to function properly each DB2 for OS/390 server that will be managed from the Control Center needs to have stored procedures enabled and the proper stored procedures installed on that server. Consult the DB2 for OS/390 Program Directory for additional information on applying service and required Function Modification Identifiers.
Appendix C. db2cpic.dll - Extended SNA Security Codes on Windows NT and Windows 95 Extended SNA Security Codes were not implemented by some SNA subsystem providers. This may affect customers using one or more of the following: v DB2 Universal Database (UDB) for Windows NT Version 5 (all editions). v DB2 Connect Enterprise Edition for Windows NT Version 5 v DB2 Connect Personal Edition Version 5 (when running on Windows 95 or Windows NT). A new DLL, called db2cpic2.
142 Quick Beginnings
Appendix D. How the DB2 Library Is Structured The DB2 Universal Database library consists of SmartGuides, online help, books and sample programs in HTML format. This section describes the information that is provided, and how to access it. To access product information online, you can use the Information Center. You can view task information, DB2 books, troubleshooting information, sample programs, and DB2 information on the Web.
SmartGuide Helps You to... How to Access... Create Table Select basic data types, and create a primary key for the table. From the Control Center, click with the right mouse button on the Tables icon and select Create->Table using SmartGuide. Create Table Space Create a new table space. From the Control Center, click with the right mouse button on the Table spaces icon and select Create->Table space using SmartGuide. Index Advise which indexes to create and drop for all your queries.
Type of Help Contents Control Center Help Explains the tasks you can From a window or notebook, click the Help push button or press the F1 key. perform in a window or notebook. The help includes prerequisite information you need to know, and describes how to use the window or notebook controls. Client Configuration Assistant Help Event Analyzer Help Command Center Help Message Help Describes the cause of a message, and any action you should take. How to Access...
DB2 Information – Hardcopy and Online The table in this section lists the DB2 books. They are divided into two groups: Cross-platform books These books contain the common DB2 information for all platforms. Platform-specific books These books are for DB2 on a specific platform. For example, there are separate Quick Beginnings books for DB2 on OS/2, on Windows NT, and on the UNIX-based platforms.
Name Description Form Number HTML Directory File Name for Online Book Cross-Platform Books Administration Guide Administration Guide, Design and Implementation contains information required to design, implement, and maintain a database. It also describes database access using the Control Center(whether local or in a client/server environment), auditing, database recovery, distributed database support, and high availability.
Name Description Form Number HTML Directory File Name for Online Book Application Development Guide Explains how to develop applications that access DB2 databases using embedded SQL or JDBC, how to write stored procedures, user-defined types, user-defined functions, and how to use triggers. It also discusses programming techniques and performance considerations. SC09-2845 db2a0 db2a0x60 This book was formerly known as the Embedded SQL Programming Guide.
Name Description Form Number HTML Directory File Name for Online Book Installation and Configuration Supplement GC09-2857 Guides you through the planning, installation, and set up of db2iyx60 platform-specific DB2 clients. This supplement contains information on binding, setting up client and server communications, DB2 GUI tools, DRDA AS, distributed installation, and the configuration of distributed requests and access methods to heterogeneous data sources.
Name Description Form Number HTML Directory File Name for Online Book What’s New Describes the new features, functions, and enhancements in DB2 Universal Database, Version 6.0, including information about Java-based tools. SC09-2851 db2q0 db2q0x60 Platform-Specific Books Administering Satellites Guide and Reference Provides planning, configuration, administration, and usage information for satellites.
Name Description Form Number HTML Directory File Name for Online Book DB2 Enterprise - Extended Provides planning, installation, and Edition for Windows NT configuration information for DB2 Quick Beginnings Enterprise - Extended Edition for Windows NT. Also contains installing and setup information for many supported clients.
Name Description Form Number HTML Directory File Name for Online Book Cross-Platform Sample Programs in HTML Sample programs in HTML Provides the sample programs in HTML format for the programming languages on all platforms supported by DB2 for informational purposes (not all samples are available in all languages). Only available when the SDK is installed. See Application Building Guide for more information on the actual programs. Note: Available in HTML format only.
Swedish Trad. Chinese Turkish s t m 2. For late breaking information that could not be included in the DB2 books: v On UNIX-based platforms, see the Release.Notes file. This file is located in the DB2DIR/Readme/%L directory, where %L is the locale name and DB2DIR is: – /usr/lpp/db2_06_01 on AIX – /opt/IBMdb2/V6.1 on HP-UX, Solaris, SCO UnixWare 7, and Silicon Graphics IRIX – /usr/IBMdb2/V6.1 on Linux. v On other platforms, see the RELEASE.TXT file.
If you have not installed the Information Center, you can open the page by double-clicking on the DB2 Online Books icon. Depending on the system you are using, the icon is in the main product folder or the Windows Start menu. To view online books or sample programs on the SCO UnixWare 7: v DB2 Universal Database for SCO UnixWare 7 uses the native SCOhelp utility to search the DB2 information.
Web. To access this information, you must have a connection to the Web from your system. When you select an item in one of the lists, the Information Center launches a viewer to display the information. The viewer might be the system help viewer, an editor, or a Web browser, depending on the kind of information you select. The Information Center provides some search capabilities, so you can look for specific topics, and filter capabilities to limit the scope of your searches.
v v v v List of books Tables of contents of frequently used books Frequently referenced articles, such as the ALTER TABLE topic The Search form For information about setting up a search, see the NetQuestion Appendix in Installation and Configuration Supplement book. Searching Online Information To search for information in the HTML books, you can do the following: v Click on Search the DB2 Books at the bottom of any page in the HTML books. Use the search form to find a specific topic.
book, simply run it as you would run any other executable program. The result from this step is a printable PostScript file with a file extension of .ps. 3. Ensure that your default printer is a PostScript printer capable of printing Level 1 (or equivalent) files. 4. Enter the following command from a command line: print filename.ps On UNIX-based platforms: 1. Mount the CD-ROM. Refer to your Quick Beginnings manual for the procedures to mount the CD-ROM. 2.
Note: These form numbers only apply if you are ordering books that are printed in the English language in North America. You can also order books individually by the form number listed in “DB2 Information – Hardcopy and Online” on page 146. To order printed versions, contact your IBM authorized dealer or marketing representative, or phone 1-800-879-2755 in the United States or 1-800-IBM-4YOU in Canada.
Appendix E. National Language Support (NLS) This section contains information about configuring national language support for the DB2 Connect product, and includes information on: v Which languages are supported by DB2 Connect Enterprise Edition and DB2 Connect Personal Edition. v How DB2 Connect handles the conversion of data between unalike systems. v How to customize your DB2 Connect workstation for your particular national language environment.
Table 8. Languages and Code Pages (continued) Country Code Language en English es Spanish fi Finnish fr French gr Greek hu Hungarian il Hebrew it Italian jp Japanese kr Korean nl Dutch no Norwegian pl Polish pt Portuguese ru Russian se Swedish si Slovenian tr Turkish tw Traditional Chinese (Taiwan) Conversion of Character Data When character data is transferred between machines, it must be converted to a form that the receiving machine can use.
FOR BIT DATA clause) is not converted. Otherwise all input and output character data is converted if the two machines have different code pages or CCSIDs. For example, if DB2 Connect is used to access DB2 Universal Database for OS/390 or DB2/MVS data, the following happens: 1. DB2 Connect sends an SQL statement and input data to OS/390 or MVS. 2. DB2 Universal Database for OS/390 converts the data to an EBCDIC CCSID and processes it. 3.
Table 9. Workstation Code Page to Host CCSID Conversion (continued) Host CCSIDs Code Page Countries 838 874 Thailand 930, 939, 5026, 5035 932, 942, 943, 954, 5039 Japan 937 938, 948, 950, 964 Taiwan 933, 1364 949, 970, 1363 Korea 935, 1388 1381, 1383, 1386 People’s Republic of China 1112, 1122 921, 922 Estonia, Latvia, Lithuania 1025 915, 1131, 1251, 1283 Belarus 1123 1124, 1125, 1251 Ukraine Notes: 1. Code page 1004 is supported as code page 1252. 2.
Since defaults on different platforms are not the same, problems appear when DB2 data is sent from one platform to another. For example, Windows platforms use LOGICAL UNSHAPED data, while data on OS/390 is usually in SHAPED VISUAL format. Therefore, without any support for these attributes data sent from DB2 Universal Database for OS/390 to DB2 UDB on a Windows 32-bit operating systems workstation displays incorrectly.
X'3F21' X'3F22' X'3F23' X'3F24' 856 862 916 1255 11 11 11 11 Where CDRA String Types are defined: String - Text - Numerical - Orientation - Shaping - Symmetrical Type - Type - Shape - Swapping ---------+-------+------------+-------------+-----------+------------4 Visual Arabic LTR Shaped OFF 5 Implicit Arabic LTR Unshaped ON 6 Implicit Arabic RTL Unshaped ON 7(*) Visual Arabic Contextual(*) Unshaped-Lig OFF 8 Visual Arabic RTL Shaped OFF 9 Visual Passthru RTL Shaped ON 10 Implicit Contextual-L ON 11 Impl
Appendix F.
Database alias names are synonyms given to remote databases. Database aliases must be unique within the System Database Directory in which all aliases are stored. When naming a database or database alias, see “General Naming Rules” on page 165. In addition, the name you specify can only contain 1 to 8 characters. To avoid potential problems, do not use the special characters @, #, and $ in a database name if you intend to have a client remotely connect to a host database.
Using delimited identifiers, it is possible to create an object that violates these naming rules; however, subsequent use of the object could result in errors. For example, if you create a column with a + or − sign included in the name and you subsequently use that column in an index, you will experience problems when you attempt to reorganize the table. To avoid potential problems with the use and operation of your database, do not violate these rules.
v Can contain 1 to 8 characters v Cannot include &, #, and @ v Must be unique within the network DB2SYSTEM Naming Rules DB2 uses the DB2SYSTEM name to identify a physical DB2 machine, system, or workstation within a network. On OS/2, you must specify the DB2SYSTEM name during install. On Windows 32-bit operating systems, you do not need to specify a DB2SYSTEM name; the DB2 setup program detects the NT Computer name and assigns it to DB2SYSTEM.
Appendix G. List Files, Bind Files, and Packages This appendix lists the bind files contained in different .lst files shipped with the product. Although the contents of these lists are similar for each platform, the bind packages are generated specifically for each platform. Each package name can be mapped back to the client platform.
xMz Clients for Macintosh xGz Clients for Silicon Graphics List Files Associated with DRDA Servers The following table lists which bind files are included in the .lst file associated with a particular DRDA host. The package associated with each bind file is also listed: DRDA Server List File OS/390 and MVS ddcsmvs.lst VSE ddcsvse.lst VM ddcsvm.lst OS/400 ddcs400.lst Table 10.
Table 10. DRDA Bind Files and Packages (continued) Component Bind File Name Package Name MVS VM/VSE OS/400 Isolation level NC db2clpnc.bnd sqlc6xyz no no yes REXX Isolation level CS db2arxcs.bnd sqla1xyz yes yes yes Isolation level RR db2arxrr.bnd sqla2xyz yes yes yes Isolation level UR db2arxur.bnd sqla3xyz yes yes yes Isolation level RS db2arxrs.bnd sqla4xyz yes yes yes Isolation level NC db2arxnc.bnd sqla5xyz no no yes Utilities Export db2uexpm.
172 Quick Beginnings
Appendix H. Notices Any reference to an IBM licensed program in this publication is not intended to state or imply that only IBM’s licensed program may be used. Any functionally equivalent product, program or service that does not infringe any of IBM’s intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user’s responsibility.
Trademarks The following terms are trademarks or registered trademarks of the IBM Corporation in the United States and/or other countries: ACF/VTAM ADSTAR AISPO AIX AIXwindows AnyNet APPN AS/400 CICS C Set++ C/370 DATABASE 2 DataHub DataJoiner DataPropagator DataRefresher DB2 DB2 Connect DB2 Universal Database Distributed Relational Database Architecture DRDA Extended Services FFST First Failure Support Technology IBM IMS LAN Distance MVS/ESA MVS/XA OS/400 OS/390 OS/2 PowerPC QMF RACF RISC System/6000 SP S
Microsoft, Windows, Windows NT, Visual Basic, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both. PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or both and is used by IBM Corporation under license. ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, or both.
176 Quick Beginnings
Index A Access Profile creating 113 using 112 accessing data through DB2 Connect 8 through Net.
DB2 Connect User’s Guide 148 DB2 Data Links Manager for AIX Quick Beginnings 151 DB2 Data Links Manager for Windows NT Quick Beginnings 151 DB2 Enterprise - Extended Edition for UNIX Quick Beginnings 150 DB2 Enterprise - Extended Edition for Windows NT Quick Beginnings 150 DB2 Enterprise Edition configuration planning 23 memory requirements 23 DB2 for MVS/ESA updating system tables 44, 45 DB2 library books 146 Information Center 154 language identifier for books 152 late-breaking information 153 online help
partner node name 69 password naming rules 169 planning DB2 configuration 23 DB2 Connect configuration privileges required 138 product descriptions 3 overview 3 protocols APPC 67 PU 70 23 Q Quick Quick Quick NT Beginnings for OS/2 150 Beginnings for UNIX 150 Beginnings for Windows 150 R RDB_NAME (VSE or VM) 70 registering ODBC driver manager 123 relational database name 70 remote link address 70 remote transaction program 70 Replication Guide and Reference 149 restrictions instance name 167 running appl
180 Quick Beginnings
Contacting IBM This section lists ways you can get more information from IBM. If you have a technical problem, please take the time to review and carry out the actions suggested by the Troubleshooting Guide before contacting DB2 Customer Support. Depending on the nature of your problem or concern, this guide will suggest information you can gather to help us to serve you better.
Log on as anonymous. In the directory /ps/products/db2, you can find demos, fixes, information, and tools concerning DB2 and many related products. Internet Newsgroups comp.databases.ibm-db2, bit.listserv.db2-l These newsgroups are available for users to discuss their experiences with DB2 products. CompuServe GO IBMDB2 to access the IBM DB2 Family forums All DB2 products are supported through these forums.
IBMR Part Number: CT6D9NA GC09-2830-00 CT6D9NA Printed in the United States of America on recycled paper containing 10% recovered post-consumer fiber.
