When accessing IMS data from TIBCO Object Service Broker, TIBCO Object Service Broker requests are translated into Segment Search Arguments (SSAs), which are used in a DL/I call to IMS. SSAs are built based on parameterized fields, access values, and the selection criteria specified for primary keys and any field defined in the DBD. The DBD used when data is accessed must be identical to the DBD used when the TIBCO Object Service Broker IMS table is defined.
If you modify the value of the primary key of a table in the Table Editor, a DELETE followed by an INSERT is issued on your behalf. If the segment the primary key is defined at is a parent, all child segments associated with that parent are deleted. Only the child segment occurrence displayed in the Table Editor is inserted back into the database.
Using the Single Occurrence Editor from the Table Browser begins a dependent transaction in TIBCO Object Service Broker, assigning a new Gateway. Therefore, to use the Single Occurrence Editor from the Table Browser, you must have one of the following running with the same SERVERID:
However, you can use the Single Occurrence Editor from the Table Editor without this condition, since this does not begin a dependent TIBCO Object Service Broker transaction.
If you include the unique sequence key of a child segment as a field of an IMS table (instead of a parameter, access value, or primary key) and you modify the value of this field the following occurs:
You can be sure only that the proper replacement occurs if unique sequence keys of child segments are identified as key fields to TIBCO Object Service Broker.
The sample screen below shows IMS data presented in TIBCO Object Service Broker table format. The IMS table is named CUST_ORDERS and the parameter values for CUSTNO and ORDER# are both 000001.
TIBCO Object Service Broker Managing Data for more information on browsing tables.