![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Developer’s workbench Type BATCHLOAD_CARDS <Enter> Type EX BATCHLOAD_CARDS <Enter>
− On z/OS systems, allocate a file to hold the control cards. This fixed block file must have a record length of 80 bytes.
− On non-z/OS systems, set the DSBIFTYPE Execution Environment parameter to TEXT.
If the table is non-parameterized, it must be empty. If the table is parameterized, the table instance you plan to load must not already exist.BATCHLOAD_CARDS references the table definition to establish the format and layout of the input file. If the definition of the table you are going to load closely resembles the layout of the input file, BATCHLOAD_CARDS references this table definition instead.See the TIBCO Object Service Broker Parameters manual for information on the DSBIFTYPE Execution Environment parameter.To define your control cards with BATCHLOAD_CARDS, you describe your input and output data in a series of screens. BATCHLOAD_CARDS then writes the necessary control cards in a file. Complete the following tasks:
Task A Execute BATCHLOAD_CARDS from a TIBCO Object Service Broker workbench
Control Card File The file (and member name if the file is a z/OS partitioned data set) to contain the BATCHLOAD_CARDS output. You can change the filename by typing over it. The character set ID for the language of the data. If the data being loaded is in a language other than the one shown, specify the appropriate character set in this field. Values are listed in Character Set Values below.
The lower portion of the Control Card Definition screen specifies the values to be used to create the S (specification) type control card. To override the defaults, type a new value in the space provided.
PAGE FILL LEVELS The percentage of usable page space that is filled during the load process. For more information about adjusting Page fill levels for TDS tables, refer to TIBCO Object Service Broker for z/OS Utilities. # of Input Records Dynamic Block Size The block size used for table instances and for temporary work files required to process secondary indexes. The small default block size can be detrimental to good performance and could require optimizing if secondary indexes are to be built for large tables, that is, tables with large numbers of rows.
To specify whether the input file was created using S6BBRULA or hrnbrula, type Y or N at the prompt:If you type Y, you must specify V (variable) as the file length format in the Input Data File Length Format field that follows.The name of the table you specified in the Table field on the previous screen appears in the Table field by default, because the table you are loading could resemble the layout of the input file.
1. Keep the default Table value or change it to a table that reflects the format of the input file. If you defined a table for your input file, enter the name of that table in this field.
2. To see the fields in the Table, press Enter. All the field definitions for that table appear on the screen.
3.
3. The lower portion of the Input File Definition Screen displays field definitions for the input file named on the Table Field. If, for example, you define a table named INPUT_FILE and change the Table value in the Input File Definition Screen to INPUT_FILE, the screen displays the fields of the INPUT_FILE table, as shown here:
To edit the field definitions displayed, clear the INPUT_FILE name from the Table field and press Enter. Now you can make changes to the other fields on the screen:
The number of post decimal positions for a numeric field. If omitted, the decimal number defaults to 0 and appears on the control cards as blank. The number of decimals is required to accurately convert the value to TIBCO Object Service Broker syntax. The location of the field within the input record. The offset is optional. If specified, it must start at 0 for position 1.Task C Match input file parameters and fields with data table parameters and fieldsTo match an input field with a receiving field, type the number of the input field in the blank area before the receiving field name. For example, in the screen that follows, SOCIAL_SECURITY (field 1) maps to PK, LAST NAME maps to F1, and so on:
The names of the input file/import table and the TDS table appear at the top of the screen. If an input file is described by a table, the table name appears in the Input File field; otherwise, it is left blank. The Table is the name of the TDS table that is loaded by S6BBRTBL or hrnbrtbl (the Batch Load utilities).If some fields are not mapped to input fields, you can load a constant value into each occurrence of a field or ignore fields of the table. If you want to specify a value for the field displayed, provide one in the VALUE field (to a maximum of 250 bytes). To ignore the displayed field, leave the VALUE field blank.In the following example, a common city and FAX number are added to each employee record loaded into the TDS table. Field F7 is ignored. If more fields than the ones displayed have not been mapped, use PF8 to scroll down.
• Primary key fields must be either cross-referenced to an input field or system generated (that is, an IDgen key). They must not appear on value cards.The following screen displays a list of TDS fields with the currently assigned primary and secondary keys. After viewing the secondary index fields, press PF4 to complete the control cards definition and write them in your file.
Notice the P and S designations for 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.The following tables relate control fields on the screens with their equivalent fields in the control records:
Syntax 1
I and H records contain a sequence number in columns 3 – 5, which must be consecutive and must start with 001. The types within these records must be in the order: R, if any, followed by P, if any, followed by F.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |