After selecting a CA‑IDMS subschema, you can provide values to the IDM table specification segment. Provide the necessary entries for the fields listed below. After completing the necessary fields in the table specification segment, press Enter to validate the entries.
The CA‑IDMS ready mode to use when you access this table in a TIBCO Object Service Broker transaction running in update mode. If the transaction is running in browse mode, shared retrieval (SR) mode is used, regardless of what is specified in this field. The default mode is SR.
For subsequent accesses to other tables with different AREA names within the same transaction, a new READY in the same mode as the first READY is issued.
If a CA‑IDMS INDEX is used to access a record, and the Gateway receives a ‘0301’ CA‑IDMS status code indicating the AREA where the INDEX resides is not READY’d, the Gateway issues a READY for the INDEX’s AREA and continues processing. You can choose from the following modes:
The ID for the instance of, or group of instances of, TIBCO Service Gateway for IDMS/DB to use when accessing the table you are defining. This identifies a group of the Gateways with common characteristics, and must match the SERVERID parameter specified in the Gateway JCL. Refer to
Supplying Service Gateway for IDMS/DB Startup Parameters for more information. This is a required field for all IDM table definitions, except minimal definitions. The default is DEFAULT. Valid entries are character strings of up to eight characters.
Provides a different subschema to use at runtime for more efficient access. The runtime subschema does not have to be loaded into TIBCO Object Service Broker. If you do not specify a runtime subschema, the same subschema used for the definition is used by default.
When you request CA‑IDMS data with a FORALL statement, the Gateway retrieves all valid record occurrences and sends them to the Data Object Broker in variable length buffers of up to 4 KB each until the request is complete.
When this field is set to N, if REPLACE or DELETE statements for the same IDM table are embedded in the FORALL loop, the Gateway uses the DBKEY of each record in the definition to re-establish currency on the correct record and then REPLACE and/or DELETE it.
When this field is set to Y, the Gateway returns one occurrence at a time to the Data Object Broker instead of 4 KB buffers, removing the need to re-establish currency.
While this option removes the need to re-read the record occurrences to be updated, it significantly increases message traffic between the Gateway, the Data Object Broker, and the Execution Environment, and therefore must be carefully considered.
Type the physical database name to use when accessing this table in a TIBCO Object Service Broker transaction. Your system administrator can define a default database name for your user ID, described in
Providing Default Database Names for Users. This name overrides entries in this field for your user ID. The database name for the first IDM table accessed in a transaction is used for all subsequent accesses to CA‑IDMS for the life of the TIBCO Object Service Broker transaction.
