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


Chapter 1 Using TIBCO Object Service Broker Utilities : S6BBRULB, S6BBRULH (Batch Unload)

S6BBRULB, S6BBRULH (Batch Unload)
S6BBRULB and S6BBRULH (Batch Unload) provide the following functions:
Refer to Appendix C, Null Handling for information on the method used by the unloads to preserve null values in the unload file. The unloads use specific field values to represent nulls in the unload file.
Selecting the Correct Utility
Select the appropriate utility based on whether the data you want to unload is online or offline:
TIBCO Object Service Broker condition…
Condition of Pagestore segment containing data to be unloaded
S6BBRULH extracts all data in a table or selected table instances of a parameterized table. When unloading data from an online database, consider the effect on the resulting unloaded copy of any updating activity going on in the table being unloaded.
Invocation
To use the batch unload utilities complete the following tasks:
1.
2.
3.
These tasks are described in the following sections.
 
Task A Define Input and Output with Control Cards
To describe the input and output to the Batch Unload utilities, you need to:
1.
2.
Refer to the documentation for BATCHUNLD_CARDS in TIBCO Object Service Broker Shareable Tools.
Tables must not be empty. Parameterized table instances selected for inclusion in the unloaded file using the equals (=) relational operator must exist in the table at unload time.
Input Files
You provide input specifications to either of the batch unload utilities in two files:
 
The control card file specifies the definition of the table to be unloaded. The CNTRL file should be defined as fixed block, record length 80.
The selection file is optional. It contains criteria for selecting table instances from a parameterized table set. If a SELECT file is required, it should be defined as fixed block, record length 530.
Output Files
The following output files are used:
 
The unload file contains all the data extracted during the execution of the batch unload process. The layout of the text area within the file is reported in the AUDIT trail.
This SYSPRINT file contains the table definition, selection criteria, table instances unloaded, and summary information. Refer to the sample audit report in Review the Audit Trail Report.
In addition to these files, the S6BBRULB utility (used when TIBCO Object Service Broker is down or the segment is offline) uses the following data set:
 
The Pagestore definition. DBDLIB is not referenced when you use S6BBRULH to unload from an active TIBCO Object Service Broker system.
Task B Define and Submit Execution JCL
Define and submit JCL to run on offline or online segments, as shown in the following sections.
Execution When TIBCO Object Service Broker is Down or Segment is Offline
The S6BBRULB member of the JCL data set distributed with TIBCO Object Service Broker contains sample JCL required to run a batch unload with TIBCO Object Service Broker shutdown or with the specified Pagestore segment offline.
This sample is provided as a reference only; modify the JCL for your needs.
Execution When TIBCO Object Service Broker is Active
The S6BBRULH member of the JCL data set distributed with TIBCO Object Service Broker contains sample JCL required to run an unload with the TIBCO Object Service Broker system up and running.
This sample is provided as a reference only; modify the JCL for your needs.
Online/Offline Differences
There are several differences between the offline and online running modes:
As parameters for S6BBRULH, you specify the Data Object Broker communications identifier and the pattern used for selecting the Execution Environment communications identifier. If required, you must also provide the user ID and password to obtain security clearance.
For compatibility with null handling techniques used in earlier TIBCO Object Service Broker releases, you can use the Execution Environment parameter setting OLDNULL=Y. For more information on this feature, refer to Appendix C, Null Handling.
Task C Review the Audit Trail Report
The audit trail report provides information about the execution of the batch unload process. The audit trail for the S6BBRULB and the S6BBRULH processes are identical except for the module name, which appears at the left margin of the page header line.
The following contains a compressed version of a sample AUDIT TRAIL report:

 
S6BBRULB BATCH - UNLOAD TABLE DATE 2009 APR 20 TIME 10:48 V520E050
 
 
UNLESS SPECIFIED BELOW (COLS 64-79) PACKED DECIMAL AND BINARY NULLS
WILL BE CONVERTED AND OUTPUT TO THE FILE AS FOLLOWS:
BINARY AS "LOWVALUE" ----> LENGTH 1-8 X'80' - X'8000000000000000'
PACKED AS "LOWVALUE" ----> LENGTH 1-8 X'9B' - X'999999999999999B'
 
 
UNLOADING TABLE - TC4048_DATA
 
NAME TYPE SYNTAX LENGTH DECIMAL OFFSET
 
FIELDS DEFINITIONS
KEY I V 20 0 0
V1 V 1 0 20
V127 V 127 0 21
V254 V 254 0 148
IV1 I V 1 0 402
IV127 I V 127 0 403
IV254 I V 254 0 530
SV1 S V 1 0 784
SV127 S V 127 0 785
SV254 S V 254 0 912
CV1 C V 1 0 1166
CV15 C V 15 0 1167
QV1 Q V 1 0 1182
QV15 Q V 15 0 1183
***** SEGMENT FORMAT IS TDS *****
S6BBU001I 5 DATA OCCURRENCES UNLOADED
START TIME 10:48:49 END TIME 10:48:49

 
Constraints
The following constraints apply:
If you use either of the batch unload utilities to unload data, you can reload the data by using the batch load utility or by treating the data as a TIBCO Object Service Broker import file. However, you cannot treat the data as an import file when binary or packed fields are to contain numeric syntax null values. Null values are preserved only by using the batch load and unload utilities. Refer to Appendix C, Null Handling for more information.
If you are using FTP to transfer unloaded data between z/OS and Windows or Solaris, transfer the files in binary and specify the z/OS FTP LOCSITE subcommand with the RDW parameter.
Security on S6BBRULH
Unload Restrictions
Unloading is not permitted under either of the following conditions:
Permissions Enforced
The following permissions are enforced for allowable unloads:
If the requestor is either the owner of the target table or the security administrator of the owner, the request is allowed.
If the requestor is neither the owner of the target table nor the security administrator of the owner, and the requestor’s security classification is less than the security clearance required of the target table, the request is denied.
If the requestor has READ ACCESS to the target table by virtue of direct permission granted to the user ID or the current group, for example, the request is allowed; otherwise, the request is denied.
Unload Requestor Identity
The Unload Requestor is identified by:
The USERID entered in the U=userid parameter in the EXEC statement.
If this parameter is supplied, the USERID is always be considered to be that of the requestor.
The USERID (owner) of the job step (JOB statement USER=), which is assumed secured by z/OS security. This USERID is used only if no USERID is provided in the EXEC statement PARM.
If a USERID is supplied in the EXEC PARM statement and it differs from the job step’s USERID, a TIBCO Object Service Broker password must be provided in the EXEC parameter P=password.
EXEC Statement Changes
Note the following changes to the JCL EXEC statement:
PARM=’ttttttmmmmmmmm’
where:
PARM=’T=tttttt,M=mmmmmm,U=uuuuuu,P=pppppp
where:
Do not use password if U=uuuuuu is not included.
If this format is used, it is not necessary to include U=uuuuuu if the job step user ID is also the TIBCO Object Service Broker user ID.
Error Situations
If the security check determines the request to be unauthorized, the utility writes the following error message to the audit report:
S6BBU139E ACCESS FOR UNLOAD DENIED
It then writes a corresponding message in the log and finally abends with a code of 202.

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