Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 Configuring a Communication Environment for Access of Distributed Data : Connecting Windows or Solaris to z/OS Using TCP/IP

Connecting Windows or Solaris to z/OS Using TCP/IP
This section describes a sample connection between TIBCO Object Service Broker node A on z/OS and node B on Windows using TCP/IP. The sample would be the same for a Solaris to z/OS connection. Configuration files and parameters can differ according to your site requirements. The following tasks are described:
1.
2.
3.
4.
5.
Refer to Managing Peer Servers for more information about configuring and operating peer-to-peer distributed data connections.
Recommendations
We recommend that you minimize the amount of data exchanged between Data Object Brokers in this configuration. For example, structure your applications so that they do not do a full table sweep on the remote node.
Assumptions
This procedure assumes the following:
 
Task A Setting up the z/OS System
Have your TIBCO Object Service Broker administrator update the TIBCO Relay Parameter file used by the z/OS TIBCO Object Service Broker to include the communications identifier for the Windows TIBCO Object Service Broker.
Example Relay Parameter File

 
<relay xmlns="http://www.tibco.com/OSB/relayparms.xsd">
   <tcpipparms tcbnum="2" maxtcbsockets="50" />
   <directory>
      <node name="HKXU0003">
         <tcpip host="brussels" port="44444" />
      </node>
      <node name="HOMEDOB">
         <tcpip host="192.160.1.101" port="2000" />
      </node>
   </directory>
</relay>

 
See Also
TIBCO Object Service Broker for z/OS Installing and Operating for detailed information about configuring TCP/IP communications for TIBCO Object Service Broker.
Task B Configuring TIBCO Object Service Broker for z/OS
Have your TIBCO Object Service Broker administrator configure TIBCO Object Service Broker and prepare JCL on the z/OS platform for distributed data. Configure the Data Object Broker on z/OS for peer connection to the Windows Data Object Broker using the Resource Management Facility. To invoke the Resource Manager, choose option 3 on the Administration menu (S6BTLADM utility).
In the Resource Manager, do the following:
1.
2.
3.
Sample Peer Server JCL
You must have JCL for the peer server (also referred to as the TIBCO Object Service Broker API server). The following shows a sample used for this configuration:

 
//KXU00SR2 JOB (1),’HKXU0003 PEER SRVR’,MSGCLASS=Y,TIME=1440
/*JOBPARM SYSAFF=*,TIME=1440
/*ROUTE PRINT HRNPRT1
//****************************************************************************
//* START A PEER SERVER (API) FOR DISTRIBUTED DATA FOR NODE A
//* VTAM APPLID - HKXU0003
///***************************************************************************
//REMSRVR EXEC PGM=S6BDR000,REGION=4096K,TIME=1440
//STEPLIB DD DSN=OSTAR.R32.LOAD,DISP=SHR
//HRNEXTR DD DSN=OSTAR.R32.LOAD,DISP=SHR
//HRNOUT DD SYSOUT=*
//HRNPRNT DD SYSOUT=*
//HRNIN DD *
PEERSERVERNUM=4,
MDL=OSB9999,
TDS=HKXU0003
/*

 
Include these Execution Environment parameters in your JCL:
 
[Optional] If not specified, defaults to OSB9999 where 9999 is the suffix that represents that a four-digit number, starting at 0001, is to be used by the identifiers as they are assigned.
The VTAM applid of the z/OS Data Object Broker. Corresponds to the COMMID in the z/OS TCP/IP static configuration data set.
See Also
TIBCO Object Service Broker for z/OS Installing and Operating for information about using the Resource Management facility.
TIBCO Object Service Broker Parameters for detailed information about the Execution Environment and Data Object Broker parameters.
Task C Configuring TIBCO Object Service Broker for Windows
Have your TIBCO Object Service Broker administrator configure TIBCO Object Service Broker on the Windows machine for distributed data. The following assumes you installed TIBCO Object Service Broker on your TCP/IP client machine.
1.
NODENAME= nodename
nodename is the Data Object Broker name. In this sample configuration, NODENAME=b.
PEERS=(remote_node, outbound#, inbound#, prefix, fslevel)
remote_node is the z/OS Data Object Broker name. fslevel should be 2. The following example corresponds to the sample configuration PEERS=(A,9,10,NTK,2).
nn is the number of users needed to accomodate peer users. Valid values are 1 to 4096. MAXUSERS must be large enough to allow incoming peers to log in. Each incoming peer uses 2 user slots, for example, if the total incoming peers is equal to 10, 20 incoming slots of MAXUSERS should be devoted to incoming peers. In this sample configuration, MAXUSERS=32.
2.

 
# z/OS Node
Node name=a,
alias=brussa
host=brussels.sdc.com,
port=44444
 
# Windows Node
Node name=b,
host=bewdley.sdc.com,
port=2000,
ipckey=0x2000

 
Refer to Attributes Defined for details on the huron.dir attributes.
3.
In your mon.prm file, specify the following values to the SERVERS Execution Environment parameter to define the peer servers, in the format SERVERS=’numberN sessionnameN’, where
Represents a session defined to the NAME parameter in the session.prm file (refer to step #4.), for example, PEERSERV1. It defaults to DEFAULT0 if left blank. If you specify a value on node A, the @PEERSERVERID shareable tool, which is a system-interpreted session table, must contain an entry with that name in the SERVERID field.
4.
If EENAME is specified, you must also specify a corresponding NAME parameter in the ee.prm file.
See Also
TIBCO Object Service Broker Shareable Tools for details about @PEERSERVERID.
TIBCO Object Service Broker Parameters for detailed information about the Execution Environment and Data Object Broker parameters.
Task D Establishing Outbound Connections
To enable requests from TIBCO Object Service Broker on Windows to the z/OS system, establish an outbound connection between the TIBCO Object Service Broker node on the Windows machine and the node running under z/OS. Follow these steps:
1.
Your job log should contain messages similar to the following:

 
10.03.03 JOB26919 S6BKC035L INITIATING PEER CONNECTION TO B :B
10.03.04 JOB26919 S6BKS050I HURON READY 1998MAR27 10:02
...
10.09.04 JOB26919 S6BKC016L U005F001 LOGGING ON (USER BATCH JOB/NET)
10.09.06 JOB26919 S6BKC018I T005F000 SERVER AVAILABLE,TYPE=API,SERVER ID=DEFAULT0
10.09.06 JOB26919 S6BKC018I T005F000 SERVER AVAILABLE,TYPE=API,SERVER ID=DEFAULT0
10.09.06 JOB26919 S6BKC018I T005F001 SERVER AVAILABLE, TYPE=API, SERVER ID=DEFAULT0
10.09.06 JOB26919 S6BKC016L U005F002 LOGGING ON (USER BATCH JOB/NET)
10.09.07 JOB26919 S6BKC016L U005F003 LOGGING ON (USER BATCH JOB/NET)
10.09.07 JOB26919 S6BKC018I T005F002 SERVER AVAILABLE, TYPE=API, SERVER ID=DEFAULT0
10.09.07 JOB26919 S6BKC018I T005F003 SERVER AVAILABLE, TYPE=API, SERVER ID=DEFAULT0
10.09.09 JOB26919 S6BKC016L @OP00600 LOGGING ON (OPERATOR/NET)

 
2.
View the Data Object Broker log on both sides to ensure the connection is successful. On Windows, you should see messages in the Data Object Broker log similar to the following:

 
2012/06/27 11:05:54 S6BUS014I Starting hrncomm(0)
2012/06/27 11:05:54 S6BUS002I hrncomm(0) startup completed
2012/06/27 11:05:54 S6BUS014I Starting hrncomm(1)
2012/06/27 11:05:55 S6BUS002I hrncomm(1) startup completed
2012/06/27 11:05:55 S6BUS014I Starting hrncomm(2)
2012/06/27 11:05:57 S6BUS002I hrncomm(2) startup completed
2012/06/27 11:05:57 S6BUS014I Starting hrncomm(3)
2012/06/27 11:05:57 S6BUA020I Peer user 'BBB00002' logged on from 'D187945@'
2012/06/27 11:05:58 S6BUS002I hrncomm(3) startup completed
2012/06/27 11:05:58 S6BUS014I Starting hrncomm(4)
2012/06/27 11:05:59 S6BUA020I Peer user 'BBB00003' logged on from 'D187945@'
2012/06/27 11:06:00 S6BUS002I hrncomm(4) startup completed
2012/06/27 11:06:00 S6BUS014I Starting hrncomm(5)
2012/06/27 11:06:00 S6BUC013I Connection(0) to 'A' established
2012/06/27 11:06:00 S6BUA020I Peer user 'BBB00004' logged on from 'D187945@'
2012/06/27 11:06:01 S6BUC013I Connection(1) to 'A' established
2012/06/27 11:06:01 S6BUS002I hrncomm(5) startup completed
2012/06/27 11:06:01 S6BUS014I Starting hrncomm(6)
2012/06/27 11:06:02 S6BUS002I hrncomm(6) startup completed
2012/06/27 11:06:02 S6BUS014I Starting hrncomm(7)
2012/06/27 11:06:02 S6BUA020I Peer user 'BBB00005' logged on from 'D187945@'
2012/06/27 11:06:02 S6BUC013I Connection(2) to 'A' established
2012/06/27 11:06:03 S6BUC013I Connection(3) to 'A' established
2012/06/27 11:06:04 S6BUS002I hrncomm(7) startup completed
2012/06/27 11:06:04 S6BUS014I Starting hrncomm(8)
2012/06/27 11:06:05 S6BUS002I hrncomm(8) startup completed
2012/06/27 11:06:05 S6BUA020I Peer user 'BBB00006' logged on from 'D187945@'
2012/06/27 11:06:05 S6BUC013I Connection(4) to 'A' established
2012/06/27 11:06:07 S6BUA020I Peer user 'BBB00007' logged on from 'D187945@'
2012/06/27 11:06:07 S6BUC013I Connection(5) to 'A' established
2012/06/27 11:06:08 S6BUC013I Connection(6) to 'A' established
2012/06/27 11:06:09 S6BUA020I Peer user 'BBB00008' logged on from 'D187945@’
2012/06/27 11:06:09 S6BUA020I Peer user 'BBB00009' logged on from 'D187945@'
2012/06/27 11:06:10 S6BUC013I Connection(7) to 'A' established
2012/06/27 11:06:10 S6BUC013I Connection(8) to 'A' established

 
On z/OS, you should see messages in your job log similar to the following:

 
11.08.53 JOB26919  S6BKC035L INITIATING PEER CONNECTION TO B :B
11.08.53 JOB26919  S6BKC016L NTK00001 LOGGING ON (PEER HURON/TCP)
11.08.55 JOB26919  S6BKC016L NTK00002 LOGGING ON (PEER HURON/TCP)
11.08.56 JOB26919  S6BKC016L NTK00003 LOGGING ON (PEER HURON/TCP)
11.08.56 JOB26919  S6BKC016L NTK00004 LOGGING ON (PEER HURON/TCP)
11.08.59 JOB26919  S6BKC016L NTK00005 LOGGING ON (PEER HURON/TCP)
11.09.00 JOB26919  S6BKC016L NTK00006 LOGGING ON (PEER HURON/TCP)
11.09.01 JOB26919  S6BKC016L NTK00007 LOGGING ON (PEER HURON/TCP)
11.09.03 JOB26919  S6BKC016L NTK00008 LOGGING ON (PEER HURON/TCP)
11.09.04 JOB26919  S6BKC016L NTK00009 LOGGING ON (PEER HURON/TCP)
15.31.15 JOB26919  S6BKC016L @OP01020 LOGGING ON (OPERATOR/NET)

 
At this point, connection is successful.
Task E Establishing Inbound Connections
To enable requests from TIBCO Object Service Broker on z/OS to the Windows Data Object Broker, establish an inbound connection between the TIBCO Object Service Broker node on the Windows machine and the node running under z/OS.
Follow these steps:
1.
On Windows, you should see messages in the Data Object Broker log similar to the following:

 
2012/06/27 11:06:13 S6BUA020I Peer user 'BBB00010' logged on from 'D187945@'
2012/06/27 11:06:15 S6BUA020I Peer user 'BBB00011' logged on from 'D187945@'
2012/06/27 15:27:35 S6BUA021I User '@HRRJW04' logged on from 'BEWDLEY'
2012/06/27 15:27:38 S6BUA021I User '@HRRJW07' logged on from 'BEWDLEY'
2012/06/27 15:27:39 S6BUA021I User '@HRRJW06' logged on from 'BEWDLEY'
2012/06/27 15:27:40 S6BUA021I User '@HRRJW02' logged on from 'BEWDLEY'
2012/06/27 15:27:40 S6BUA021I User '@HRRJW05' logged on from 'BEWDLEY'
2012/06/27 15:27:40 S6BUA021I User '@HRRJW08' logged on from 'BEWDLEY'
2012/06/27 15:27:40 S6BUA021I User '@HRRJW03' logged on from 'BEWDLEY'
2012/06/27 15:27:40 S6BUA021I User '@HRRJW01' logged on from 'BEWDLEY'
2012/06/27 15:27:40 S6BUA021I User '@HRRJW09' logged on from 'BEWDLEY'
2012/06/27 15:27:55 S6BUA023I PRS server DEFAULT0(THRRJW01) logged on from '@HRRJW01'
2012/06/27 15:27:56 S6BUA023I PRS server DEFAULT0(THRRJW05) logged on from '@HRRJW05'
2012/06/27 15:27:56 S6BUA023I PRS server DEFAULT0(THRRJW09) logged on from '@HRRJW09'
2012/06/27 15:27:56 S6BUA023I PRS server DEFAULT0(THRRJW03) logged on from '@HRRJW03'
2012/06/27 15:27:56 S6BUA023I PRS server DEFAULT0(THRRJW07) logged on from '@HRRJW07'
2012/06/27 15:27:56 S6BUA023I PRS server DEFAULT0(THRRJW06) logged on from '@HRRJW06'
2012/06/27 15:27:56 S6BUA023I PRS server DEFAULT0(THRRJW04) logged on from '@HRRJW04'
2012/06/27 15:27:56 S6BUA023I PRS server DEFAULT0(THRRJW02) logged on from '@HRRJW02'
2012/06/27 15:27:56 S6BUA023I PRS server DEFAULT0(THRRJW08) logged on from '@HRRJW08'

 
2.
View the Data Object Broker log on both sides to ensure the connection is successful. On Windows, you should see messages similar to the ones in step #1. On z/OS, you should see messages similar to the following:

 
11.08.53 JOB26919  S6BKC035L INITIATING PEER CONNECTION TO B :B
11.08.53 JOB26919  S6BKC016L NTK00001 LOGGING ON (PEER HURON/TCP)
11.08.55 JOB26919  S6BKC016L NTK00002 LOGGING ON (PEER HURON/TCP)
11.08.56 JOB26919  S6BKC016L NTK00003 LOGGING ON (PEER HURON/TCP)
11.08.56 JOB26919  S6BKC016L NTK00004 LOGGING ON (PEER HURON/TCP)
11.08.59 JOB26919  S6BKC016L NTK00005 LOGGING ON (PEER HURON/TCP)
11.09.00 JOB26919  S6BKC016L NTK00006 LOGGING ON (PEER HURON/TCP)
11.09.01 JOB26919  S6BKC016L NTK00007 LOGGING ON (PEER HURON/TCP)
11.09.03 JOB26919  S6BKC016L NTK00008 LOGGING ON (PEER HURON/TCP)
11.09.04 JOB26919  S6BKC016L NTK00009 LOGGING ON (PEER HURON/TCP)
15.31.15 JOB26919  S6BKC016L @OP01020 LOGGING ON (OPERATOR/NET)

 
Ending the Windows Connection
1.
hrncr stopserver=ALLPRS
2.
For more information on hrncr commands, refer to TIBCO Object Service Broker Operator Commands.
Ending the z/OS Connection
1.
2.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved