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


Chapter 2 Operating Service Gateway for IDMS/DB : Defining CA‑IDMS Databases to TIBCO Object Service Broker

Defining CA‑IDMS Databases to TIBCO Object Service Broker
There are two methods you can use to define a CA‑IDMS database to TIBCO Object Service Broker, depending on the location of your CA‑IDMS data. Both methods produce the same results:
Using IDMSLOAD
IDMSLOAD in the JCL data set provides a sample JCL to extract a CA‑IDMS subschema definition from the IDD and load that definition into TIBCO Object Service Broker in a single job. IDMSLOAD performs the following functions:
1.
Extracts a CA‑IDMS subschema definition into four data sets (RECORD, ELEMENT, SET, and INDEX) that it automatically creates
2.
Executes the LOAD_IDMS_DEF rule to load the four data sets extracted in the previous step into TIBCO Object Service Broker tables
3.
Using S6BIDU12 and the IDMS Tool
To use S6BIDU12 and the IDMS tool to define a CA‑IDMS database to TIBCO Object Service Broker, complete the following tasks:
1.
2.
These tasks are described in the following sections.
 
Task A Extracting CA‑IDMS data dictionary information
To extract CA‑IDMS element, record, set, and index information from the IDD, use the S6BIDU12 program for subschemas for Release 12.0 and greater. The SYSIN member identifies the subschema that you want to define to TIBCO Object Service Broker and the dictionary where the subschema resides. You can request specific records to be unloaded if you do not require all records defined in the subschema. Only one subschema can be extracted at a time.
Extracting information from the IDD using the extract program
The extract program navigates the IDD database to create RECORD, ELEMENT, SET, and INDEX data sets, as shown in the illustration below. These data sets are defined to TIBCO Object Service Broker as import files and are loaded into TIBCO Object Service Broker control tables. This process is described in Task B, Loading a CA‑IDMS subschema definition into TIBCO Object Service Broker.
The sample JCL required to run the extract program exists in member IDMSUJCL of the JCL data set. This member extracts the CA‑IDMS subschema definition.
You must extract and load only the subschema that contains all the records defined in the application database. You can define all IDM tables using this subschema. When defining the table, you can specify which Run Time Subschema accesses the data.
Syntax For Identifying the CA‑IDMS Subschema
The illustration below shows a sample SYSIN member identifying the CA‑IDMS subschema in the extract program. To select specific records from a subschema, include as many REC lines as required.
The PREFSUFF=NO parameter removes the CA‑IDMS prefix or suffix added to element names from the TIBCO Object Service Broker control table entries. The default specification for this parameter is YES.
Task B Loading a CA‑IDMS subschema definition into TIBCO Object Service Broker
To load the information extracted from the IDD, as described in Extracting CA‑IDMS data dictionary information, complete the following steps:
1.
Edit the definitions for the @IDMS_GEN_ELE, @IDMS_GEN_REC, @IDMS_GEN_SET, and @IDMS_GEN_NDX tables.
For each of these tables, enter the name of the corresponding data set created by the extract program in the FILENAME field.
Notes: To edit these import tables you must have MODIFY_DEFN access to them. Only a level‑7 system administrator can assign MODIFY_DEFN for the import tables. For the @IDMS_GEN_REC layout, it is recommended that you allow for large record sizes >9999 bytes long by re-extracting the subschemas and reloading them into TIBCO Object Service Broker.
The IDMS load program fails when a second attempt is made to reload definitions for a given subschema. IDMS utilities use $CLRTAB prior to loading the definition, which requires the user to have MOD_DEFN permission on the following system tables: @IDMSELEMENTS, @IDMSRECORDS, @IDMSINDEXES, and @IDMSSETTS (this applies to level‑1 users).
2.
You can execute the tool from the workbench using either the EX execute rule option or the primary command field.
The screen below shows the Manager Utilities for IDMS Data main menu. To select a menu option, type an S in the line command field beside it and press Enter.

 
 
MANAGER UTILITIES FOR IDMS DATA
---------------------------------
Enter an "S" to select a function
_ List IDMS Tables
_ List IDMS Subschemas
_ Load an IDMS Subschema
_ Delete IDMS Subschemas
 
 
 
 
PFKEYS: 1=HELP 3=EXIT 12=EXIT

 
3.
A screen similar to the one below appears. Verify that the data set names on the screen correspond to those created by the extract program.

 
MANAGER UTILITIES FOR IDMS DATA: DEFINE SUBSCHEMA
Command ===>
------------------------------------------------------------------------------
About to define SUBSCHEMA: EMPSS01 from IMPORTFILES listed
------------------------------------------------------------------------------
IDMS Records ..... ...> USR00.IDMS.REC.DATA
IDMS Elements..... ...> USR00.IDMS.ELE.DATA
IDMS Sets ........ ...> USR00.IDMS.SET.DATA
IDMS Indexes ..... ...> USR00.IDMS.NDX.DATA
 
PFKEYS: 1=HELP 3=EXIT 12=EXIT 4=CONFIRM

 
4.
If the subschema definition currently exists, it is overwritten. The IDM table definitions using this subschema still exist; however, they contain no subschema changes. The sample screen below shows a count of the number of records, elements, sets, and indexes.

 
MANAGER UTILITIES FOR IDMS DATA: DEFINE SUBSCHEMA
Command ===>
------------------------------------------------------------------------------
About to define SUBSCHEMA: EMPSS01 from IMPORTFILES listed
------------------------------------------------------------------------------
IDMS Records ..... 14 ...> USR00.IDMS.REC.DATA
IDMS Elements..... 391 ...> USR00.IDMS.ELE.DATA
IDMS Sets ........ 24 ...> USR00.IDMS.SET.DATA
IDMS Indexes ..... 19 ...> USR00.IDMS.NDX.DATA
 
PFKEYS: 1=HELP 3=EXIT 12=EXIT 4=CONFIRM

 
If your subschema definition changes, re-extract the subschema with the extract program described in Extracting CA‑IDMS data dictionary information, and reload the subschema using the IDMS tool.
Determining When to Modify Table Definitions
You do not have to modify existing IDM table definitions unless one of the following changes occur:
See Also
TIBCO Object Service Broker Managing Security for more information on security access levels.

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