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


Chapter 3 Tools : SIXBUILD_CARDS

SIXBUILD_CARDS
Defines the control cards required by the Batch Secondary Index Build utilities. (E)
Invocation
Do one of the following:
Usage Notes
SIXBUILD_CARDS helps you define the control cards required by the S6BBRSIX and hrnbrsix (Batch Secondary Index Build for TDS tables) utilities.
SIXBUILD_CARDS displays a series of screens where you identify the table and secondary index fields, and then writes the necessary controls in a file.
See Also
TIBCO Object Service Broker for z/OS Utilities or TIBCO Object Service Broker for Open Systems Utilities for complete information about the Batch Secondary Index Build utilities.
TIBCO Object Service Broker Parameters for information on the DSBIFTYPE Execution Environment parameter.
Procedure Overview
The following table summarizes the tasks to prepare cards:
 
Task A Prepare the file for the control cards
On z/OS systems, before you can use SIXBUILD_CARDS you must allocate a file to hold the control cards. This file must have a record length of 80 bytes and be fixed block.
Task B Invoke SIXBUILD_CARDS
Invoke the control card preparation facility, by following these steps:
1.
The initial screen is illustrated with sample input here:

 
Control Card Definition for SIXBUILD
v
Control Card File : USR01.BATCH.CNTLCARD(FEB2000)
Table : EMP_MSTR_TDS Character Set : ENGL
PAGE FILL LEVELS : (Default = 75 % if blank)
Group Index : Primary Index :
Secondary Index : Data Pages :
# of Input Records : (Default = 100000 if blank)
Total # of Fields : (Default = 50 if blank)
Dynamic Unit Name : (Default = SYSDA if blank)
Dynamic Block Size : (Default = 4096 if blank)
 
 
 
 
 
PFKEYS: 1=HELP 3=EXIT 4=CONTINUE 12=CANCEL

 
2.
The lower half of the screen specifies override values for the batch secondary index build process. Default values are available and appear on the screen. To override any of these defaults, type in a new value in the space provided.
3.
Task C Specify secondary indexes
The screen to specify the secondary indexes is shown here:

 
Control Card Definition SIXBUILD
These are the fields and their key types for the selected table.
Table: EMP_MSTR_TDS
Primary Secondary Field Name
Y _ PK
Y F1
F2
F3
F4
F5
F6
 
 
 
PFKEYS: 1=HELP 3=EXIT 4=CREATE CTL CARDS 12=CANCEL

 
This screen displays a list of TIBCO Object Service Broker fields with the currently assigned primary keys. Type a Y in the Secondary column beside the field or fields for which you want to define a secondary index. You can define a secondary index on any field except the first primary key field or fields with syntax RD (raw data) or UN (Unicode).
After specifying the secondary index fields, press PF4. The control cards are written out to your file and the control cards definition is complete.
Task D Review the output file
An example of an output file containing the control cards is shown here:

 
S 75 75 000000000100000 050 SYSDA
H 001 R EMP_MSTR_TDS
H 002 P PRM1 S C 0015
H 003 P PRM2 S C 0004
H 004 F PK I C 0009 P
H 005 F F1 S C 0015 S
H 006 F F2 S C 0015
H 007 F F3 S C 0025
H 008 F F4 S C 0025
H 009 F F5 Q P 0006 02
H 010 F F6 S C 0008
H 011 F F7 C B 0002

 
Notice the P and S designations next to the PK and F1 fields. These letters mean that PK is a primary key, and F1 is a secondary index. If a field is both a primary key and a secondary index, the designation is Q.
Record Layout
The following tables relate control fields on the screens with their equivalent fields in the control records:
 
TIBCO Object Service Broker Field Definitions:

1
Columns 45 to 48 contain the syntax if the field is raw data or Unicode; otherwise, the semantic type goes in column 46.

H type records contain a sequence number in columns 3 – 5 that must be consecutive and must commence with 001. The types within these records must be in the order: R, if any, followed by P, if any, followed by F.
The Dynamic Block Size, on z/OS only, is used for any temporary work files required to process secondary indexes and for table instances. The small default block size can be detrimental to good performance. If secondary indexes are to be built for large tables, that is, tables with large numbers of occurrences, consider optimizing the Dynamic Block Size.

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