Review this section 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.
So that TIBCO Object Service Broker can access sufficient TCP/IP sockets concurrently, set the MAXFILEPROC UNIX System Services parameter to an appropriate value. TIBCO recommend MAXFILEPROC=256 at minimum. This value may need to be set much higher than 256 for highly active systems with a large user base. The maximum number of sockets allowed is set initially by the MAXFILEPROC parameter in PARMLIB member BXPPRM
xx. To dynamically set MAXFILEPROC, type the following z/OS system command:
Set the z/OS system-wide parameter MAXPROCSYS to limit the number of processes that execute concurrently. An insufficient number might cause your application to suffer such failures as U1979/U07BB abends as you use more UNIX services.
As a guideline, every Execution Environment (EE) uses at least two UNIX processes, one for the main TCB and the other for the TCB, which controls the communications
RELAY. Also consider these examples:
•
|
If you set TASKPOSIXNUM=1 or default the parameter to 1, that is another UNIX process for POSIX-compliant code.
|
The relay file, RELAYCFG, in the CNTL data set, contains information about TIBCO Object Service Broker components that use TCP/IP. It associates TCP/IP host names and port numbers with the TIBCO Object Service Broker communications identifiers that are used by these components running on any supported platform. The file is a text file in XML format that must be modified whenever changes to the TCP/IP environment are needed. Each component could have a separate relay file, or a common file could be shared across a number of components.
If XCF communications relay is deployed, TCP/IP parameters must be merged with the XCF parameters, and the combined parameters are contained in RELAYCFG in the CNTL data set. For details on XCF parameters, see
Configuring XCF Communications.
The order of the relay parameters for each node name will be the order of selection for that node. If merged with XCF parameters, XCF will be considered before TCP/IP for nodes PRODZDOB and PRODZNEE; see
Relay File Samples.
$HLQNONV$.$SLQ$.RELAYCFG contains your live TCP/IP information. If you need to make changes to your TCP/IP configuration, use the CNTL member RELAYCFG to make and verify your changes, then copy the new information to $HLQNONV$.$SLQ$.RELAYCFG.
To override the data set name set by USERMODD, add a DDNAME S6BRELAY to your TIBCO Object Service Broker component or any other z/OS components requiring TCP/IP communications. If this override is invalid during the component initialization, then the TCP/IP support is disabled until you provide a valid parameter file. Once the relay file has been processed during component initialization, it is freed.
The relay file consists of a set of protocol specific parameters followed by a directory that maps communications identifiers to protocol specific parameters.
<tcpipparms tcbnum="3" maxtcbsockets="50" />
<tcpip host="zos1.mydomain.com" service="emprec" />
<tcpip host="solaris5.mydomain.com" port="26360" />
<tcpip host="zos1.mydomain.com" port="22636" />
<tcpip host="168.192.0.101" port="26362"/>
<tcpipparms tcbnum="3" maxtcbsockets="50" />
<xcfparms groupname='S6BOSB'/>
<tcpip host="zos1.mydomain.com" service="emprec" />
<tcpip host="solaris5.mydomain.com" port="26360" />
<tcpip host="zos1.mydomain.com" port="22636" />
<tcpip host="168.192.0.101" port="26362"/>
The tcpipparms element specify TCP/IP specific parameters. The parameter values are static for the life of your TIBCO Object Service Broker component.
|
The number of z/OS tasks to be started that will process socket specific events (default is 3 and minimum is 1).
|
|
|
|
The name of the TCP/IP address space that you want to connect to. If the name is not specified, the system derives a value from the TCP/IP system configuration file, as described in the IBM publication z/OS Communications Server: IP Configuration Reference.
|
The relay file directory maps communications identifiers to protocol specific parameters. Each node element defines a communications identifier. The following are attributes that you can used to define the TCP/IP parameters for a node.
If you are upgrading from ObjectStar 4.1 or earlier to TIBCO Object Service Broker 5.x, you can use the S6BRLYGN utility to generate a relay file automatically. The utility converts the configuration data in a HRNPCSCM load module and creates the relay parameter file. The IN DD name specifies the load module library where HRNPCSCM is located job and the new configuration file is copied to the data set referenced by the OUT DD name. Any error messages are displayed in the file allocated to the SYSPRINT DD name.
The relay parameters for a TIBCO Object Service Broker component can be refreshed by using a z/OS System modify command. The command allows an administrator to change the mapping of communication identifiers to TCP/IP hosts and ports. Changes to
tcpipparms are not be honored and you must restart the component for the changes to become effective.
Note that for CICS, the CS, sub-command prefix should not be used. The HREL transaction is intended to be used from a z/OS console. You may enter the transaction from a CICS terminal, but the response will be issued via a WTO and not back to your terminal.
STATUS may be replaced by any valid relay command, such as
DISABLE,
ENABLE,
PARMDSN= and
REFRESH.
The S6BRLYVA program allows the administrator of TIBCO Object Service Broker to verify that the syntax of a relay file is correct before starting a TIBCO Object Service Broker component that uses the file. The utility will parse the relay file allocated to the S6BRELAY DD name and will display any error messages in the SYSPRINT DD name.