01.01.2013 Views

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Note: Although using this technique ensures our LU names will be unique<br />

within the subnet, it is possible that two machines from different subnets will<br />

connect to the same <strong>CICS</strong> region, causing a potential name clash. In this<br />

case, we suggest that you ensure that you only use three (or less) substitution<br />

characters and that the fifth characters in the LU name template is different for<br />

each subnet.<br />

To help you in determining what a given TCP62 LU name will be for different<br />

inputs, we developed a sample utility, tcp62locallu.exe, that takes a given IP<br />

address, subnet mask, and LU name template, and generates the LU name that<br />

TCP62 will use. This use of this utility is illustrated in Figure 3-3 and it is provided<br />

with the additional material for this book.<br />

Example 3-3 tcp62locallu utility<br />

C:> tcp62locallu.exe CCLIE*** FFFFFE00 9.1.38.39<br />

Local LU template: CCLIE***<br />

Address mask : FFFFFE00<br />

IP address : 9.1.38.39<br />

Local LU is CCLIEE17<br />

Configuring TCP/IP host names<br />

Since TCP62 flows SNA LU 6.2 packets over TCP/IP, you need to define a<br />

mapping of the SNA partner LU name to an IP address. Our partner LU is our<br />

<strong>CICS</strong> region, with a fully qualified LU name of US<strong>IBM</strong>SC.SCSCPJA1. This needs<br />

to be mapped to the IP address of our z/OS system wtsc66, which is 9.12.6.6.<br />

<strong>The</strong> function in TCP62 achieves this by generating a host name from the<br />

concatenation of the following elements separated by periods:<br />

LU name (5) + network name of the LU (4) + domain name suffix (2)<br />

We defined a mapping of this host name to the IP address of our z/OS system<br />

using the TCP/IP hosts file (C:\WINNT\system32\drivers\etc\hosts) on our<br />

Windows 2000 workstation. <strong>The</strong> following is the line we added to our hosts file.<br />

9.12.6.6 SCSCPJA1.US<strong>IBM</strong>SC.ITSO.<strong>IBM</strong>.COM<br />

If you wish to use the same CTG.INI configuration file across multiple client<br />

workstations, you will also need to provide a means of resolving the TCP62 host<br />

name to the correct z/OS IP address on all workstations. Instead of just using the<br />

TCP/IP hosts file, it is possible to add an entry to the Domain Name System<br />

(DNS) server used by the workstations.<br />

Chapter 3. TCP62 connections to <strong>CICS</strong> 51

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

Saved successfully!

Ooh no, something went wrong!