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


Chapter 1 Using TIBCO Object Service Broker Utilities : hrnbrulb (Batch Unload (Offline))

hrnbrulb (Batch Unload (Offline))
Syntax
hrnbrulb -C controlfile [arguments] filename
Platforms
Windows, Solaris
Description
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:
The two unload utilities (hrnbrulb and hrnbrulh (Batch Unload (Online))) are similar, and differ only in the following ways:
The hrnbrulb utility is an offline unload, while the hrnbrulh utility is an online unload.
In the hrnbrulb utility, you must specify the segment in which your table resides. In the hrnbrulh (Batch Unload (Online)) utility, you must identify the Data Object Broker to be accessed.
While the hrnbrulb utility provides a committed table unload, the hrnbrulh (Batch Unload (Online)) utility does not necessarily do so, depending on concurrent online activity.
Arguments
 
-A auditreport
The file to which the audit report is written. If this argument is omitted, the report is written to the screen (Windows) or stdout (Solaris).
-C controlfile
-s segment#
The offline segment number. If this argument is omitted, the segment number defaults to 0 (that is, the base segment is used).
-S selectionfile
-O unloadfile
Files
controlfile
A file containing the control information describing the output file and the table to unload. Create this file using the BATCHUNLD_CARDS tool.
filename
The name of the file to which the table is unloaded.
Environment Variable
UNICODEDIR
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.
Constraints
Segment Offline
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.
Control File
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.
The complete file must be defined so that the hrnbrulb utility can determine the size of the maximum record.
Selection File
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.
Parameterized Table Instances
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.
Reloading the Data
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.
EBCDIC Format
The output file is created in EBCDIC (z/OS variable) format.
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:
where the first two bytes contain the length followed by two bytes containing zeros.
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:
followed by the first record (of 20 bytes).
Null-equivalent Values
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:
Packed Decimal fields use the alternative negative sign (X’B’), which means that the lowest possible value can still be used in tables. In a file where the default null-equivalent value is used, the following values must not be used:
The default values can be overridden to use a user-defined value, the highest possible value, or no null-equivalence permitted.
You cannot represent a floating point null in fixed format. When a floating point null is unloaded using the hrnbrulb utility or the hrnbrulh (Batch Unload (Online)) utility, it is unloaded as true zero. Therefore, when floating point nulls are reloaded using the hrnbrtbl (Batch Load) utility, they are loaded as a zero.
Transferring Unloaded Data Using FTP
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.
Examples
Windows
hrnbrulb -A audit.trail -C c:\cntl\control.file -s 1
         -O output.file
Solaris
hrnbrulb -A audit.trail -C /usr1/cntl/scontrol.file -s 1
         -O output.file
These command lines indicate:
Sample Audit Log
The following illustrates a sample audit log for the hrnbrulb utility:

 
*batchsrv OFFLINE BATCH UTILITY SERVER DATE 2007 MAR 06 TIME 11 27
Requested Utility: hrnbrulb
 
CONTROL - file: Y2000ULB.CTL
INPUT - TDS Table: Y2000_TDS Character Set: ENGL
OUTPUT - file: ULB.OUT: Data type: Huron; Record format: Variable
 
#fields - 2; #records - 100000; #parameters - 0; #secondaries - 0
Output sizes: Record - 18; Minimum Record - 3 Buffer - 65536
 
 
UNLESS SPECIFIED BELOW (COLS 64-79) PACKED DECIMAL AND BINARY NULLS WILL
BE CONVERTED AND OUTPUT TO THE FILE AS FOLLOWS:
BINARY: (default = LOWVALUE) Length 2 thru 8 x'80~~~~~~~~00'
PACKED: (default = LOWVALUE) Length 1 thru 8 x'9B' thru x'999999999999999B'
 
 
UNLOAD FIELD - KEY: type= I; syntax= B; length= 4; decimals= 0
 
UNLOAD FIELD - FLD: type= S; syntax= C; length= 10; decimals= 0
 
 
END OF TABLE
 
 
PAGESTORE SEGMENT NAME SEG01 SEGMENT # 1 TYPE TDS - OPENED
 
 
 
*hrnbrulb TDS TABLE UNLOAD Date 2007 MAR 06 Time 11:27
 
Table's primary path begins at page: 0100004F; no secondaries allocated.
 
S6BBU100E: TABLE TO BE UNLOADED DOES NOT CONTAIN ANY DATA
 
 
 
PAGESTORE SEGMENT NAME SEG01 SEGMENT # 1 TYPE TDS - CONNECTION TERMINATED

 
Related Utilities

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