TIBCO Object Service Broker journals are data sets that provide a record of all modified page images. Journals are essential to the TIBCO Object Service Broker continuous backup and recovery procedures.
Journal backups can be merged together and used to refresh your current system backup. For guidance in developing a continuous backup procedure that meets your unique backup and recovery requirements, read this chapter and then refer to
Chapter 6, Backing Up Your System.
When one journal file reaches capacity, the Data Object Broker automatically switches to the other. The Data Object Broker still continues processing transactions during this switch. The journal that is almost full is then
spun (emptied of its contents) and made available for use again.
Journal spinning is normally performed under the control of the batch files (for Windows) or scripts (Solaris): spin01, spin02, and spin03. These files are shipped with a default behavior, which can be tailored at any time by the TIBCO Object Service Broker system administrator.
In Windows, the spin01.bat and spin02.bat files reset the journal for reuse. In Solaris, the spin01 and spin02 scripts reset the journal for reuse. To turn on journal spinning for continuous backup, do one of the following:
The journal spin process uses the hrnspjex (Journal Extraction) utility to extract relevant records from JOURNAL1 or JOURNAL2 and produces an audit trail. At the end of the journal off‑load, the hrnspset (Reset Journal) utility resets the journal and changes its state to
EMPTY so that it can be reused.
TIBCO Object Service Broker for Open Systems Utilities for information about the hrnspjex and hrnspset utilities.