![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
TIBCO Object Service Broker supports any hardware that runs z/Architecture as specified in z/Architecture Principles of Operation (SA22-7832-06). The architectural extensions listed in Chapter 1.2 are not required.TIBCO Object Service Broker requires approximately 1500 cylinders of Direct-Access Storage Device (DASD) space.TIBCO Object Service Broker supports the use of 3278 and 3279 terminals running in model 2, 3, 4, or 5 mode, and terminals that are compatible with these devices and model types.Before installing TIBCO Object Service Broker in a z/OS environment, ensure that the following software components are installed and properly configured.TIBCO Object Service Broker requires that IBM's Language Environment product be available during execution. Within a CICS environment, you must install the CICS RDO definitions in CEE.SCEESAMP(CEECCSD) or have the CICS autoinstall be operational for programs.
For routines for which LANGUAGE=LE or LEPERSIST (refer to TIBCO Object Service Broker for z/OS External Environments), it is the responsibility of the developer to provide the appropriate CEEUOPT in the LE-compliant external routine. This is because the CEEPIPI enclave is initialized according to the specification of the external routine being called. The same CEEUOPT options must be used for all external routines in each class (LE or LEPERSIST) for the same Execution Environment because the same CEEPIPI enclave cannot support different runtime options.TIBCO Object Service Broker can also access data stored in the following external database server products:
•
•
•
•
•
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |