Abstract: The capturing of rich database metadata includes: capturing partitioned column metadata of a database as mappings defined by a plurality of constraint statements; defining non-standard user-defined types of the database according to a schema; defining physical representations of columns of the database according to the schema; and storing the defined mappings, the defined user-defined types, and the defined physical representations of columns to a catalog of the database. Application enumerated data values in the database may also be defined according to the XML schema and stored to the catalog of the database. In this manner, the database management system may manage application constraints, user-defined types, and physical representations of data for applications referencing the same database using the metadata information stored in the catalog of the database.

Abstract: Provided are techniques for processing structured content within Large Object (LOB) data that is stored in a column of a database table. Structural metadata describing structures that each define a different format of the structured content is stored. A request for data in the database table is received. The structural metadata is used to create an empty result set with columns defined by at least two of the structures. For each row of data in the database table that includes LOB data, control data is used to identify one of the structures to be applied to the structured content within the LOB data stored in that row of data, and the structured content within the LOB data in that row of data is mapped to the columns in the result set based on the identified one of the structures. The result set is returned.

Abstract: Provided are techniques for processing structured content within Large Object (LOB) data that is stored in a column of a database table. Structural metadata describing structures that each define a different format of the structured content is stored. A request for data in the database table is received. The structural metadata is used to create an empty result set with columns defined by at least two of the structures. For each row of data in the database table that includes LOB data, control data is used to identify one of the structures to be applied to the structured content within the LOB data stored in that row of data, and the structured content within the LOB data in that row of data is mapped to the columns in the result set based on the identified one of the structures. The result set is returned.

Abstract: Provided are techniques for processing structured content within Large Object (LOB) data that is stored in a column of a database table. Structural metadata describing structures that each define a different format of the structured content is stored. A request for data in the database table is received. The structural metadata is used to create an empty result set with columns defined by at least two of the structures. For each row of data in the database table that includes LOB data, control data is used to identify one of the structures to be applied to the structured content within the LOB data stored in that row of data, and the structured content within the LOB data in that row of data is mapped to the columns in the result set based on the identified one of the structures. The result set is returned.

Abstract: Provided are techniques for processing structured content within Large Object (LOB) data that is stored in a column of a database table. Structural metadata describing structures that each define a different format of the structured content is stored. A request for data in the database table is received. The structural metadata is used to create an empty result set with columns defined by at least two of the structures. For each row of data in the database table that includes LOB data, control data is used to identify one of the structures to be applied to the structured content within the LOB data stored in that row of data, and the structured content within the LOB data in that row of data is mapped to the columns in the result set based on the identified one of the structures. The result set is returned.

Abstract: The capturing of rich database metadata includes: capturing partitioned column metadata of a database as mappings defined by a plurality of constraint statements; defining non-standard user-defined types of the database according to a schema; defining physical representations of columns of the database according to the schema; and storing the defined mappings, the defined user-defined types, and the defined physical representations of columns to a catalog of the database. Application enumerated data values in the database may also be defined according to the XML schema and stored to the catalog of the database. In this manner, the database management system may manage application constraints, user-defined types, and physical representations of data for applications referencing the same database using the metadata information stored in the catalog of the database.

Abstract: The present invention relates generally to data retrieval, and more particularly but not exclusively to obtaining referentially converted user data having user-defined data types. In one implementation, the present invention is a method for retrieving user data in a data system using one or more application programs for defining a layout for each user data type, defining one or more conversion routines for non-standard data types, calling a coordination call to map standard and non-standard data types, and retrieve the user data from the data storage device.

Abstract: The apparatus and system are provided for defining a metadata schema to facilitate passing data between an XML document and a hierarchical database. The invention includes a database accessor, a document accessor, and an association module. The database accessor accesses a database schema indicative of database field names and a hierarchical structure for a hierarchical database. The document accessor accesses a document schema that defines the hierarchical structure, content data syntax, and semantics of valid, well-formed, XML documents that can be passed into and out of the hierarchical database. The document schema also includes at least one XML element name that maps to a corresponding database field name in the database schema. The association module associates the database schema and the document schema to provide a metadata schema that enables data to be passed between an XML document and the hierarchical database.

Abstract: An apparatus, system, and method are provided for defining a metadata schema to facilitate passing data between an XML document and a hierarchical database. The invention includes a database accessor, a document accessor, and an association module. The database accessor accesses a database schema indicative of database field names and a hierarchical structure for a hierarchical database. The document accessor accesses a document schema that defines the hierarchical structure, content data syntax, and semantics of valid, well-formed, XML documents that can be passed into and out of the hierarchical database. The document schema also includes at least one XML element name that maps to a corresponding database field name in the database schema. The association module associates the database schema and the document schema to provide a metadata schema that enables data to be passed between an XML document and the hierarchical database.

Abstract: The present invention relates generally to data retrieval, and more particularly but not exclusively to obtaining referentially converted user data having user-defined data types. In one implementation, the present invention is a method for retrieving user data in a data system using one or more application programs for defining a layout for each user data type, defining one or more conversion routines for non-standard data types, calling a coordination call to map standard and non-standard data types, and retrieve the user data from the data storage device.

Abstract: The apparatus and system are provided for defining a metadata schema to facilitate passing data between an XML document and a hierarchical database. The invention includes a database accessor, a document accessor, and an association module. The database accessor accesses a database schema indicative of database field names and a hierarchical structure for a hierarchical database. The document accessor accesses a document schema that defines the hierarchical structure, content data syntax, and semantics of valid, well-formed, XML documents that can be passed into and out of the hierarchical database. The document schema also includes at least one XML element name that maps to a corresponding database field name in the database schema. The association module associates the database schema and the document schema to provide a metadata schema that enables data to be passed between an XML document and the hierarchical database.

Abstract: A method is provided for defining a metadata schema to facilitate passing data between an XML document and a hierarchical database. The invention includes a database accessor, a document accessor, and an association module. The database accessor accesses a database schema indicative of database field names and a hierarchical structure for a hierarchical database. The document accessor accesses a document schema that defines the hierarchical structure, content data syntax, and semantics of valid, well-formed, XML documents that can be passed into and out of the hierarchical database. The document schema also includes at least one XML element name that maps to a corresponding database field name in the database schema. The association module associates the database schema and the document schema to provide a metadata schema that enables data to be passed between an XML document and the hierarchical database.

Abstract: An apparatus, system, and method are provided for passing data between an XML document and a hierarchical database. The apparatus, system, and method include a hierarchical database, a metadata schema, and a mapping module. The hierarchical database comprises a conventional hierarchical database, such as IMS. The metadata schema is derived from the hierarchical database. The metadata schema includes a first representation representative of the hierarchical structure of the hierarchical database, a second representation representative of the hierarchical structure of XML documents valid for passing into and out of the hierarchical database, one or more database field names, and one or more XML element names that map to the one or more database field names. The mapping module passes data between the XML document and the hierarchical database using the metadata schema.

Abstract: A database definition, logical database view, extended field definition and control statement information are accessed to build an in-memory representation of selective information contained therein. Utilizing this in-memory representation, a class in one form is automatically generated and customized wherein this class is used to access a hierarchical database responsive to a hierarchical database access request from an application.

Abstract: A system for identifying and utilizing a secondary index to access a database using a management system without an internal catalogue of online metadata. The system receives an application request to access a database from the application program, and parses the application request to determine at least one column name and at least one table name. The system utilizes an online catalogue containing metadata to translate the column name to a field name and the table name to a segment name, wherein the segment name has an associated secondary index. The system utilizes the online catalogue to determine an associated secondary index name, and builds a database request that includes the segment name, the field name, and the associated secondary index name. The system then sends the database request to the database management system, so that the associated secondary index can be used by the database management system in response to the database request.

Abstract: A database definition, logical database view, extended field definition and control statement information are accessed to build an in-memory representation of selective information contained therein. Utilizing this in-memory representation, a hierarchical database schema report is automatically generated wherein this hierarchical database schema report may be used to write application code to access the hierarchical database without further need to utilize the database definition, the extended field definition, the logical database view or any combination thereof.

Abstract: A system for identifying and utilizing a secondary index to access a database using a management system without an internal catalogue of online metadata. The system receives an application request to access a database from the application program, and parses the application request to determine at least one column name and at least one table name. The system utilizes an online catalogue containing metadata to translate the column name to a field name and the table name to a segment name, wherein the segment name has an associated secondary index. The system utilizes the online catalogue to determine an associated secondary index name, and builds a database request that includes the segment name, the field name, and the associated secondary index name. The system then sends the database request to the database management system, so that the associated secondary index can be used by the database management system in response to the database request.

Abstract: A database definition, logical database view, extended field definition and control statement information are accessed to build an in-memory representation of selective information contained therein. Utilizing this in-memory representation, a hierarchical database schema report is automatically generated wherein this hierarchical database schema report may be used to write application code to access the hierarchical database without further need to utilize the database definition, the extended field definition, the logical database view or any combination thereof.

Abstract: A database definition, logical database view, extended field definition and control statement information are accessed to build an in-memory representation of selective information contained therein. Utilizing this in-memory representation, a class in one form is automatically generated and customized wherein this class is used to access a hierarchical database responsive to a hierarchical database access request from an application.