![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
When you access external data from TIBCO Object Service Broker, import field data types are translated to the field types defined in the IMP table. You can access the data using:
• In the Open Systems versions of TIBCO Object Service Broker, use the DSBIFTYPE Execution Environment parameter to set the file type to LENGTH_PREFIXED_EBCDIC type files when migrating data from one TIBCO Object Service Broker system to another.You can browse an import table in the same way you would browse any other table with the following exceptions:
• The table definition must have one to eight primary keys, but the data in the table does not have to result in unique values in the key fields for each row.
• If your table definition contains fields of syntax C or V that are longer than 260 bytes, or fields of syntax RD or UN that are longer than 130 bytes, you must use SELECT LIKE instead of SELECT to access fields of this length.
• Accessing import data using the rules language is similar to accessing native TIBCO Object Service Broker data. You can access external data online or in batch mode using tools such as COPY_DATA to copy external data to a TIBCO Object Service Broker table that you can update.Because multiple record formats for import tables are implemented by accessing parent and child tables, workbench tools such as the Table Browser cannot be used. Use either rules or the TIBCO Object Service Broker Host Language Interface. For a sample rule, refer to Sample Rules.
• Each transaction stream accessing external data requires its own server thread. Ensure your system administrator is aware of the number of server threads required to accommodate all transaction streams accessing external data in a single transaction.
• If you use the default CTABLESIZE Data Object Broker parameter value, you can access at least 16 import tables per transaction; more, depending on the size of the import table definitions, since the more fields you define, the more space is required to hold the definition in the memory in the Data Object Broker and the Execution Environment.A single cursor is used to retrieve import data for the following retrieval statements in your rule:
•
• Import files with multiple record formats cannot be sorted (ORDERED clause) or selected (WHERE clause) by field values.A GET statement to an import table causes the search for the first occurrence that satisfies the specified selection criteria to be started at the beginning of the import table.A GET … ORDERED statement must retrieve all import data that satisfies the selection criteria and sort it in the Execution Environment before returning the first occurrence that meets the selection criteria.When using a FORALL statement, occurrences are returned to TIBCO Object Service Broker in the order in which the import server passes them. If you require a different order, you must include an ORDERED clause in your FORALL statement. TIBCO Object Service Broker orders only occurrences specified in the selection criteria.Remote table access can cause a significant increase in message traffic. This is especially true with import tables that have the IDgen field set to Y, which is a normal requirement for handling data in multiple record import tables.To overcome remote table access limitations when processing a multi-record table, complete the following steps:
2. Access the import table remotely. Refer to the example rule that follows for an example of accessing an import table remotely.
RULE EDITOR ===> SCROLL: P
PEER_ACCESS1;
_
_ ---------------------------------------------------------------------------
_ ------------------------------------------------------------+--------------
_ FORALL REMOTE_TABLE : | 1
_ LOCAL_TABLE.* = REMOTE_TABLE.*; |
_ INSERT LOCAL_TABLE; |
_ END; |
_ ---------------------------------------------------------------------------
• TIBCO Object Service Broker Parameters for more information about the DSBIFTYPE Execution Environment parameter and the CTABLESIZE Data Object Broker parameter.
• TIBCO Object Service Broker Managing Data for more information on browsing tables.
• TIBCO Object Service Broker for z/OS External Environments for more information about the Host Language Interface.
• TIBCO Object Service Broker Programming in Rules for more information on transactions and writing rules.
• TIBCO Object Service Broker Shareable Tools for more information on the COPY_DATA tool.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |