Abstract: A computer program product is provided as a system and associated method to provide a robust, fail-safe, fast environment for running non-native language routine programs, such that when the program fails or terminates, the virtual machine can be restarted without terminating the operating system process. The system dynamically creates a number of independent virtual machines to run non-native language routines. Each virtual machine is created in a process external to the database engine, in a refreshable native runtime environment inside the process or address space. If the virtual machine should terminate with an uncaught exception or error or if it becomes unusable for executing other non-native language routines, the system recognizes that condition and terminates the native runtime environment without terminating the process.

Abstract: A method and system for efficiently providing maintenance activity on a relational database that is utilized within a processing system is disclosed. The relational database includes a pool of threads and a plurality of resources. The pool of threads receive requests from a plurality of clients and control the plurality of resources. The method and system comprise determining that a maintenance activity is required and providing a first command that initiates a first process which terminates all threads in the pool of threads if the maintenance activity is required. The method and system further include providing a second command which initiates a second process after the maintenance activity has completed which causes the threads to be created and initiates the processing of requests.

Abstract: Aspects for dynamically changing attributes in an embedded-SQL application are described. In these aspects, an option is provided within a standard SQL statement for specifying one or more attributes of at least a declared cursor. The standard SQL statement is then processed to include the specified one or more attributes in at least the declared cursor. The provision occurs with an ATTRIBUTES option and within a PREPARE SQL statement.

Abstract: A method and system for efficiently providing maintenance activity on a relational database that is utilized within a processing system is disclosed. The relational database includes a pool of threads and a plurality of resources. The pool of threads receive requests from a plurality of clients and control the plurality of resources. The method and system comprise determining that a maintenance activity is required and providing a first command that initiates a first process which terminates all threads in the pool of threads if the maintenance activity is required. The method and system further include providing a second command which initiates a second process after the maintenance activity has completed which causes the threads to be created and initiates the processing of requests.

Abstract: Provided is a method, system, and program for accessing data in a distributed database environment. A client program receives multiple requests for data from a database object satisfying specified search predicates from an application program. Each request includes a request for at least one row from the table. The client program transfers a database command and a rowset parameter indicating a maximum number of rows to return to a server program over a network if the requested row is not maintained by the client program. A data block is generated with the server program including rows from the database object satisfying the search predicates in response to the database command. The rows included in the data block do not exceed the rowset parameter. The server program transfers the data block to the client program. In turn, the client program returns at least one requested row from the received data block in response to one request for the at least one row of data from the application program.

Abstract: Using a database management system's own infrastructure to invoke a stored procedure for creating and preparing a database application. The stored procedure automates the pre-compile, compile, linker, and binder steps performed in creating and preparing the database application. The stored procedure is invoked to perform these steps in order to render the database application executable by the RDBMS. In conjunction with the invocation of the stored procedure, input parameters for the stored procedure may be specified including the requested function, the name of the database application, the source code for the database application, pre-compiler options, compiler options, linker options, binder options, and runtime options. The outputs from the stored procedure may include an executable load module, a database resource module, an output parameter string indicating the success or failure of each step, and one or more result sets containing the outputs of each step.

Abstract: A method, apparatus, and article of manufacture for a computer implemented authorization system. A statement is to be executed by a computer to manipulate data in a database stored on a data storage device connected to the computer. Initially, an environment of the database from which the statement was invoked is identified. Additionally, a security option is identified. Then, authorization privileges for the statement are determined based on the identified environment and security option.

Abstract: A client connected to a multi-server system, (e.g., a parallel database management system) can locate a server product that may have moved to a different network address within the multi-server system. For example, a client is able to perform two-phase commit and automatic resynchronization with a same DBMS server that may have moved to a new network address before a transaction was committed. A unique resync port number is assigned to each server member when the server member is started up. The server's physical IP address and resync number are stored in a list in a global area accessible by each server member. When a client establishes a connection to a server member, the client will receive the server member's resync number or the global list. The client records the server's unique resync number in the client's dataset.

Abstract: The system, method and program of this invention provides a technique that enables a client, connected by a network, such as TCP/IP, to a multi-server system, such as a parallel database management system, to locate a server product that may have moved to a different network address within the multi-server system. More specifically, the client is able to perform two-phase commit and automatic resynchronization with a same DBMS server that may have moved to a new network address before a transaction with the client was committed. In order to complete the two-phase resynchronization process for uncompleted units of work, the client system has to reestablish connection to the previously connected DBMS member.

Abstract: The system, method, and program of this invention allows a two-phase commit protocol to work properly, even when the client acting as the coordinator does not have a log to record two-phase state information. In a preferred embodiment, the client in a client/server distributed transaction processing system is a personal computer. The client, without a recovery log, acts as a coordinator of a commit process. The coordinator migrates, i.e., passes, responsibility for resynchronization, and any associated logging requirement, to a server, e.g., to any of the connected relational database management system (RDBMS) servers, which is a participant in the transaction. The server uses its own recovery log for use in satisfying the logging requirement.

Abstract: Apparatus and accompanying methods for use preferably in a multi-system shared data (sysplex) environment (100), wherein each system (110) provides one or more servers (115), for dynamically and adaptively assigning and balancing new work and for new session requests, among the servers in the sysplex, in view of attendant user-defined business importance of these requests and available sysplex resource capacity so as to meet overall business goals. Specifically, systems and servers are categorized into two classes: eligible, i.e., goal-oriented servers running under a policy and for which capacity information is currently available, and candidate, i.e., servers which lack capacity information.