![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
When you start the Gateway, the S6BDB2M module connects to both DB2 and TIBCO Object Service Broker. The number of Gateways specified in the SERVERS parameter are then attached by S6BDB2M. Each Gateway (the S6BDB2S module) connects to TIBCO Object Service Broker. When the Execution Environment requests access to DB2 data, a thread to DB2 is established. For more information, refer to Adding Gateway Threads.Modify JCL member DB2BATCH in the JCL data set to be a JCL procedure and move it to your site PROCLIB (for example, SYS1.PROCLIB). You can then start the Gateway from the z/OS operator console using the z/OS START command.
Region size must be large enough to hold all the Static SQL handlers to be used during the life of the Gateway. All Static SQL handlers remain in memory during the life of the Gateway for improved performance.TIBCO Object Service Broker Messages With Identifiers for information on messages produced by the Gateway.TIBCO Object Service Broker for z/OS Installing and Operating for more information on running the Gateway as a batch job.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |