![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
the hrnbrula utility is a TIBCO Object Service Broker recovery utility that restores one or more TDS tables from an archive file. You can:There are three phases to the unload table from archive process. During the process, the archive file is scanned twice. The utility accepts a number of arguments to control both the program flow and storage utilization. The three phases of the table unload process are:
At the end-of-file, the archive checks to ensure that a root page exists for each requested entry. Identifies which data pages contain the information for all the unloaded tables. Extracts the data occurrences from the required pages and produces a work file that is sorted into appropriate order based on parameter values within the table name.
The file to which the audit report is written. This entry is optional. If omitted, the report is written to the default file stdout. -C controlfile -d datapage% Data page %. This number indicates the approximate % of used pages that are D pages. The entry is optional and has a default of 85%. -g group% Group index page %. Approximate % of used segment pages that are G pages. This is an optional entry and has a default of 10%. -h groupindex% Group-index index page %. Approximate % of used segment pages that are H pages. This is an optional entry and has a default of 2%. -i dataindex% Data Index page %. Approximate % of used segment pages that are I pages. This is an optional entry and has a default of 3%. -M 3-char-prefix This entry indicates a separate file is required for each table or instance. You must supply either an ‑M 3 character prefix or a ‑U unloadfile argument. -n buffer# Number of sort buffers to be used. The entry is optional and has a default of 10 buffers. -p pages# Approximate number of used pages in segment. This optional entry has a default of 100000. In cases where this number is unknown, enter the total number of pages in the segment. The default number is usually sufficient. If not, it is better to overestimate. -S selectionfile Full path of selection control file. This entry is required only if selected parameter instances of a table are being recovered. -s segment# The offline segment number. This argument defaults to 0 (that is, the base segment is used). -U unloadfile The full path and name of the unload file. You must supply either a ‑U unloadfile or an ‑M 3 character prefix argument. -v parameter% Parameter value %. Approximate % of G pages participating in the recovery. This optional entry has a default of 1%. -W workdir The full path of the work directory. This entry is optional and defaults to the current directory.
When in doubt, allow % arguments to default, as the defaults are sufficient to handle most unload situations.A file containing the control information describing the output file and the table to unload. Create this file using the BATCHUNLD_CARDS tool.Environment VariableSet 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.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 information can be prepared using the BATCHUNLD_CARDS tool or with an ASCII editor like Notepad or vi. For more information, refer to TIBCO Object Service Broker Shareable Tools.The complete file must be defined so that the hrnbrula utility can determine the size of the maximum record.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. 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 one 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.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, which 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:
• It is possible that binary fields do not use the following values if the null-equivalent value is used:
• 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 hrnbrula utility, the hrnbrulb (Batch Unload (Offline)) 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.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.
• Unloaded tables are written to files TBL001 through TBLnnn in the directory c:\brula (Windows) or /usr1/brula (Solaris). TBL is the 3 character prefix designated by the ‑M argument.
• Unload uses the control file called control.file in the directory c:\cntl (Windows) or /usr1/cntl (Solaris).
• Unload uses the select file called select.file in the directory c:\brula (Windows) or /usr1/brula (Solaris).
• Archive used as input is located in the directory c:\archives (Windows) or /usr1/archives (Solaris).Sample Audit Log
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |