If TIBCO Object Service Broker is shut down or the Pagestore segment containing the table is offline, use the hrnbrulb utility to unload data. This utility provides you with:
Set this to indicate the directory that contains the Unicode configuration files, for example, %OS_ROOT%\database\UNICODEDIR in Windows or ${OS_ROOT}/database/UNICODEDIR in Solaris. For more information, refer to
TIBCO Object Service Broker for Open Systems Installing and Operating.
The Pagestore segment from which you intend to unload a table must be offline. This means that if the segment containing the table’s data is segment 0, the Data Object Broker must be shut down.
You must have a correctly formatted control file, describing the format of your table (which is also the format of your output file), the table name to be unloaded, and other relevant control information. This file is prepared using the
BATCHUNLD_CARDS shareable tool and supplied to the utility using the ‑C argument. For more information, refer to
TIBCO Object Service Broker Shareable Tools.
If the table to be unloaded is parameterized and you want to unload only selected instances, you must have a correctly formatted selection file (ASCII text) constructed using the online
BATCHUNLD_CARDS tool and supplied to the utility using the ‑S argument. For more information, refer to
TIBCO Object Service Broker Shareable Tools. This selection file indicates which parameter instances you want to include or exclude.
Tables must not be empty. Parameterized table instances selected for inclusion in the unloaded file by using the equals (=) relational operator must exist in the table.
If you use either of the Batch Unload utilities to unload data, reload the data by using the Batch Load utility. You cannot reload the data using the interactive
LOAD tool.
Fixed (F) or Fixed Block (FB) format means that all records are the same length. Under OSB for Windows or OSB for Solaris, there is no difference between F and FB formats.
Variable Block (VB) means that each block is prefixed by a four-byte Block Descriptor Word (BDW) containing the length of the data in the block, including the four-byte BDW itself. For example, the BDW for a 256-byte block of data would appear as follows:
Within each block, each record has a Record Descriptor Word (RDW) with exactly the same format as the BDW. If a record contained 20 bytes of data, the RDW would appear as follows:
where the first two bytes contain the length, followed by two bytes containing zeros. If this record is the first in the block, the beginning of the block would appear as follows:
Numeric syntax fields (binary and packed decimal) have a null-equivalent value that is defined as the lowest possible value that the field can hold. Null values in the input file are preserved using the following default behavior:
If you are using FTP to transfer unloaded data between z/OS and Windows or Solaris, you must reformat the unloaded data using the S6BBRFRU z/OS utility before it can be used by TIBCO Object Service Broker. Refer to
TIBCO Object Service Broker for z/OS Utilities for more information on the S6BBRFRU utility.