Copyright © Cloud Software Group, Inc. All Rights Reserved

SIXBUILD_CARDS (Prepare Cards for Batch Secondary Index Build)

SIXBUILD_CARDS helps you define the control cards required by the utility S6BBRSIX (Batch Secondary Index Build for TDS tables).

SIXBUILD_CARDS displays a series of screens for you to identify the table and secondary index fields, and then writes the necessary controls in a pre-allocated data set. For complete information about the Batch Secondary Index Build utility refer to S6BBRSIX (Batch Secondary Index Build for TDS Tables).

Invocation

Follow the instructions in the following sections to prepare cards.

•	Prepare Data Set for Control Cards

•	Invoke SIXBUILD_CARDS

•	Specify Secondary Indexes

•	Review Output Data Set

 

Task A Prepare Data Set for Control Cards

Before you can use SIXBUILD_CARDS, you must allocate a data set to hold the control cards. This data set must have a record length of 80 bytes and be fixed block.

Task B Invoke SIXBUILD_CARDS

To invoke SIXBUILD_CARDS, complete the following steps:

1.	Execute SIXBUILD_CARDS from the workbench as follows:

EX execute rule ==> SIXBUILD_CARDS

The following is the initial screen is illustrated with sample input:

---

 

Control Card Definition for SIXBUILD

 

 

Control Card File : USR01.BATCH.CNTLCARD(SIX)

 

Table : EMP_MSTR_TDS

 

Page Fill Levels : (Default = 75 % if blank)

Group Index :

Secondary Index :

 

# 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=EXIT

---

 

2.	Supply values for the following fields:

Control Card File	The pre-allocated data set (and member name if the data set is partitioned). You can change the data set name by typing over it.
Table	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 a new value in the space provided. The fields are explained in detail in Appendix A, Defining Batch Load Control Cards Manually.
Page Fill Levels	For more information about adjusting Page Fill Levels for TDS tables, refer to Page Fill Tailoring.

3.	To continue defining the control cards, press PF4.

Task C Specify Secondary Indexes

The following is the screen to specify secondary indexes:

---

 

Control Card Definition SIXBUILD

These are the fields and their key types for the selected HURON table.

Table: EMP_MSTR_TDS

Primary Secondary Field Name

Y _ PK

_ F1

_ F2

_ F3

_ F4

_ F5

_ F6

 

 

 

PFKEYS: 1=HELP 3=EXIT 4=CREATE CTL CARDS 12=CANCEL

Select the field for sixbuild by typing a ’Y’ in front of it

---

 

This screen displays a list of TIBCO Object Service Broker TDS fields with the currently assigned primary keys. Type a Y in the Secondary column beside the 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.

After specifying the secondary index fields, press PF4. The control cards are written out to your data set and the control cards definition is complete.

Task D Review Output Data Set

The following is an example of an output data set containing the control cards:

---

 

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

---

 

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.

SIXBUILD_CARDS Record Layout

These tables relate the on-screen control fields to their equivalent control-record fields:

Input File Definition	Screen	Record ID/Type	Columns
Table Name	1	H/R	64 - 79
Character Set:	1	H/R	9 - 12
Page Fill Levels:	1
Group Index		S	3 - 4
Secondary Index		S	9 - 10
# of Input Records	1	S	15 - 29
Total # of Fields	1	S	31 - 33
Dynamic Unit Name	1	S	35 - 42
Dynamic Block Size	1	S	44 - 48
# Volumes for work file	n/a	S	50 - 51

 

Field Definitions	Screen	Record ID/Type	Columns
Secondary Key Fields	2
TIBCO Object Service Broker Field Definitions:	n/a
Name		H/F or P	9 - 44
Semantic Type		H/F or P	46
Syntax		H/F or P	48
Length		H/F or P	49 - 52
Decimal		H/F or P	54 - 55
Key Type		H/F	57

Considerations

Note the following:

•	H type records contain a sequence number in columns 3 - 5, which 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.

•

You use the Dynamic Block Size 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. For large tables, that is, tables with large numbers of occurrences, consider optimizing the Dynamic Block Size to build secondary indexes.

 

Sample Report

The following illustrates the S6BTLPCL report:

---

 

 

 

 

 

---

 

 

 

Copyright © Cloud Software Group, Inc. All Rights Reserved