Instruction/ maintenance manual of the product GC09-2830-00 IBM
Go to page of 196
IB M D B2 C o nn ect P e rs o nal Editi o n Qui c k B e gin ning s Ve r s i o n 6 GC09-2830-00 IBM.
.
IB M D B2 C o nn ect P ers o nal Ed i ti o n Qui c k B e gin ning s Ve r s i o n 6 GC09-2830-00 IBM.
Before using this information and the pr oduct it supports, be sure to r ead the general information under “Appendix H. Notices” on page 173. This document contains proprietary information of IBM. It is pr ovided under a license agreement and is pr otected by copyright law .
Contents Welcome to DB2 Connect! ...... v i i How This Book is Structured ...... v i i Conventions ........... viii Part 1. Introduction to DB2 Connect ............ 1 Chapter 1. About DB2 Connect .... 3 W orking with DB2 Data ....... 4 Accessing Host or AS/400 DB2 Data Using DB2 Connect Personal Edition 4 Connections via Communications Gateway .
Step 2. Update the APPC Profiles on the DB2 Connect W orkstation ....... 7 0 Configuring IBM eNetwork Communications Server for W indows NT 70 Configuring IBM eNetwork Communications Server for W indows NT SNA API Client ......... 7 6 Configuring Microsoft SNA Server for W indows NT .
Code Page and Language Support .... 1 5 9 Conversion of Character Data ..... 1 6 0 Bidirectional CCSID Support ...... 1 6 2 Bidirectional-specific CCSIDs ..... 1 6 3 Appendix F . Naming Rules ...... 1 6 5 General Naming Rules ........ 1 6 5 Database, Database Alias, and Catalog Node Name Rules .
vi Quick Beginnings.
W elcome to DB2 Connect! The DB2 Connect Quick Beginnings books provide a focused intr oduction to the installation and configuration of DB2 Connect products. 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.
This icon marks a fast path. A fast path guides you to information specific to your configuration where multiple options ar e 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.
x Quick Beginnings.
Part 1. Introduction to DB2 Connect © Copyright IBM Corp. 1993, 1999 1.
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.
Working with DB2 Data As well as providing a r elational database to stor e your data, DB2 lets you issue requests to administer , query , update, insert, or delete data using local or remote client applications.
In this environment, if you ar e using W indows 32-bit operating systems you can use the DB2 Connect Personal Edition Integrated SNA Support to connect directly to the host or AS/400 servers.
Connections via Communications Gateway Some organizations pr efer to concentrate access to SNA networks through dedicated SNA Gateways , such as IBM eNetwork Communications Server , Microsoft SNA Server , or Novell Netware for SAA.
Although you can use DB2 Connect Personal Edition with SNA gateways, you may find DB2 Connect Enterprise Edition a better choice if you want to use many DB2 Clients.
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.
Java applets. In addition, you can use a wide range of of f-the-shelf or custom-developed database applications with DB2 Connect and its associated tools.
DB2 Run-Time Client DB2 Administration Client DB2 for MVS DB2 for VSE DB2 for VM OS/390 Communication Suppor t APPC , Named Pipes, NetBIOS , IPX/SPX, TCP/IP AS/400 S/390, S/370 Applic a tion 1 Applic a tion 2 Applic a tion n DB2 Connect Enter prise Edition DB2 f or AS/400 Not al l prot oc ols ar e su ppor ted for all pl at for ms.
TP Monitor Client DB2 for MVS DB2 for VSE DB2 for VM OS/390 TP Monitor (eg. CICS , ENCINA, MTS) Application Business Logic AS/400 S/390, S/370 Applic a tion 1 Applic a tion 2 Applic a tion n DB2 Connect Enter prise Edition DB2 f or AS/400 Not al l prot oc ols ar e su ppor ted for all pl at for ms.
Web Bro wser DB2 for MVS DB2 for VSE DB2 for VM OS/390 WebSphere Ja va Servlets, JSP , Enterpr ise Jav a Beans AS/400 S/390, S/370 Applic a tion 1 Applic a tion 2 Applic a tion n DB2 Connect Enter prise Edition DB2 f or AS/400 Not al l prot oc ols ar e su ppor ted for all pl at for ms.
Web Bro wser DB2 for MVS DB2 for VSE DB2 for VM OS/390 ASPs, COM Objects AS/400 S/390, S/370 Applic a tion 1 Applic a tion 2 Applic a tion n DB2 Connect Enter prise Edition DB2 f or AS/400 Not al l prot oc ols ar e su ppor ted for all pl at for ms. ..
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 cr eate applications that access data in DB2 databases from the W eb. Programming languages containing embedded SQL are called host languages.
JDBC and SQLJ applications can be run fr om any system that has a DB2 client installed; a W eb browser and a W eb server are not requir ed. Jav a-enabled W eb Browser DB2 for MVS DB2 for VSE DB2 for V.
For more information on Java enablement, r efer 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.
Web Bro wser DB2 for MVS DB2 for VSE DB2 for VM OS/390 Net.Data Net.Data T emplates AS/400 S/390, S/370 Applic a tion 1 Applic a tion 2 Applic a tion n DB2 Connect Enter prise Edition DB2 f or AS/400 Not al l prot oc ols ar e su ppor ted for all pl at for ms.
Managing Connections to Databases Using the Client Configuration Assistant The Client Configuration Assistant (CCA) helps you manage your database connections to remote servers.
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 requir ed to run CLI, ODBC, JDBC, and some SQLJ applications. For more information on r unning your own applications, refer to the Installation and Configuration Supplement .
Part 2. DB2 Connect: Planning and Installation © Copyright IBM Corp. 1993, 1999 21.
22 Quick Beginnings.
Chapter 2. Planning for Installation If you know that your system meets all the hardwar e and software requir ements, and you want to begin installing your DB2 product right away , go to “Chapter 4. Installing DB2 Connect on W indows 9x or W indows NT” on page 31 or “Chapter 3.
For information about space requir ements for data, r efer to the Administration Guide . Estimating Fixed Disk Requirements T o estimate the disk requirements for a particular configuration, add the recommended minimum disk sizes for the pr oducts and components that you want to install.
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 T able 2 lists the operating system and communications software requir ed for DB2 Connect.
T able 2. Software Requirements (continued) Product Hardware/Software Requirements Communications W indows 32-bit Operating Systems v DB2 Connect Personal Edition v W indows 95 V ersion 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 .
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: r epr esents your CD-ROM drive.
For information on errors encounter ed during installation, see the l1.log and l2.log files. These files store general information and error messages r esulting from installation and uninstall activities. By default, these files are located in the x:db2log dir ectory; where x: repr esents the drive on which your operating system is installed.
Upgrading from a T ry-and-Buy License T o upgrade from a T ry-and-Buy license, perform the following steps: Step 1. Start the Contr ol Center . For more information, see “Starting the Control Center” on page 134. Step 2. Click on the License Center icon fr om the Control Center toolbar .
Chapter 4. Installing DB2 Connect on Windows 9x or Windows NT This section describes how to install DB2 Connect Personal Edition on W indows 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 .
__ 3. For W indows 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 T o 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 4. The W elcome window opens. Step 5. Respond to the setup program’s prompts. Online help is available to guide you through the r emaining steps. Invoke the online help by clicking on the Help push button or pressing the F1 key at any time. Y ou can click on the Cancel push button at any time to end the installation.
T o 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.
Upgrading from a T ry-and-Buy License T o upgrade from a T ry-and-Buy license, perform the following steps: Step 1. Start the Contr ol Center . For more information, see “Starting the Control Center” on page 134. Step 2. Click on the License Center icon fr om the Control Center toolbar .
36 Quick Beginnings.
Part 3. Preparing Host and AS/400 Databases for DB2 Connect Communications © Copyright IBM Corp. 1993, 1999 37.
38 Quick Beginnings.
Chapter 5. Configuring Host and AS/400 Databases for DB2 Connect This section describes the steps requir ed to configur e host and AS/400 database servers to accept connections from DB2 Connect workstations.
Many details of these steps have changed with the introduction of DB2 Universal Database for OS/390 V ersion 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 .
Sample Network Element Names (VT AM) Figure 9 shows the sample VT AM definitions used to configure a host database server . Sample VT AM APPL Definition for OS/390 Figure 10 on page 42 shows the sample VT AM application major node definitions. In most cases, such a definition will already exist with a dif fer ent LU name.
Note: Continuations must begin in column 16, with continuation marks in column 72. Sample VT AM PU and LU Definitions for DB2 Connect If your security policies allow it, it is recommended that you enable DYNPU and DYNLU in VT AM to allow any PU and LU access through VT AM.
Sample VT AM Log Mode Definition for DB2 Figure 12 on page 44 shows the sample VT AM logon mode table definition for the IBMRDB and SNASVCMG modes. Note that this example specifies a 4K RUSIZE , which may not be suitable for your environment (for example, if you are using Ethernet, which has a maximum Frame Size of 1536 bytes).
Y ou must define the SNASVCMG logon mode when using APPC. Configuring DB2 Universal Database for OS/390 Before you can use DB2 Connect, your DB2 Universal Database for OS/390 Administrator must configure DB2 Universal Database for OS/390 to permit connections from DB2 Connect workstations.
The sections that follow contain examples of commands to update these tables for DB2 Universal Database for OS/390. W ork with your DB2 Administrator to determine the updates requir ed for your DB2 Universal Database for OS/390 system.
The sections that follow contain examples of commands to update these tables. W ork with your DB2 Administrator to determine the options r equir ed 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 repr esents the PU name of server involved v IBMRDB repr esents the name of VT AM logon mode v 150 repr esents the maximum number of conversations v Y repr esents the number of sessions pr eallocated at startup. This can also be left as N, or blank (the default) for deferred at startup.
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.
Example W orksheet: T able 3. Example Worksheet for Planning TCP/IP Connections to DB2 Universal Database for OS/390 Ref. Description Sample V alue Y our V alue User Information TCP-1 User Name A.
Configuring the TCP/IP Connection Use the manual steps in this section to complete the configuration and make the connection. Complete the W orksheet: Complete a copy of the example worksheet for each TCP/IP host: 1. Fill in the values to be used for the TCP/IP addr ess and hostname of the DB2 Universal Database for OS/390 host (items 8 and 9).
v 1ST_CONN , the first database that a connection is established to will be used as the T ransaction Manager database for transactions. If this option is used, then the first database connected to must be either a DB2 Universal Database V ersion 5 or later database, or a DB2 Universal Database for OS/390 V ersion 5.
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.
Display Relational Database Directory Entries Position to ...... Type options, press Enter. 5=Display details 6=Print details Relational Remote Option Database Location Text _ __________________ _ DLH.
54 Quick Beginnings.
Part 4. Configuring DB2 Connect to Communicate with Host and AS/400 Databases © Copyright IBM Corp. 1993, 1999 55.
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.
v Change your server password. The CCA provides thr ee methods to set up a database connection to a server: v Using a profile. v Searching the network for databases.
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 “Cr eating and Using Profiles” on page 1 12. If your administrator provided you with a pr ofile, perform the following steps: Step 1.
c. If you would like to create an ODBC data sour ce file to shar e 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.
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.
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.
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 Dir ectory Access Protocol (LDAP), this tab will not be shown, skip this step and go to Step 3. Step 2.
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.
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.
66 Quick Beginnings.
Chapter 7. Configuring APPC Communications on the DB2 Connect W orkstation 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 instr uctions that follow assume that APPC is supported on the DB2 Connect and host or AS/400 machines.
Note: The worksheet and configuration instructions supply suggested or sample values for requir ed configuration parameters. For other parameters, use the communications program’s default values.
T able 5. Worksheet for Planning Host and AS/400 Server Connections (continued) Ref. Name at the DB2 Connect W orkstation Network or VT AM Name Sample V alue Y our V alue 13 Local Node or Node.
4. For database name ( 5 ), determine the name of the host database. This is the LOCA TION 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 suf f icient.
__ 1. It is V ersion 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 V ersion 5.01 of CS/NT is requir ed __ 2. The IBM Communications Server IEEE 802.2 LAN interface was installed (this is an installation option for Communications Server) __ 3.
window . T o configure IBM eNetwork Personal Server for APPC communications, complete the perform the following steps: Step 1. Configur e Node a. In the Configuration options field, select Configure Node , then click on the New push button. The Define the Node window appears.
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 appr opriate DLC is highlighted. For example, LAN . c. Click on the New push button. The appropriate window appears with default values displayed.
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.
v T o 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.
T o automatically start Communications Server when the machine is booted, you can register it as a W indows NT Service. T o 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:ibmcsprivateyour.
T o configure the W indows 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 W indows NT server a. Click on the Start button and select Programs->Administrative T ools (Common)->User Manager .
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.
b. T ype 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.
similar to that of the W indows NT Explorer . The following illustration shows the interface. There ar e 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 .
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 )i nt h e Name field. c. Click on the Link Service drop-down box and select the SnaDlc1 option.
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.
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.
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 W inner Limit fields. Y our 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 .
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 ).
Configuring Microsoft SNA Client Read this section if you have a W indows NT workstation that has DB2 Connect installed. This section provides step-by-step instr uctions for setting up the communications between your DB2 Connect workstation and a W indows NT workstation that has Microsoft SNA Server V4.
The rest of this section assumes: 1. The Microsoft SNA Server has already been configur ed for APPC communications with the host, and is enabled for ODBC and DRDA.
2. Microsoft SNA Client V ersion 2.1 1 is not alr eady installed on your DB2 Connect workstation. T o configure the Microsoft SNA client perform the following steps: Step 1. Obtain Required Information For your Microsoft SNA client software to function pr operly you must have access to a properly configur ed Micr osoft SNA Server .
__ 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 ). Y ou now need to update the DB2 directories, bind utilities and applications to the server , and test the connection.
program name ( 17 ), the mode ( 15 ), and the security type. Enter the following commands substituting your values from the worksheet in T able 5 on page 68: catalog "appn node db.
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. T o catalog a database on the DB2 Connect W orkstation, perform the following steps.
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.
The userid and password values requir ed ar e those defined at the host or AS/400 system, and must be provided to you by your DB2 Administrator . For more information, r efer 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.
96 Quick Beginnings.
Chapter 8. Enabling Multisite Updates (T wo-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 coor dinate a transaction that accesses both DB2 and non-DB2 resour ce managers such as Oracle, Informix, SQLServer , etc.
Host and AS/400 multisite update scenarios that require SPM. Y es TCP/IP Y es v DB2 Connect Enterprise Edition v DB2 Universal Database Enterprise Edition v DB2 Universal Database Enterprise- Extended Edition v DB2 for OS/390 V5.1 v DB2 Universal Database for OS/390 V6.
Host and AS/400 multisite update scenarios that require SPM. No TCP/IP No v DB2 Connect Personal Edition v DB2 Connect Enterprise Edition v DB2 Universal Database Enterprise Edition v DB2 Universal Database Enterprise- Extended Edition v DB2 for OS/390 V5.
1. Set your W eb browser to the following URL: http://www.software.ibm.com/data/db2/library/ 2. Select ″ DB2 Universal Database ″ . 3. Search for ″ T echnotes ″ using the search keywor ds ″ DDCS ″ , ″ SPM ″ , ″ MTS ″ , ″ CICS ″ , and ″ ENCINA ″ .
Step 2. Select the databases you wish to test from the available databases in the left sub-window . Y ou 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 T est.
Part 5. Configuring DB2 Clients to Use DB2 Connect © Copyright IBM Corp. 1993, 1999 103.
104 Quick Beginnings.
Chapter 9. Configuring Client-to-Server Communications Using the Client Configuration Assistant T o configure communications fr om a DB2 client to a server , the remote server must be configured to accept inbound client r equests.
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 r esides. Configuration Steps T o configure your workstation to access a database on a remote server , perform the following steps: Step 1.
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.
Adding a Database Using Discovery This option cannot return information about pr e-V ersion 5 DB2 systems or any systems where an Administration Server is not running. For more information, r efer to the Administration Guide . Y ou can use the Discovery feature to search the network for databases.
b. Enter the requir ed communication pr otocol 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 8. Y ou are now able to use this database. T o 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.
OS/390 or MVS Location name AS/400 RDB name VM or VSE DBNAME When a database is created on the r emote server , if a database alias is not specified during database creation, the database is cr eated with a database alias= database_name ; otherwise, the database alias is the name that was specified when the database was created.
have incorrectly specified or click on the Help push button for mor e information. For even more detailed information, r efer to the T roubleshooting Guide . Step 8. Enter your user ID and password and click on OK . If the connection is successful, a message confirming the connection appears.
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.
A Client Profile is generated fr om 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).
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 . T o import a Client Profile, perform the following steps: Step 1.
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.
Part 6. Using DB2 Connect © Copyright IBM Corp. 1993, 1999 11 7.
11 8 Quick Beginnings.
Chapter 10. Running Y our Own Applications V arious types of applications can access DB2 databases: v Applications developed using the DB2 Software Developer’s Kit that include embedded SQL, APIs, stored procedur es, user-defined functions or calls to the DB2 CLI.
The bind files are gr ouped together in dif ferent .lst files in the bnd dir ectory , under the installation directory (typically sqllibwin on W indows 3.x systems and sqllib for OS/2, and W indows 32-bit operating systems). Each file is specific to a server .
"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 .
The following general steps are r equir ed 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 ar e automatic.
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 “W indows 32-bit.
d. On W indows 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 Contr ol Panel or by running odbcad32.
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.
2) Click on the Add push button from the Data Sour ces window . The Add Data Source W indow 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.
Running Java Programs Y ou 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 W indows 32-bit operating systems. The JDK includes Java Database Connectivity (JDBC), a dynamic SQL API for Java.
Configuring the Environment T o build and run DB2 Java programs, you need to install and configur e the appropriate version of the Java Development Kit (JDK) on your development machine: AIX: The Java Development Kit (JDK) V ersion 1.1.2 for AIX from IBM.
Y ou 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 Refer ence . On Solaris, some Java V irtual Machine implementations do not work well in programs that run in a ″ setuid ″ envir onment.
java prog_name where prog_name is the name of the pr ogram. 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 r eceive the results. An SQLJ application must be bound to the database before it is run.
Part 7. Appendixes © Copyright IBM Corp. 1993, 1999 131.
132 Quick Beginnings.
Appendix A. Basic T ask Knowledge This section describes the basic tasks that you will need to know to use this product ef fectively . Go to the task that you want to perform: v “Starting the Software Registration T ool”. v “Starting the Client Configuration Assistant”.
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 W arp button and select DB2 for OS/2–>Control Center . Note: Y ou must have the prerequisite Java Runtime Envir onment (JRE) level to launch the Control Center using this command.
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.
T o save commands as scripts, select Script->Save as from the menu bar . For more information, click on the Help push button or pr ess 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 .
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 pr operly .
db2 => select empno, function, firstname, lastname, birthdate, from db2 (cont.) => employee where function='service' and db2 (cont.) => firstname='Lily' order by empno desc T o end interactive input mode, enter the quit command.
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 pr ovided as part of the DB2 Administration Client. The Control Center gives database administrators a powerful tool for managing DB2 Family databases.
Preparing DB2 for OS/390 Servers for the Control Center The DB2 Control Center uses stor ed pr ocedures to deliver many of its management functions. Therefor e, for the contr ol center to function pro.
Appendix C. db2cpic.dll - Extended SNA Security Codes on Windows NT and W indows 95 Extended SNA Security Codes were not implemented by some SNA subsystem providers. This may af fect customers using one or mor e of the following: v DB2 Universal Database (UDB) for W indows NT V ersion 5 (all editions).
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. T o access product information online, you can use the Information Center .
SmartGuide Helps Y ou to... How to Access... Create T able Select basic data types, and create a primary key for the table. From the Contr ol Center , click with the right mouse button on the T ables icon and select Create -> T able using SmartGuide .
T ype of Help Contents How to Access... Control Center Help Client Configuration Assistant Help Event Analyzer Help Command Center Help Explains the tasks you can perform in a window or notebook. The help includes prer equisite information you need to know , and describes how to use the window or notebook controls.
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.
Name Description Form Number File Name for Online Book HTML Directory Cross-Platform Books Administration Guide Administration Guide, Design and Implementation contains information requir ed to design, implement, and maintain a database.
Name Description Form Number File Name for Online Book HTML Directory Application Development Guide Explains how to develop applications that access DB2 databases using embedded SQL or JDBC, how to write stored pr ocedures, user -defined types, user-defined functions, and how to use triggers.
Name Description Form Number File Name for Online Book HTML Directory Installation and Configuration Supplement Guides you through the planning, installation, and set up of platform-specific DB2 clients.
Name Description Form Number File Name for Online Book HTML Directory What’s New Describes the new features, functions, and enhancements in DB2 Universal Database, V ersion 6.
Name Description Form Number File Name for Online Book HTML Directory DB2 Enterprise - Extended Edition for Windows NT Quick Beginnings Provides planning, installation, and configuration information for DB2 Enterprise - Extended Edition for W indows NT .
Name Description Form Number File Name for Online Book HTML Directory Cross-Platform Sample Programs in HTML Sample programs in HTML Provides the sample pr ograms in HTML format for the programming languages on all platforms supported by DB2 for informational purposes (not all samples are available in all languages).
Swedish s T rad. Chinese t T urkish 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.
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 pr oduct folder or the W indows Start menu.
W eb. T o access this information, you must have a connection to the W eb 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 W eb browser , depending on the kind of information you select.
v List of books v T ables of contents of frequently used books v Frequently r efer enced articles, such as the AL TER T ABLE topic v The Search form For information about setting up a search, see the NetQuestion Appendix in Installation and Configuration Supplement book.
book, simply run it as you would run any other executable pr ogram. The result fr om 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.
Note: These form numbers only apply if you are or dering books that ar e printed in the English language in North America. Y ou can also order books individually by the form number listed in “DB2 Information – Hardcopy and Online” on page 146.
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.
T able 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 .
FOR BIT DA T A clause) is not converted. Otherwise all input and output character data is converted if the two machines have dif ferent 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.
T able 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 T aiwan.
Since defaults on dif ferent platforms ar e not the same, problems appear when DB2 data is sent from one platform to another . For example, W indows platforms use LOGICAL UNSHAPED data, while data on OS/390 is usually in SHAPED VISUAL format.
X'3F21' 856 11 X'3F22' 862 11 X'3F23' 916 11 X'3F24' 1255 11 Where CDRA String T ypes are defined: String - Text - Numerical - Orientation - Shaping - Symmetri.
Appendix F . Naming Rules Go to the section that describes the naming rules that you requir e information on: v “General Naming Rules” v “Database, Database Alias, and Catalog Node Name Rules”.
Database alias names are synonyms given to r emote databases. Database aliases must be unique within the System Database Directory in which all aliases ar e 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.
Using delimited identifiers, it is possible to create an object that violates these naming rules; however , subsequent use of the object could result in err ors.
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.
Appendix G. List Files, Bind Files, and Packages This appendix lists the bind files contained in dif ferent .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.
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.
T able 10. DRDA Bind Files and Packages (continued) Component Bind File Name Package Name MVS VM/VSE OS/400 Isolation level NC db2clpnc.bnd sqlc6 xyz no no yes REXX Isolation level CS db2arxcs.bnd sqla1 xyz yes yes yes Isolation level RR db2arxrr .bnd sqla2 xyz yes yes yes Isolation level UR db2arxur .
172 Quick Beginnings.
Appendix H. Notices Any refer ence to an IBM licensed pr ogram in this publication is not intended to state or imply that only IBM’s licensed program may be used. Any functionally equivalent product, pr ogram or service that does not infringe any of IBM’s intellectual property rights may be used instead of the IBM pr oduct, program, or service.
T rademarks The following terms are trademarks or r egister ed trademarks of the IBM Corporation in the United States and/or other countries: ACF/VT AM ADST AR AISPO AIX AIXwindows AnyNet APPN AS/400 .
Microsoft, W indows, W indows NT , V isual Basic, and the W indows logo are trademarks or register ed trademarks of Micr osoft Corporation in the United States, other countries, or both. PC Direct is a trademark of Zif f Communications Company in the United States, other countries, or both and is used by IBM Corporation under license.
176 Quick Beginnings.
Index A Access Profile creating 1 13 using 1 12 accessing data through DB2 Connect 8 through Net.Data or JDBC 14 accessing host servers configuring communications IBM Personal Communications for W i.
DB2 Connect User’s Guide 148 DB2 Data Links Manager for AIX Quick Beginnings 151 DB2 Data Links Manager for W indows NT Quick Beginnings 151 DB2 Enterprise - Extended Edition for UNIX Quick Beginnin.
partner node name 69 password naming rules 169 planning DB2 configuration 23 DB2 Connect configuration 23 privileges requir ed 138 product descriptions 3 overview 3 protocols APPC 67 PU 70 Q Quick B.
180 Quick Beginnings.
Contacting IBM This section lists ways you can get more information fr om IBM. If you have a technical problem, please take the time to r eview and carry out the actions suggested by the T roubleshooting Guide befor e contacting DB2 Customer Support.
Log on as anonymous. In the directory /ps/pr oducts/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 ar e available for users to discuss their experiences with DB2 products.
.
IBMR Part Number: CT6D9NA Printed in the United States of America on recycled paper containing 10% recovered post-consumer fiber . GC09-2830-00 CT6D9NA.
An important point after buying a device IBM GC09-2830-00 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought IBM GC09-2830-00 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data IBM GC09-2830-00 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, IBM GC09-2830-00 you will learn all the available features of the product, as well as information on its operation. The information that you get IBM GC09-2830-00 will certainly help you make a decision on the purchase.
If you already are a holder of IBM GC09-2830-00, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime IBM GC09-2830-00.
However, one of the most important roles played by the user manual is to help in solving problems with IBM GC09-2830-00. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device IBM GC09-2830-00 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
