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


Chapter 12 Starting and Shutting Down TIBCO Object Service Broker : Starting a Data Object Broker or External Database Server

Starting a Data Object Broker or External Database Server
Starting a Data Object Broker
Starting a Data Object Broker activates TIBCO Object Service Broker. Depending on your installation requirements, the Data Object Broker can operate as one of the following:
Starting a Data Object Broker as a Started Task
To start a Data Object Broker as a started task, issue a Start command from the z/OS console, specifying the procedure name that was added to your system procedure library.
Sample JCL is the OSRUNSTC member in the JCL data set. This JCL starts TIBCO Object Service Broker as a started task. Its name and contents could be customized for your site.
Starting a Data Object Broker as a Batch Job
To start TIBCO Object Service Broker as a batch job, submit the JCL named OSRUN. OSRUN JCL is in the JCL data set. Messages similar to those shown for the started task startup appear in the batch job log. This JCL could have been relocated or renamed in your operating environment.
Restarting a Data Object Broker
TIBCO Object Service Broker automatically checks the journal cache to determine whether to perform a cold start or a warm start:
If TIBCO Object Service Broker detects that the system was shut down normally, it performs a cold start. This starts the Data Object Broker with the segment availability as defined in the DBDLIB (specified by INIT=Y/N on the DB statement).
If TIBCO Object Service Broker detects anything except a graceful shutdown, it automatically performs a warm start with recovery. This starts the Data Object Broker with the same segment availability that existed at the time of the abnormal termination.
If TIBCO Object Service Broker cannot safely restart itself, it issues the appropriate messages to help you diagnose the problem.
After a system failure, in order to synchronize all updates to the Pagestore that were in-flight at the time of the failure, you should restart TIBCO Object Service Broker and terminate it again using a normal shutdown. Failure to do this can result in a corrupted Pagestore if any offline processing is attempted on the Pagestore.
The first time you start a Data Object Broker, the Data Object Broker assumes a previous failure; it issues message S6BKR006A and asks that you reply G or C to S6BKR098A. If you reply C, it cancels the start-up; if you reply G, it performs a cold start (no recovery processing).
Starting External Database Servers
External database servers are available to access database management systems outside TIBCO Object Service Broker. To learn which servers are available, refer to the Late Breaking News on our Support web site.
Each server type, depending on the external database to be accessed, has a unique startup procedure. Each server type must also be defined to the Data Object Broker using the Resource Manager facility in the Administration menu. Refer to 3. Resource Management for additional information about this facility.
See Also
The Service Gateway manuals for information on starting the server for a specific DBMS.
The online TIBCO Object Service Broker Messages With Identifiers documentation for information about abnormal termination messages and the appropriate responses.

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