Abstract: A tool for standardized layout transformations of BIDI data exchanged between legacy and modern systems is provided. Responsive to a determination that data requested in a client request is BIDI data, the tool initiates a layout transformation of the data requested at a single point within a database server. The tool determines a plurality of data from a connection string of the client request, wherein the plurality of data indicates a type of bi-directional data transformation. Responsive to the plurality of data from the connection string indicating data being returned to the client application from a database, the tool converts visual data to logical data at the single point within the database server. The tool returns transformed BIDI data to a client application. The tool inserts the transformed BIDI data into a database.

Abstract: A method for updating drivers. The method may include transmitting a connection request from a first computer to a second computer. The method may include creating a connection handshake in the first computer in response to the transmitted connection request, whereby the connection handshake includes client credentials and driver information. The method may include transmitting the created connection handshake from the first computer to a second computer. The method may include determining the first computer is authorized to connect to the second computer based on the client credentials. The method may include determining a first version level of a first plurality of drivers associated with the first computer is a lower version level than a second version level of a second plurality of drivers associated with the second computer based on the driver information. The method may include transmitting a driver update. The method may include installing the driver update.

Abstract: Exposing existing database server attributes that are used for load balancing, accounting, log filtering, problem determination, and end user identification as tenant identifiers. An example of such attribute is the values in existing client information fields that are available to applications for passing additional information to the database server via connections. These values are then used by the database server for enhanced operational functions of load balancing, accounting, log filtering, problem determination, and end user identification.

Abstract: A method for updating drivers. The method may include transmitting a connection request from a first computer to a second computer. The method may include creating a connection handshake in the first computer in response to the transmitted connection request, whereby the connection handshake includes client credentials and driver information. The method may include transmitting the created connection handshake from the first computer to a second computer. The method may include determining the first computer is authorized to connect to the second computer based on the client credentials. The method may include determining a first version level of a first plurality of drivers associated with the first computer is a lower version level than a second version level of a second plurality of drivers associated with the second computer based on the driver information. The method may include transmitting a driver update. The method may include installing the driver update.

Abstract: A first compute node of a plurality of compute nodes of a database cluster may receive a request for a database transaction from a client application. The client application may be located within the first compute node. A first connection may be established, without regard to whether another compute node has a lighter workload than the first compute node, between the client application and a first database of the database cluster. The first connection may be a local connection, wherein the first database is located within the first compute node. The first compute node may detect that a failure associated with the first database has occurred. The first compute node may execute a failover operation to continue servicing the request for the data. The executing of a failover operation may include establishing a second connection between the client application and a second database of the database cluster.

Abstract: Exposing existing database server attributes that are used for load balancing, accounting, log filtering, problem determination, and end user identification as tenant identifiers. An example of such attribute is the values in existing client information fields that are available to applications for passing additional information to the database server via connections. These values are then used by the database server for enhanced operational functions of load balancing, accounting, log filtering, problem determination, and end user identification.

Abstract: A method for updating drivers. The method may include transmitting a connection request from a first computer to a second computer. The method may include creating a connection handshake in the first computer in response to the transmitted connection request, whereby the connection handshake includes client credentials and driver information. The method may include transmitting the created connection handshake from the first computer to a second computer. The method may include determining the first computer is authorized to connect to the second computer based on the client credentials. The method may include determining a first version level of a first plurality of drivers associated with the first computer is a lower version level than a second version level of a second plurality of drivers associated with the second computer based on the driver information. The method may include transmitting a driver update. The method may include installing the driver update.

Abstract: A tool for standardized layout transformations of BIDI data exchanged between legacy and modern systems is provided. Responsive to a determination that data requested in a client request is BIDI data, the tool initiates a layout transformation of the data requested at a single point within a database server. The tool determines a plurality of data from a connection string of the client request, wherein the plurality of data indicates a type of bi-directional data transformation. Responsive to the plurality of data from the connection string indicating data being returned to the client application from a database, the tool converts visual data to logical data at the single point within the database server. The tool returns transformed BIDI data to a client application. The tool inserts the transformed BIDI data into a database.

Abstract: A tool for standardized layout transformations of BIDI data exchanged between legacy and modern systems is provided. The tool retrieves client connection information from a client request for data. The tool determines, based, at least in part, on the client connection information, a client application's operating system. The tool determines whether the data requested in the client request is BIDI data. Responsive to a determination that the data requested is BIDI data, the tool initiates a layout transformation of the data requested at a single point within the database server. The tool returns transformed BIDI data to the client application.

Abstract: A method for updating drivers. The method may include transmitting a connection request from a first computer to a second computer. The method may include creating a connection handshake in the first computer in response to the transmitted connection request, whereby the connection handshake includes client credentials and driver information. The method may include transmitting the created connection handshake from the first computer to a second computer. The method may include determining the first computer is authorized to connect to the second computer based on the client credentials. The method may include determining a first version level of a first plurality of drivers associated with the first computer is a lower version level than a second version level of a second plurality of drivers associated with the second computer based on the driver information. The method may include transmitting a driver update. The method may include installing the driver update.

Abstract: A method for updating drivers. The method may include transmitting a connection request from a first computer to a second computer. The method may include creating a connection handshake in the first computer in response to the transmitted connection request, whereby the connection handshake includes client credentials and driver information. The method may include transmitting the created connection handshake from the first computer to a second computer. The method may include determining the first computer is authorized to connect to the second computer based on the client credentials. The method may include determining a first version level of a first plurality of drivers associated with the first computer is a lower version level than a second version level of a second plurality of drivers associated with the second computer based on the driver information. The method may include transmitting a driver update. The method may include installing the driver update.

Abstract: A method for updating drivers. The method may include transmitting a connection request from a first computer to a second computer. The method may include creating a connection handshake in the first computer in response to the transmitted connection request, whereby the connection handshake includes client credentials and driver information. The method may include transmitting the created connection handshake from the first computer to a second computer. The method may include determining the first computer is authorized to connect to the second computer based on the client credentials. The method may include determining a first version level of a first plurality of drivers associated with the first computer is a lower version level than a second version level of a second plurality of drivers associated with the second computer based on the driver information. The method may include transmitting a driver update. The method may include installing the driver update.

Abstract: Disclosed aspects relate to structured data and unstructured data integration management to provide a valid Java Database Connectivity (JDBC) results-set. A query is received by a database driver. In response to receiving the query, a single data frame having both a set of structured data and a set of unstructured data is constructed in a dynamic fashion by the database driver. Based on the single data frame, a valid JDBC results-set for the query is compiled by the database driver. Accordingly, a query response having the valid JDBC results-set is provided by the database driver.

Abstract: A tool for standardized layout transformations of BIDI data exchanged between legacy and modern systems is provided. The tool retrieves client connection information from a client request for data. The tool determines, based, at least in part, on the client connection information, a client application's operating system. The tool determines whether the data requested in the client request is BIDI data. Responsive to a determination that the data requested is BIDI data, the tool initiates a layout transformation of the data requested at a single point within the database server. The tool returns transformed BIDI data to the client application.

Abstract: A first compute node of a plurality of compute nodes of a database cluster may receive a request for a database transaction from a client application. The client application may be located within the first compute node. A first connection may be established, without regard to whether another compute node has a lighter workload than the first compute node, between the client application and a first database of the database cluster. The first connection may be a local connection, wherein the first database is located within the first compute node. The first compute node may detect that a failure associated with the first database has occurred. The first compute node may execute a failover operation to continue servicing the request for the data. The executing of a failover operation may include establishing a second connection between the client application and a second database of the database cluster.

Abstract: As disclosed herein a method, executed by a computer, for enabling multi-tiered software stack diagnostic collection includes initiating, on a first tier of a multi-tiered software stack, a targeted diagnostics collection corresponding to a symptom of a failure, determining a symptom to a reason code mapping corresponding to the symptom in a product of a subsequent tier, and issuing a command to the product of the subsequent tier to initiate targeted diagnostics collection corresponding to the reason code. Problems or failures in a multi-tiered software stack environment may require analyses of programs or products corresponding to each tier of a multi-tiered software stack. The method described herein enables simultaneous collection of diagnostics for programs or products corresponding to each tier of a multi-tiered software stack. A computer system, and a computer program product corresponding to the method are also disclosed herein.

Abstract: A first compute node of a plurality of compute nodes of a database cluster may receive a request for a database transaction from a client application. The client application may be located within the first compute node. A first connection may be established, without regard to whether another compute node has a lighter workload than the first compute node, between the client application and a first database of the database cluster. The first connection may be a local connection, wherein the first database is located within the first compute node. The first compute node may detect that a failure associated with the first database has occurred. The first compute node may execute a failover operation to continue servicing the request for the data. The executing of a failover operation may include establishing a second connection between the client application and a second database of the database cluster.

Abstract: A tool for standardized layout transformations of BIDI data exchanged between legacy and modern systems is provided. The tool retrieves client connection information from a client request for data. The tool determines, based, at least in part, on the client connection information, a client application's operating system. The tool determines whether the data requested in the client request is BIDI data. Responsive to a determination that the data requested is BIDI data, the tool initiates a layout transformation of the data requested at a single point within the database server. The tool returns transformed BIDI data to the client application.

Abstract: A first compute node of a plurality of compute nodes of a database cluster may receive a request for a database transaction from a client application. The client application may be located within the first compute node. A first connection may be established, without regard to whether another compute node has a lighter workload than the first compute node, between the client application and a first database of the database cluster. The first connection may be a local connection, wherein the first database is located within the first compute node. The first compute node may detect that a failure associated with the first database has occurred. The first compute node may execute a failover operation to continue servicing the request for the data. The executing of a failover operation may include establishing a second connection between the client application and a second database of the database cluster.

Abstract: A first compute node of a plurality of compute nodes of a database cluster may receive a request for a database transaction from a client application. The client application may be located within the first compute node. A first connection may be established, without regard to whether another compute node has a lighter workload than the first compute node, between the client application and a first database of the database cluster. The first connection may be a local connection, wherein the first database is located within the first compute node. The first compute node may detect that a failure associated with the first database has occurred. The first compute node may execute a failover operation to continue servicing the request for the data. The executing of a failover operation may include establishing a second connection between the client application and a second database of the database cluster.