Abstract: A method, apparatus, and article of manufacture accesses a dataset using an unsupported access method. A first request to access a dataset is intercepted. The first request is associated with a first data structure that specifies a first access method. The first data structure is replaced with a second data structure that specifies a second access method which is different from the first access method. The dataset is accessed in accordance with the second access method of the second data structure. In another particular embodiment, the first access method is the basic direct access method, and the second access method is any of the basic sequential access method and the queued sequential access method. In yet another embodiment, the dataset is an extended format physical sequential dataset.

Abstract: An abstraction layer (50) is provided for facilitating accessing a database (10) containing database records each including a plurality of fields stored in one or more tables (12, 14). The abstraction layer (50) includes a control table (52) containing control records corresponding to database fields. Each control record contains metadata associated with the corresponding database field. The abstraction layer (50) also includes at least one additional table (54, 56, 58, 60, 62, 64, 66, 70, 72, 74, 80) containing additional metadata. Each database field is selectively associated with one or more selected portions of the additional metadata through metadata contained in the control record corresponding to the database field. A user database application (30) accesses the database (10) using metadata obtained from the abstraction layer (50).

Abstract: In a database, a high availability data replicator (28, 46, 48) synchronizes primary and secondary servers (10, 30). A smart large object application program interface (82) resides on the secondary server (30). A cache module (108) creates a memory cache (88) corresponding to a smart large object responsive to a smart large object read operation requested by a client (86). A smart large object read module (110) executes the read operation without acquiring a lock on the corresponding smart large object. An exception module (102) sends an exception to the client (86) responsive to a synchronizing event of the high availability data replicator (28, 46, 48) modifying said smart large object. On the primary server (10), log entries of the modifying operation are ordered so that a log entry updating a large object header of said smart large object is consistent immediately upon execution on the secondary server (30).

Abstract: A data processing apparatus includes a storage device having a replication generation function for replicating a data base to create a replication data base, and stores data and a plurality of log information in transaction processing that uses the data in the storage device, selects a transaction that is performing a data operation without meeting a predetermined condition after synchronization between the data base and the replication data base is released, and performs the data operation cancellation processing to the replication data base by the selected transaction. It also selects a transaction, which meets the predetermined condition and is not performing a data operation to the replication data base, to perform a data operation to the replication data base with the selected transaction. It then becomes possible to reduce the burden for the data processing apparatus during using the replication data base.

Abstract: An arrangement is provided for using a stack trace cache when performing root set enumeration in a stack of a thread during garbage collection. During the first root set enumeration in the stack, full stack unwinding may be performed and a stack trace cache may be created to cache stack trace information relating to stack frames. Subsequent sessions of root set enumeration in the stack may access and copy parts or the entire cached stack trace information instead of performing full stack unwinding.