![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The S6BIMSU program extracts IMS database, segment, and field information for physical databases from the IMS DBD load modules. S6BIMSU can extract only database and partial segment information for logical databases. Refer to Completing the Definition for a Logical Database for more information. A SYSIN member identifies the DDname of the IMS DBD load libraries and specifies the load modules to be processed by S6BIMSU. The extracted information is stored in the data set associated with the SYSPUNCH DDname.You must allocate the SYSPUNCH data set before you run S6BIMSU. You can use an existing partitioned data set and specify a new member. If you specify an existing member name, its contents are overwritten.Task C, Load an IMS database definition into TIBCO Object Service Broker describes how to define the SYSPUNCH data set to a TIBCO Object Service Broker import file. The IMS tool loads DBD information into control tables defining the IMS database to TIBCO Object Service Broker.Sample JCL for the S6BIMSU program is included as member IMSUJCL in the JCL data set. Modify this JCL as required.A sample SYSIN member is located in member XIMSUJCL of the CNTL data set. This SYSIN member identifies the DBD load modules to be processed and the DDnames associated with the load libraries.The DBD statement must start in column 5. One or more load libraries and modules can be specified in the SYSIN member. Use the following syntax when defining the SYSIN member:dbdname – the DBD load module name.library – the DDname of the DBD load library.Before loading the extracted data set into TIBCO Object Service Broker, users responsible for loading the DBD information must be given MODIFY_DEFN authority to the IMSGEN import table. Only a level‑7 system administrator can assign MODIFY_DEFN for the import table.TIBCO Object Service Broker Managing Security for more information on security levels.
1. Identify the data set that contains the extracted IMS DBD information to TIBCO Object Service Broker.The S6BIMSU program creates a SYSPUNCH data set. Information from this data set must be imported into TIBCO Object Service Broker where it is stored in the @IMSDBS, @IMSSEGS, @IMSDBD, and @IMSSIXFIELDS control tables. To import the SYSPUNCH information, complete the following steps:In the FILENAME field of this table, specify the name of the output data set created using the S6BIMSU program. If the data set is partitioned, include the member name.
2. Execute IMS from the EX execute rule option or the primary command field on the workbench.The screen below shows the Manager Utilities for IMS Data menu. From this screen you can select an option by typing an S beside the option and pressing Enter.
If any definitions are currently defined to TIBCO Object Service Broker, they are overwritten. The existing IMS table definitions using these databases still exist; however, they do not contain new DBD information.
5.
6. If the target segment of an IMS secondary index is not the root segment, and you use this secondary index to access the IMS database, IMS returns the segments in an order different from the expected orderIf this type of secondary index is used to access IMS data from TIBCO Object Service Broker, you must do one of the following:
− Modify the PARENT and LEVEL fields of the @IMSSEGS control table to reflect the new order in which the segments are returned.
− Create an IMS logical database that reflects the new order in which the segments are returned and define the logical database to TIBCO Object Service Broker.
If you require access to an IMS database from TIBCO Object Service Broker using both the primary and secondary processing sequence, a logical database is required. Refer to Defining Gateway Program Specification Blocks for more information.Logical databases establish relationships between segments that belong to other physical databases. Logical database definitions refer only to the physical databases for each segment named; therefore, the S6BIMSU program extracts only the following logical DBD information:You must add the missing information to the @IMSSEGS, @IMSDBD, and @IMSSIXFIELDS control tables before you can access the logical database from TIBCO Object Service Broker. You can add the information manually or complete the following steps:
1. Using the S6BIMSU program, import the physical database definition for each segment named in the logical database definition.
2. Check that the physical database segment names are the same as the logical database segment names.If the names are not the same, note which physical database segment name corresponds to each logical database segment name.
3. Using the CT copy table option from the workbench, copy the @IMSSEGS(physical database name) table instance to the @IMSSEGS(logical database name) table instance.
−
−
−
4. If you have a corresponding logical database, do one of the following, depending on whether your database definition uses secondary indexes:
− If your database definition does not use secondary indexes, use the CT copy table option from the workbench to copy the @IMSDBD(physical database name, physical segment name) table instance to the @IMSDBD(logical database name, logical segment name) table instance. This defines the field information. The physical segment name is the name that corresponds to the logical segment name, described in Step 2.
If the logical database is made up of segments from different databases, check the logical database definition to determine the order in which the segments are defined, and copy them into the @IMSDBD(logical database name, logical segment name) table instance in this same order. Ensure that the IMSOFF field is updated to reflect the correct offsets after combining the physical segment definitions.
− If your database definition does use secondary indexes, use the CT copy table option from the workbench to copy the @IMSSIXFIELDS(physical database name, physical targetsegment name, physical field name) table instance to the @IMSSIXFIELDS(logical database name, logical targetsegment name, logical field name) table instance.
Existing control tables are overwritten by S6BIMSU. After using this program, you must edit the @IMSSEGS and @IMSDBD tables as described above to replace the additional information required for logical databases.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |