![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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:Refer to Managing Peer Servers for more information about configuring and operating peer-to-peer distributed data connections.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.Task A Setting up the z/OS SystemHave 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.
<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>
TIBCO Object Service Broker for z/OS Installing and Operating for detailed information about configuring TCP/IP communications for TIBCO Object Service Broker.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).
1. Use resource type HIN for incoming connections, and resource type HRN for outgoing connections.
3. For each of these components, define a schedule that sets day and time of day limits, if desired for these connections.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:
[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. 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.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.
NODENAME= nodename nodename is the Data Object Broker name. In this sample configuration, NODENAME=b. 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.
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 the number of inbound connections, for example, 10. 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. In the session.prm file, specify the following Execution Environment parameter values:
The name of the session parameter assignment to be used, for example, PEERSERV1. The path for the server log, for example, D:\Ostar\log. [Optional] The name of the Execution Environment to be used.If EENAME is specified, you must also specify a corresponding NAME parameter in the ee.prm file.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.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:
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:
11.08.53 JOB26919 S6BKC035L INITIATING PEER CONNECTION TO B :B11.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)
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.
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 :B11.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)
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |