Customizing Communications

Data Object Broker – VTAM Application Definition and Nodename

VTAM is not supported between TIBCO Object Service Broker components—client processes, Execution Environments, Data Object Brokers, and external database gateways on a z/OS system.

VTAM is supported for VTAM terminals and the Execution Environments. Refer to member OSRUN in the distribution source library <HLQ>.FILEJCL for non-customized reference to the variables listed below. Modify OSRUN in the JCL data set to your new values and submit the job to check it out. For detailed instructions, see Appendix B, Configurations for Communications, Configuring VTAM Communications.


Variable	Description	Default	Your Value
$TDS$	Data Object Broker Communications Identifier	OSBDOB
$NODNAM$	Data Object Broker name in a distributed data environment	DOB60ZOS

Data Object Broker – TCP/IP Identifiers

If you are using TCP/IP to communicate between TIBCO Object Service Broker components-client processes, Execution Environments, Data Object Brokers, and external database gateways on a z/OS system and TIBCO Object Service Broker components on z/OS or non-z/OS platforms, TCP/IP identifiers will require customization. Refer to the RELAYCFG member in the distribution source library <HLQ>.FILECTL for non-customized references to the variables listed below. Modify member RELAYCFG in the CNTL data set to your new values and submit member OSRUN to check it out. For detailed instructions, see Appendix B, Configurations for Communications, Configuring TCP/IP.


Variable	Description	Default	Your Value
$TDS$	Data Object Broker communication identifier	OSBDOB
$HOST$	Data Object Broker host name	ZOS.OSB.COM
$DOBPORT$	Data Object Broker port number	9000
$EENAME$	Execution Environment communication identifier	OSBNEE
$EEPORT$	Execution Environment port number	9001