Abstract: Described systems and techniques store, at a first time, first system service verification data that includes a first capture of a system services table having at least one system service entry, and a first portion of a system service identified in the at least one system service entry. At a second time, second system service verification data may be stored that includes a second capture of the system services table and a second portion of the system service identified in the at least one system service entry. At least one mismatch between the first system service verification data and the second system service verification data may be determined. At least one security notification message identifying the at least one mismatch with respect to at least one of the second capture of the system services table and the second portion may thus be generated.

Abstract: Described techniques provide convenient, reliable, straightforward techniques for enabling multi-path application outputs. A single application may be configured to output two or more data sets to two or more output destinations within a mainframe environment, without requiring copying or forwarding by an intermediate application utility.

Abstract: Described systems and techniques store, at a first time, first system service verification data that includes a first capture of a system services table having at least one system service entry, and a first portion of a system service identified in the at least one system service entry. At a second time, second system service verification data may be stored that includes a second capture of the system services table and a second portion of the system service identified in the at least one system service entry. At least one mismatch between the first system service verification data and the second system service verification data may be determined. At least one security notification message identifying the at least one mismatch with respect to at least one of the second capture of the system services table and the second portion may thus be generated.

Abstract: Systems and methods are provided that allow client programs using APIs for accessing local DB2 databases to access DB2 systems on remote logical partitions and remote zSeries mainframes rather than from a local DB2 system. For example, a method may include intercepting a DB2 request using a documented API for accessing local DB2 databases from a client program executing on a source mainframe system. The method may also include selecting a destination mainframe system and sending a buffer including information from the request from the source mainframe system to the destination mainframe system and establishing, at the destination mainframe system, a DB2 connection with the DB2 system from the request. The method may further include receiving a response from the DB2 system, sending a buffer having information from the response from the destination mainframe system to the source mainframe system, and providing the information to the client program.

Abstract: Systems and methods are provided that allow client programs using APIs for accessing local DB2 databases to access DB2 systems on remote logical partitions and remote zSeries mainframes rather than from a local DB2 system. For example, a method may include intercepting a DB2 request using a documented API for accessing local DB2 databases from a client program executing on a source mainframe system. The method may also include selecting a destination mainframe system and sending a buffer including information from the request from the source mainframe system to the destination mainframe system and establishing, at the destination mainframe system, a DB2 connection with the DB2 system from the request. The method may further include receiving a response from the DB2 system, sending a buffer having information from the response from the destination mainframe system to the source mainframe system, and providing the information to the client program.

Abstract: Systems and methods are provided that allow client programs using APIs for accessing local DB2 databases to access DB2 systems on remote logical partitions and remote zSeries mainframes rather than from a local DB2 system. For example, a method may include intercepting a DB2 request using a documented API for accessing local DB2 databases from a client program executing on a source mainframe system. The method may also include selecting a destination mainframe system and sending a buffer including information from the request from the source mainframe system to the destination mainframe system and establishing, at the destination mainframe system, a DB2 connection with the DB2 system from the request. The method may further include receiving a response from the DB2 system, sending a buffer having information from the response from the destination mainframe system to the source mainframe system, and providing the information to the client program.

Abstract: Systems and methods are provided that allow client programs using IMS database access interfaces to access IMS database data available from IMS systems on remote logical partitions and remote zSeries mainframes rather than from a local IMS system. For example, a method may include intercepting an IMS request having a documented IMS request format from a client program executing on a source mainframe system. The method may also include selecting a destination mainframe system and sending a buffer including information from the request from the source mainframe system to the destination mainframe system and establishing, at the destination mainframe system, an IMS DRA connection with the IMS system from the request. The method may further include receiving a response from the IMS system, sending a buffer having information from the response from the destination mainframe system to the source mainframe system, and providing the information to the client program.

Abstract: The embodiments provide a system for managing access to Information Management System (IMS) database resources. The system may include an initialization routine configured to generate a first task in response to an IMS batch job request to enable an application program access to IMS resources including attaching an IMS Coordinator Controller. The IMS Coordinator Controller may be configured to establish a database resource adaptor (DRA) connection to an IMS database control region. The initialization routine may be configured to generate a second task in response to the DRA connection being established including attaching an application program controller. The application program controller may be configured to transform a database access call from the application program to a DRA interface call to access the IMS resources via the DRA connection.

Abstract: Systems and methods are provided that allow client programs using APIs for accessing local DB2 databases to access DB2 systems on remote logical partitions and remote zSeries mainframes rather than from a local DB2 system. For example, a method may include intercepting a DB2 request using a documented API for accessing local DB2 databases from a client program executing on a source mainframe system. The method may also include selecting a destination mainframe system and sending a buffer including information from the request from the source mainframe system to the destination mainframe system and establishing, at the destination mainframe system, a DB2 connection with the DB2 system from the request. The method may further include receiving a response from the DB2 system, sending a buffer having information from the response from the destination mainframe system to the source mainframe system, and providing the information to the client program.

Abstract: Systems and methods are provided that allow client programs using IMS database access interfaces to access IMS database data available from IMS systems on remote logical partitions and remote zSeries mainframes rather than from a local IMS system. For example, a method may include intercepting an IMS request having a documented IMS request format from a client program executing on a source mainframe system. The method may also include selecting a destination mainframe system and sending a buffer including information from the request from the source mainframe system to the destination mainframe system and establishing, at the destination mainframe system, an IMS DRA connection with the IMS system from the request. The method may further include receiving a response from the IMS system, sending a buffer having information from the response from the destination mainframe system to the source mainframe system, and providing the information to the client program.

Abstract: Systems and methods are provided that allow client programs using IMS database access interfaces to access IMS database data available from IMS systems on remote logical partitions and remote zSeries mainframes rather than from a local IMS system. For example, a method may include intercepting an IMS request having a documented IMS request format from a client program executing on a source mainframe system. The method may also include selecting a destination mainframe system and sending a buffer including information from the request from the source mainframe system to the destination mainframe system and establishing, at the destination mainframe system, an IMS DRA connection with the IMS system from the request. The method may further include receiving a response from the IMS system, sending a buffer having information from the response from the destination mainframe system to the source mainframe system, and providing the information to the client program.

Abstract: Systems and methods are provided that allow client programs using APIs for accessing local DB2 databases to access DB2 systems on remote logical partitions and remote zSeries mainframes rather than from a local DB2 system. For example, a method may include intercepting a DB2 request using a documented API for accessing local DB2 databases from a client program executing on a source mainframe system. The method may also include selecting a destination mainframe system and sending a buffer including information from the request from the source mainframe system to the destination mainframe system and establishing, at the destination mainframe system, a DB2 connection with the DB2 system from the request. The method may further include receiving a response from the DB2 system, sending a buffer having information from the response from the destination mainframe system to the source mainframe system, and providing the information to the client program.

Abstract: The embodiments provide a system for managing access to Information Management System (IMS) database resources. The system may include an initialization routine configured to generate a first task in response to an IMS batch job request to enable an application program access to IMS resources including attaching an IMS Coordinator Controller. The IMS Coordinator Controller may be configured to establish a database resource adaptor (DRA) connection to an IMS database control region. The initialization routine may be configured to generate a second task in response to the DRA connection being established including attaching an application program controller. The application program controller may be configured to transform a database access call from the application program to a DRA interface call to access the IMS resources via the DRA connection.

Abstract: Systems and methods are provided that allow client programs using IMS database access interfaces to access IMS database data available from IMS systems on remote logical partitions and remote zSeries mainframes rather than from a local IMS system. For example, a method may include intercepting an IMS request having a documented IMS request format from a client program executing on a source mainframe system. The method may also include selecting a destination mainframe system and sending a buffer including information from the request from the source mainframe system to the destination mainframe system and establishing, at the destination mainframe system, an IMS DRA connection with the IMS system from the request. The method may further include receiving a response from the IMS system, sending a buffer having information from the response from the destination mainframe system to the source mainframe system, and providing the information to the client program.

Abstract: Systems and methods are provided that allow client programs using APIs for accessing local DB2 databases to access DB2 systems on remote logical partitions and remote zSeries mainframes rather than from a local DB2 system. For example, a method may include intercepting a DB2 request using a documented API for accessing local DB2 databases from a client program executing on a source mainframe system. The method may also include selecting a destination mainframe system and sending a buffer including information from the request from the source mainframe system to the destination mainframe system and establishing, at the destination mainframe system, a DB2 connection with the DB2 system from the request. The method may further include receiving a response from the DB2 system, sending a buffer having information from the response from the destination mainframe system to the source mainframe system, and providing the information to the client program.

Abstract: The present invention includes aspects pertaining to enabling an IMS batch application program to temporarily release its access to IMS resources that it shares with an IMS database management system or other non-IMS system agent, without terminating the application program. The present invention identifies when the batch application program issues a call that generate a sync point, and disconnects the program's connection to the IMS resources. The batch application program retains access to any independently obtained non-IMS resources when the program is disconnected from the IMS resources. The IMS database management system or other non-IMS system agent has temporary exclusive access to the IMS resources after the batch application program connection is disconnected. After such temporary exclusive access is complete, the batch application program's connection to the IMS resources is reestablished, and the batch application receives a response to its original call that generated a sync point.