Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

DB2 10.1 DBA for Linux, UNIX, and Windows certification exam 611 prep, Part 8: Connectivity and networking

Darliene Hopes (dlhopes@us.ibm.com), DB2 Solution Migration Consultant, IBM
Darliene Hopes
Darliene Hopes is a DB2 solution migration consultant at IBM. She has been working with DB2 for Linux, UNIX, and Windows since the start of her career. She is an IBM Certified DB2 database administrator who has been recently and consistently contributing to the DB2 community.

Summary:  This tutorial aims to explain the process of configuring communications and the processes of cataloging databases, remote servers (nodes), and Database Connection Services (DCS) databases. You will also get introduced to DB2® Discovery and learn how to manage connections to System z® and System i® host databases. You will also learn about Lightweight Directory Access Protocol (LDAP). This tutorial prepares you for Part 8 of the DB2® 10.1 DBA for Linux®, UNIX®, and Windows® certification exam 611.

View more content in this series

Date:  25 Oct 2012
Level:  Intermediate PDF:  A4 and Letter (389 KB | 20 pages)Get Adobe® Reader®

Comments:  

Configuring communications to System z and System I database servers

System z and System i communications

To access the data stored in a DB2 for z/OS or a DB2 for i5/OS database:

  1. Configure TCP/IP communications on the DB2 Connect server.
  2. Catalog the TCP/IP node.
  3. Catalog the System z or System i database as a DCS database.
  4. Catalog the System z or System i database.
  5. Bind utilities and applications to the System z or System i database server.

Most steps to establish a connection between a DB2 Connect and a System z or System i host database are the same as the steps used to configure a client to access a database stored on a remote server. The difference is the host database must be cataloged as a DCS database, and DB2 utilities and applications must be bound to the System z or System i host database.


Binding utilities and applications

To bind utilities and applications the following steps must be taken from the DB2 Connect server:

  1. Go to the directory on the DB2 Connect server where the DB2 utility and application bind files are located (Linux/UNIX - sqllib/bnd Windows - bnd sub directory of the sqllib directory where DB2 is installed)
  2. Establish a connection to the database stored on the System z or System i server by executing CONNECT TO [DatabaseAlias].

    DatabaseAlias: Alias assigned to the database on the System z or System i server when the database was cataloged.

    A note about db2schema.bnd bind file

    When databases are created are migrated to a Linux, UNIX, or Windows DB2 server, the db2schema.bnd file is automatically bound to the database as part of the creation/migration process. It only exists on these kinds of servers and is used to create a package providing system catalog function support. If for some reason this package is missing, it must be rebound to the database.

    The file can be found in the sqllib/bnd subdirectory on Linux/UNIX and the bnd subdirectory of the sqllib directory where DB2 was installed for Windows. This file can be bound to the database by executing BIND db2schema.bnd BLOCKING ALL GRANT PUBLIC.

  3. Bind the DB2 utilities and applications to the database on the System z or System i server by executing the following: BIND @db2ubind.lst MESSAGES ubind.msg GRANT PUBLIC; BIND @db2cli.lst MESSAGES clibind.msg GRANT PUBLIC;

    db2ubind: List of the bind files needed to create packages for DB2 database utilities
    db2cli.lst: List of the bind files needed to create packages for the DB2 Call-Level Interface (CLI) and the DB2 ODBC driver.

  4. Terminate connection to the database stored on the System z or System i server by executing a command like CONNECT RESET;.

4 of 9 | Previous | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Information Management
ArticleID=842457
TutorialTitle=DB2 10.1 DBA for Linux, UNIX, and Windows certification exam 611 prep, Part 8: Connectivity and networking
publish-date=10252012
author1-email=dlhopes@us.ibm.com
author1-email-cc=