Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Configuring the Accesses to Adabas Data : Startup Process

Startup Process
The TIBCO Object Service Broker Execution Environment receives several parameters at startup. The parameters are described in Startup Parameters. The SERVERS parameter instructs this Execution Environment to attach a specified number of instances of the server used to access Adabas, thus accommodating multiple servers in a single address space.
Each server connects to Adabas with a unique Adabas session identifier. The Adabas session is disconnected from Adabas only when the thread is disconnected or the address space is terminated.
At Transaction Start
At the beginning of a TIBCO Object Service Broker transaction, the first request for data from Adabas results in an Adabas OP (Open) command being sent to Adabas. A TIBCO Object Service Broker transaction running in browse mode causes the file to be opened with the ACCess argument. Transactions running in update mode are opened with the UPDate argument.
At Transaction End
When the transaction ends, the Adabas session terminates. If the transaction completes successfully, only an Adabas CL (Close) command is issued. This close command implies an Adabas ET (End transaction), which is equivalent to a TIBCO Object Service Broker commit point. However, if the transaction fails, an Adabas BT (Backout Transaction) is sent before the CL (Close) command.
See Also
TIBCO Object Service Broker External Environments for z/OS about Execution Environments.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved