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


Chapter 12 Starting and Shutting Down TIBCO Object Service Broker : Overview

Overview
Starting the TIBCO Object Service Broker System
The exact procedures you use to start TIBCO Object Service Broker depend upon the mix of TIBCO Object Service Broker components that you use and your z/OS system environment. In general, the steps are:
1.
2.
3.
Shutting Down the TIBCO Object Service Broker System
Shutting down the TIBCO Object Service Broker system involves the following steps:
1.
2.
3.
4.
5.
Critical Messages
When TIBCO Object Service Broker encounters a serious problem, it issues to the operator a critical message, for example:
S6BTW005E  Highest level index updated for table "DJC_TAB1"
which indicates that the DJC_TAB1 table is almost full, and logs this message in the @CRITICALMSGS table. Critical messages are those that require action by the system administrator. Using the @CRITICALMSGS table, TIBCO Object Service Broker ensures that the messages are still available after they are gone from the operator’s console.
It is the system administrator’s responsibility to delete processed messages from the @CRITICALMSGS table. When the table is full, critical messages are issued to the operator console only.
Here is an example of the @CRITICALMSGS table showing the date and time when the messages it contains were issued:

 
BROWSING TABLE : @CRITICALMSGS
COMMAND ==>
SCROLL: P
KEY DATE TIME MESSAGE
_ ----------- -------- ------ -
_ 1 20070527 152108 .
_ 2 20070527 152944 .
_ 3 20070527 154547 .

 
By browsing the second row, we see the issued message:

 
TABLE TYPE : TDS
COMMAND ==>
------------------------------------------------------------------------------
KEY : 2
DATE : 20070527
TIME : 152944
MESSAGE : S6BTW005E Highest level index updated for table "DJC_TAB1"
:
:

 

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