![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Task B: Define Fields for the DAT TableA field definition consists of both the TIBCO Object Service Broker and CA Datacom definitions. The TIBCO Object Service Broker field definition is extended by the CA Datacom field definition. Use the Extensions screen to define the TIBCO Object Service Broker portion of the field definition.To define fields, press PF5 on the Table Definition screen. The following illustration shows the leftmost portion of the screen. Press PF11 to view the CA Datacom field information displayed to the right.
• If you enter the Table Definer with the DATACOM tool, TIBCO Object Service Broker and CA Datacom field values are provided in this Extensions screen. Modify the TIBCO Object Service Broker field values as required; modifications cannot be made to the CA Datacom values.
• If you entered the Table Definer directly, values are not provided unless you are modifying an existing DAT table.Fields in CA Datacom are not necessarily in the same sequence as in TIBCO Object Service Broker.Either type in or modify values directly or press PF2 to display the Fields screen for the selection of fields. If you select the fields using the Fields screen, default values are provided for the definition. You can modify the following fields:
Specifies the position of the field in the table. You can re-order the fields by typing new values in this field or you can delete the field by blanking out the number. There is no limit as to the number of fields you can name, either using the Table Definer or generating the definition.The number of fields you can select depends on the length of the sum of all fields, primary keys, and parameters. This sum plus control information must be less than or equal to 31,744 bytes.A valid entry is a character string of up to 16 characters beginning with a letter (A - Z) or a special character ($ or #), and continuing with more letters, special characters, digits (0 - 9), or underscore characters (_), for example, DEPTNO. Elements are field collections that CA Datacom rows consist of. Enter the five-character element name on this screen, once per element, in the line that corresponds to the field with the lowest row offset (Xoff) within that element. When you return to the table screen, the element list there will contain all the element names you have entered. The value that uniquely identifies each occurrence in the table. At least one field must be defined as a primary key field. The primary key can be a single field or a composite of up to 16 fields, with a maximum length of 127 bytes. For more information, see Selecting Fields. The valid entries are as follows:
• P — Primary key. Specifies the TIBCO Object Service Broker semantic data type of the CA Datacom field. The valid entries are as follows:Refer to Translating Data Types for information on the default mapping of Datacom data types to TIBCO Object Service Broker semantic types and syntax. Specifies the TIBCO Object Service Broker syntax of the CA Datacom field. The valid entries are B, C, P, V, F, W, UN, and RD.Refer to Translating Data Types for information on the default mapping of Datacom data types to TIBCO Object Service Broker semantic types and syntax. Specifies the TIBCO Object Service Broker length of the Datacom field, in bytes. Refer to Translating Data Types for the default mapping of Datacom data types to TIBCO Object Service Broker semantic types and syntax. When reading or writing data from or to CA Datacom, the server converts the data from or to the format described by these attributes. Exercise caution if you change them.Xsyn — TIBCO Object Service Broker’s external syntax mapping the CA Datacom data type of the field in the CA Datacom table row.Xlen — The length in bytes of the field in the CA Datacom table row.Xdec — The number of digits to the right of the decimal point in the field in the CA Datacom table row.Xoff — The offset of the field in the CA Datacom table row. You cannot change this value, which has been computed either by the metadata extractor or by the UI Table Editor, depending on which of these two tools you used to generate the definition. The name that originates from either the CA Data Dictionary or, if you created your DAT definition through the TIBCO Object Service Broker Eclipse UI table definer, from the COBOL copybook you used. Specifies the number of digits to the right of the decimal point. This field is relevant only for syntax P. The valid entries are as follows: Specifies if the field is required. Any field can be a required field. By definition, a primary key field is a required field. The valid entries are as follows:
• Y — Required. Every occurrence in the table must have a value for this field. Inserting or editing an occurrence without valid values in required fields causes an exception to be raised. If a table is to be referenced when a user is inserting or replacing a value in the field, enter the name of a table that is to be referenced. The added or modified value must exist as a primary key value in the referenced table or the action fails.Reference checking is not done if a null value is given for a field that is not required and does not have a default value. A valid entry is the name of any table except a table of type SCR, RPT, or EXP; the primary key field on the table must hold the values for the referenced field. The table cannot be parameterized. If you specify a default value for a field and no data is provided, the default value is used instead of a null value. A valid entry is any valid value for the field. If arithmetic operations are to be performed on numeric fields of type Q or C, you must enter a numeric default value such as 0.00; arithmetic operations cannot be performed on data containing null values.
From the sample Extensions screen shown in Defining Fields, use PF2 to display a listing of available fields for selection.Type an S in the line command field of each field that you require. Press PF3 to save the selection and return to the Extensions screen. Press PF12 to cancel and return to the Extensions screen.
• Group fields and simple fields are available for selection. You must not have overlapping fields in your DAT table definition. Use the fields Off and Length to determine if fields are overlapping. Pressing PF3 from the Extensions screen also validates for overlapping.
• The primary key of the DAT table must include all the master key fields of the CA Datacom table, with no overlapping of fields. You can include both group fields and simple fields in the primary key.TIBCO Object Service Broker holds a maximum of 16 fields in a composite primary key; however, you can use the Table Editor and the Table Browser only on tables that have a maximum of eight fields.
• Component fields of a master key must have the same order in the primary key. If the field is part of a master key, a value greater than 0 in the MKS field indicates the sequence of the fields in the master key.
• Newly selected fields are placed last in the order of existing fields, and are automatically numbered when you return to the Extensions screen.The following table illustrates CA Datacom data types that can be converted to TIBCO Object Service Broker syntax. Default translations are shown in the following table.
D N 161 U P L packed, unsignedG N 327181 UN UN L graphicH N 327181 V V L hexadecimal, two-byte displayK N 327181 UN UN L Kanji, same as GN N 311 M P L/2+1 zoned decimal, unsignedN Y 311 N P L/2+1 zoned decimal, signedRAW N 327191 H RD L+4 all "other" data typesY N 327181 UN UN L DBCS, same as GZ N 327191 W W L mixed (DBCS & SBCS)
1The reported/assumed length of the CA Datacom field is less or equal to this number. The notation L in the Len column refers to this length.The CA Datacom interface used by TIBCO Object Service Broker has no concept of nulls. As a result, the following translations occur:For more information on null processing within TIBCO Object Service Broker, refer to the TIBCO Object Service Broker Programming in Rules manual.You can modify any attribute in the TIBCO Object Service Broker field definition section of the Extensions screen. You can:
• Change the default order in which the fields appear, by typing new numbers in the # field. When you are defining the order, specify the primary key(s) as the first field(s).
• The other selected fields follow the primary key(s) in numeric order from top to bottom of the list. Fields without numbers are deleted.
• Change the entry in the Name field to a new name to uniquely identify the field within the DAT table.
• You can name a field the same as a field in another table; if you are moving data between tables, giving the fields the same name simplifies the process.
• Change the TIBCO Object Service Broker semantic type (Type field) and syntax (Syn field) of the field.You can use any valid TIBCO Object Service Broker semantic type (except date) and syntax (except floating point), provided the combination is valid. Refer to the TIBCO Object Service Broker Programming in Rules manual for a list of valid combinations.
Changing the TIBCO Object Service Broker field syntax can cause a conversion error, since the server must convert each affected field of each row to the new syntax as defined in the DAT Table Definition.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |