27.12.2012 Views

International Technical Support Organization Database Systems ...

International Technical Support Organization Database Systems ...

International Technical Support Organization Database Systems ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

5.7 Configuring OS/2 for DataHub <strong>Support</strong>/2<br />

5.7.1 OS/2 Host Components<br />

This section covers all the OS/2 definitions that allow the DataHub/2 workstation<br />

to manage OS/2 <strong>Database</strong> Manager databases. It shows how to customize the<br />

different components used for DataHub tools conversation connectivity. Because<br />

the OS/2-managed host must be a participant in the DRDA and the RDS network,<br />

you should have already implemented this OS/2 host in that network. (See 3.7,<br />

“OS/2 Definitions” on page 69.)<br />

This section does not cover how to install the DataHub <strong>Support</strong>/2 component.<br />

You should refer to the DataHub <strong>Support</strong>/2 Installation and Operations Guide for<br />

more information.<br />

The same prerequisite components are required on the DataHub <strong>Support</strong>/2 host<br />

as on the DataHub/2 workstation. The only exception is that DataHub/2 requires<br />

the server version of OS/2 <strong>Database</strong> Manager because the DataHub/2<br />

workstation will need to access that machine as a client using the RDS protocol.<br />

The DDCS/2 software is not required if this OS/2 host does not connect to a<br />

DRDA server to transfer data from or to it (for example, the DataHub copy data<br />

operation).<br />

What is different from a DataHub/2 workstation are the definitions that will be<br />

required. The DataHub/2 workstation needs to know all the hosts that are<br />

managed by the DataHub/2 product. The OS/2-managed host needs to know<br />

only the host(s) to which data will be transferred in a copy operation.<br />

If you use one host as a data repository from where you copy data, all the<br />

managed hosts have to know that repository host and need to connect to it. If<br />

you use the OS/2 <strong>Database</strong> Manager system to capture data that eventually will<br />

be transfered to a central site, the OS/2 <strong>Database</strong> Manager system needs to<br />

know only one system.<br />

OS/2 Host Component Relationship<br />

Another difference between the DataHub/2 workstation and the DataHub<br />

<strong>Support</strong>/2 hosts is the relationship between the different components.<br />

Figure 146 on page 194 shows the key connectivity parameters relationship on<br />

the OS/2-managed host. It shows only the tools conversation flow on this<br />

workstation. To understand the RDS connectivity, you should refer to Figure 46<br />

on page 71 and follow the Inbound request: CONNECT.<br />

The tools conversation request that has been sent by the DataHub/2 workstation<br />

contains the following information:<br />

• Logical unit name<br />

• Network ID<br />

• Mode name to use<br />

• Transaction program name that will process the request locally<br />

• Data that will contain the RDB name.<br />

The program that is associated with the transaction program name will execute<br />

the request and connect to the OS/2 <strong>Database</strong> Manager database using the RDB<br />

name mapping information provided in the DataHub <strong>Support</strong>/2 map file.<br />

Chapter 5. DataHub Tools Conversation Connectivity 193

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!