Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Appendix B Samples of Recommended Table Definitions : Sample Table Definitions

Sample Table Definitions
Sample IMS Database with Unique Segments
If you need to directly retrieve or update specific IMS data, you should have one TIBCO Object Service Broker IMS table definition for each segment that can be uniquely identified. The illustration below shows a sample IMS database where all segments contain unique sequence keys.
Creating the Sample Table Definition
To create an IMS table definition for each segment in the illustration above, complete the following steps:
1.
2.
3.
4.
5.
Sample IMS Database with Non-unique Segments
The illustration below shows an IMS database containing non-unique segments.
Retrieving and Updating Non-unique IMS Data
If you need to directly retrieve or update non-unique IMS data, complete the following steps:
1.
Determine the type of key (unique, multiple, or no key) for each segment of the database using the @IMSSEGS(dbname) control table.
2.
3.
4.
If you plan to modify IMS data using this definition, specify Optimize Update=Y in the IMS Table Definition screen.
5.
If you plan to modify IMS data using this definition, specify Optimize Update=Y in the IMS Table Definition screen.
6.
If you plan to modify IMS data using this definition, specify Optimize Update=Y in the IMS Table Definition screen.
7.
8.
Segment G has a unique sequence key; however, if you plan to modify IMS data using this definition, you must still specify Optimize Update=Y in the IMS Table Definition screen, since its parent (segment E) does not have a unique sequence key.
For definitions containing non-unique IMS segments, the Gateway requires a minimum of two identical PCBs defined for the database in question. Refer to Retrieval Processing for more information.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved